Kenva MCP server
Checked 2026-09-07. Alive: no. Handshake: dead.
Category: crm-sales. API and field schema.
Facts
| id | registry--io.github.kenvaapp--kenva |
| name | Kenva |
| registry_name | io.github.kenvaapp/kenva |
| repo_url | not available |
| endpoint_url | https://kenva-crm-mcp-server.kenva.workers.dev/mcp |
| transport | streamable-http |
| alive | no |
| liveness_reason | stale |
| check_reachable | yes |
| check_recent_commit | no |
| check_installable | yes |
| handshake_status | dead |
| handshake_checked_at | 2026-09-07T18:49:50Z |
| handshake_protocol_version | not available |
| handshake_auth_hint | not available |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | http |
| handshake_latency_ms | 1040 |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | unknown |
| last_commit_at | not available |
| category | crm-sales |
| license_spdx | not available |
How to install or connect
Connect your MCP client to https://kenva-crm-mcp-server.kenva.workers.dev/mcp.
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.