chat-recall MCP server
Checked 2026-09-07. Alive: yes. Handshake: gated.
Category: ai-ml. API and field schema.
Facts
| id | munhq--chat-recall |
| name | chat-recall |
| registry_name | io.github.munhq/chat-recall |
| repo_url | https://github.com/munhq/chat-recall |
| endpoint_url | https://chatrecall.dev/mcp |
| transport | stdio |
| alive | yes |
| liveness_reason | not available |
| check_reachable | yes |
| check_recent_commit | yes |
| check_installable | yes |
| handshake_status | gated |
| handshake_checked_at | 2026-09-07T18:08:32Z |
| handshake_protocol_version | not available |
| handshake_auth_hint | Bearer resource_metadata="https://chatrecall.dev/.well-known/oauth-protected-resource" |
| handshake_auth_discoverable | resource_metadata |
| handshake_failure_layer | none |
| handshake_latency_ms | 1886 |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | active |
| last_commit_at | 2026-09-07T08:15:01Z |
| category | ai-ml |
| license_spdx | Elastic-2.0 |
How to install or connect
Run it with npx over stdio; the package coordinate 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.