ChainRPC MCP MCP server
Checked 2026-09-07. Alive: yes. Handshake: dead.
Category: databases. API and field schema.
Facts
| id | john0n1--chainrpc-mcp |
| name | ChainRPC MCP |
| registry_name | io.github.John0n1/chainrpc-mcp |
| repo_url | https://github.com/John0n1/chainrpc-mcp |
| endpoint_url | https://chainrpc-mcp.mitander.io/mcp |
| transport | mixed |
| alive | yes |
| liveness_reason | not available |
| check_reachable | yes |
| check_recent_commit | yes |
| check_installable | yes |
| handshake_status | dead |
| handshake_checked_at | 2026-09-07T18:06:26Z |
| handshake_protocol_version | not available |
| handshake_auth_hint | not available |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | http |
| handshake_latency_ms | 998 |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | active |
| last_commit_at | 2026-09-04T10:01:52Z |
| category | databases |
| license_spdx | MIT |
How to install or connect
Connect your MCP client to https://chainrpc-mcp.mitander.io/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.