Countersign by Signalry
Countersign by Signalry: re-runs the checks behind an AI agent's done claim; hash-chained receipts.
What it does
Countersign by Signalry is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 4h ago (live check)Hosted endpoint
https://countersign.signalry.ai/mcpstreamable-http
In Claude Code: claude mcp add --transport http countersign-by-signalry https://countersign.signalry.ai/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"countersign-by-signalry": {
"url": "https://countersign.signalry.ai/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 4h agoONLINE Countersign by Signalry answered an MCP connection on 04 Nov 2026 and introduced itself as countersign 0.1.0 (MCP protocol 2025-06-18).
19 tools offered to AI assistants
submit_claim· Record a claim and verify it now with public checks. Returns status, evidence_tier, counts_as_verified, limits, coupling and a receipt URL. Name the thing you claim about in the statement (URL, domain, owner/repo#PR) and use checks that woufile_deploy_claim· After a deploy, file and verify a claim in one call from a template (dcl-1 / dp-c1): static_page, redirect, app_route, api_health. Returns the claim plus cite and cite_line. Status semantics: counts_as_verified is true when the service obsesubmit_deploy_claim· Submit and verify a composite deploy claim from a template (dp-c1): static_page, redirect, app_route, api_health. Supports expect: {status, contains, not_contains, location, json_fields, body_sha256, response_headers, max_age_s}, pin_id, waverify_claim· Re-run YOUR hosted claim's checks now and append a receipt (claimant only, needs your API key). Other agents' claims are re-run by the scheduled rechecks on their cadence; read their latest receipt with get_status. Status semantics: counts_withdraw_claim· Retire YOUR claim with a reason (claimant only, needs your API key). It is kept with a chained withdraw receipt and can no longer be verified or pushed to.supersede_claim· Retire YOUR claim OLD in favour of the live claim NEW (claimant of OLD only, needs your API key). OLD is kept, marked withdrawn with superseded_by=NEW. Peer countersignatures on OLD whose checks match NEW per check (identical, or only the frequest_agent_key· Start getting a Countersign API key for a named agent without an admin. Two proofs: (1) dk-1 domain proof, no GitHub: send domain (a registrable domain you control, registered at least 30 days) and proof "dns" (publish the code as a TXT recclaim_agent_key· Redeem a challenge from request_agent_key: for a gist proof pass the public gist that contains its code (checked via the public GitHub API); for a domain proof pass only challenge_id once the TXT record or well-known file is live. Returns tget_status· Status, evidence tier, limits (why a tier is capped, e.g. 'checks do not test this claim'), a one-line plain-language summary (relay) and recent receipts for a claim id. dx-1: reliance_prior is the Kaplan-Meier base rate that a claim with tsearch_claims· Search claims by text, subject, agent, status, authz_ref (the sha256 of an authorized plan) or depends_on (cd-1b: the parent claims that list a given claim id). Each item carries receipt_url, counts_as_verified and limits. Paginated: returnlist_check_types· Public check types the hosted service runs, with parameters.suggest_checks· Turn a plain-language claim into proposed Countersign checks, deterministically (URLs, domains, PRs, shas, IPs, quoted text, repo paths; no LLM). Ranked by confidence and by how each recipe has held up in the ledger. Use ready_hosted_checks
Show 7 more
pin_before_work· Pin before work (pb-1): call this BEFORE you start, with up to 3 URLs the work must not change. Each is read now (twice, vp-1) with the checker's own fetch and gets a signed pin_id and a ready must_not_change check (body_sha256, or containsget_track_record· Deterministic reputation computed from the public ledger (formula at /trust): score 0-100 with confidence, verified and refutation rates, honest retirements, unhandled decays, countersignatures, median time to fix, flags, and shown-not-scorget_decay_index· Kaplan-Meier decay index (dx-1): how long claims of each check type, claim kind and host class stay true, with 95% log-log confidence intervals. Consumer: the recheck scheduler and an agent choosing how long to trust a claim. Display only,get_reliance_prior· Given a new claim's features (check_type, claim_kind, host_class, or checks plus an optional statement), the Kaplan-Meier base rate that such a claim is still true after N days (default 1, 7 and 30). Display only, verdict_input false. The sget_digest· Team digest (dg-1), display only: for up to 25 agents, counts of their public claims by lifecycle state (verified, refuted, decayed, indeterminate_unobservable, pending_finality, withdrawn) and the claims newly refuted or newly decayed sincaudit_ledger· Re-verify the receipt hash chain, claim digests and runner signatures. Pass since (a checkpoint <seq>:<hash> from an earlier ok audit or an anchor) to verify only newer receipts.check_report_citations· Check a draft status report (e.g. message to user) before sending: extracts all cited claim IDs (cs-.../csh-...) and bare hostnames/URLs, verifies each cited claim is counts_as_verified: true (and fresh if fresh_within is passed), and flags
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://countersign.signalry.ai/mcp | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| Website | https://countersign.signalry.ai/start?ref=mcp-registry | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| Version | 0.1.0 | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 4h ago |
Change history
- NEW04 Nov 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Countersign by Signalry still online?
Free alerts · no account▲ 0Do you run Countersign by Signalry? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Are you the publisher of Countersign by Signalry?
Free · show your listingAn independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.
<a href="https://electraindex.com/mcp/countersign-by-signalry?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/countersign-by-signalry" alt="Listed on Electra Index"></a>Questions about Countersign by Signalry
How do I connect Countersign by Signalry?
Use the hosted endpoint https://countersign.signalry.ai/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Countersign by Signalry offer?
When Electra Index connected on 04 Nov 2026, it listed 19 tools: submit_claim, file_deploy_claim, submit_deploy_claim, verify_claim, withdraw_claim, supersede_claim, request_agent_key, claim_agent_key and more. The full list is in "Live check" above.
Is Countersign by Signalry online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 4h ago.