Respawn Signal MCP server
Checked 2026-09-07. Alive: no. Handshake: gated.
Category: communication. API and field schema.
Facts
| id | registry--co.respawnmedia.signal--respawn-signal |
| name | Respawn Signal |
| registry_name | co.respawnmedia.signal/respawn-signal |
| repo_url | not available |
| endpoint_url | https://signal.respawnmedia.co/mcp |
| transport | streamable-http |
| alive | no |
| liveness_reason | stale |
| check_reachable | yes |
| check_recent_commit | no |
| check_installable | yes |
| handshake_status | gated |
| handshake_checked_at | 2026-09-07T18:16:54Z |
| handshake_protocol_version | not available |
| handshake_auth_hint | Bearer realm="respawn-signal", resource_metadata="https://signal.respawnmedia.co/.well-known/oauth-protected-resource/mcp", scope="signal:read signal:intel" |
| handshake_auth_discoverable | resource_metadata |
| handshake_failure_layer | none |
| handshake_latency_ms | 381 |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | unknown |
| last_commit_at | not available |
| category | communication |
| license_spdx | not available |
How to install or connect
Connect your MCP client to https://signal.respawnmedia.co/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.