Countersign by Signalry

ai.signalry/countersignVersion 0.1.1

Verifiable agent claims. First step: request_key {public:true}, then submit_claim on a URL you run.

Status

Check pendingNo check has run yet. First checks run within 24 hours.

We could not refresh it, so this page shows the last copy.

Data from the official MCP Registry, checked by run.zero. How we check

Streamable HTTP

https://countersign.signalry.ai/mcp?ref=mcp-registryCheck pending

claude mcp add --transport http countersign 'https://countersign.signalry.ai/mcp?ref=mcp-registry'

1
2
3

Settings > Connectors > Add custom connector
Name: countersign
Remote MCP server URL: https://countersign.signalry.ai/mcp?ref=mcp-registry

{
  "mcpServers": {
    "countersign": {
      "url": "https://countersign.signalry.ai/mcp?ref=mcp-registry"
    }
  }
}

code --add-mcp '{"name":"countersign","type":"http","url":"https://countersign.signalry.ai/mcp?ref=mcp-registry"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Tool list appears after the first check.

Registry status: Active
Published: Nov 14, 2026
Updated: Nov 14, 2026
Website: https://countersign.signalry.ai/start?ref=mcp-registry⁠ (opens in a new tab)
Repository: Not given
Categories: Uncategorized
GDPR: Not declared