inoyu-mcp-unomi-server MCP server
Checked 2026-09-08. Alive: no. Handshake: not available.
Category: other. API and field schema.
Facts
| id | inoyu-dev--inoyu-mcp-unomi-server |
| name | inoyu-mcp-unomi-server |
| registry_name | not available |
| repo_url | https://github.com/inoyu-dev/inoyu-mcp-unomi-server |
| endpoint_url | not available |
| transport | unknown |
| alive | no |
| liveness_reason | stale |
| check_reachable | yes |
| check_recent_commit | no |
| check_installable | yes |
| handshake_status | not available |
| handshake_checked_at | not available |
| handshake_protocol_version | not available |
| handshake_auth_hint | not available |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | not available |
| handshake_latency_ms | not available |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | dormant |
| last_commit_at | 2025-09-12T12:17:05Z |
| category | other |
| license_spdx | Apache-2.0 |
How to install or connect
Connect using the published unknown transport; installation metadata is available through the API.
What the checks mean
alive combines the applicable repository, package, and endpoint checks. A null result is not verifiable, not a failure. The MCP handshake is a separate structural probe and is not a security audit. Read the methodology.