Countersign
REMOTE · COUNTERSIGN.LLPRO.AI
Signed AI checks. Free daily quota; credit keys from $10 at llpro.ai/pay/credit; x402 accepted.
Available components
Last scanned (18 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1428 tokens (~204/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 7 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 0
- Tool “countersign_stamp” rewrote its description, which is the text the model reads security
- 20 Nov 26 +4
- Stability: 0.17 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “launchpad.start” was removed ▼ security
- Tool “launchpad.progress” was removed ▼ security
- Tool “feedback.submit” was removed ▼ security
- Authorization: unverified → partial ▲ security
- Tool “countersign_stamp” rewrote its description, which is the text the model reads security
- Schema quality: 173 → 201 ▼ functional
- Schema quality: good → excellent functional
- New tool “agent_readiness_audit” functional
- Tool “countersign_stamp” changed its title: Check work and get a signed stamp cosmetic
- Tool “countersign_log” changed its title: Read the public stamp log cosmetic
- Tool “countersign_verify” changed its title: Verify a stamp cosmetic
- Tool “launchpad_start” changed its title: Start here: get a plan for a goal cosmetic
- Tool “launchpad_progress” changed its title: Report progress on a plan cosmetic
- Tool “feedback_submit” changed its title: Send feedback to LLPRO cosmetic
- 19 Nov 26 +3
- Tool “countersign_stamp” rewrote its description, which is the text the model reads security
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2025-03-26 → 2026-07-28 functional
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
- HTTPS: unverified → fail ▼ security
- Tool “countersign_log” rewrote its description, which is the text the model reads security
- Tool “countersign_verify” rewrote its description, which is the text the model reads security
- Schema quality: 145 → 167 ▼ functional
- Tool coverage: 68% → 78% ▲ functional
- “countersign_log” reworded the description of “after” cosmetic
- “countersign_log” reworded the description of “limit” cosmetic
- “countersign_verify” reworded the description of “id” cosmetic
- “countersign_verify” reworded the description of “output” cosmetic
- 15 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Nov 26 54
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://countersign.llpro.ai/mcp?via=mcp-registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=llpro.ai | CN=WE1,O=Google Trust Services,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ffa50cd1836b2a8b0ecd6433c52c4e23 |
| SANs: llpro.ai, *.llpro.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of countersign.llpro.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| llpro.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://countersign.llpro.ai/mcp?via=mcp-registry | Verified | 200 | |
| http (plaintext) | http://countersign.llpro.ai/mcp?via=mcp-registry | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agent_readiness_audit ~313
Use when you or your user want a site or a code repo ready for agent traffic. Send a domain (example.com) or a public GitHub repo (https://github.com/owner/repo). Returns a 0-100 readiness score and each item checked, found or missing, why it matters and how to fix it. Site: /llms.txt, A2A agent card, MCP server card or endpoint, a payment path for agents (HTTP 402 / x402), robots.txt rules for AI agents, sitemap, OpenAPI. Repo: llms.txt, AGENTS.md, MCP registry server.json, agent card, README connect section. Read-only GET requests (at most 12), public addresses only, nothing stored about the site, signed result. First audit each day free; then $0.10 an audit (prepaid credit key or x402), charged only while it passes today's known-answer test. Free daily quota; credit keys from $1 at llpro.ai/pay/credit; x402 accepted. Send the key as Authorization: Bearer <llk_ key>. We charge only while this tool passes today's known-answer test; in testing it answers free.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | A website to audit, e.g. example.com (a full https URL is accepted; only the host name is used). |
| repo | string | – | Or a public GitHub repo: https://github.com/owner/repo (send domain OR repo, not both). |
No output schema declared.
No examples provided.
countersign_log Read the public stamp log ~134
Read the public, append-only log of Countersign stamps: entries after a sequence number, in order, plus the head hash, entry count and public key so you can check signatures yourself. Use it when you audit stamps in bulk, mirror the log, or want to see where a stamp sits in the chain. Free, read-only; private stamps show only a hash of each finding's detail.
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | Return entries with a sequence number above this (default 0 = from the first entry) |
| limit | integer | – | Entries per call, 1 to 200 (default 20) |
No output schema declared.
No examples provided.
countersign_stamp Check work and get a signed stamp ~353
Use when you need a signed check, by code that did not make the work, of work you or another agent produced (a report, calculation, summary, filing draft or code) before relying on it or handing it on. Countersign re-computes arithmetic, looks up quotes and values in the cited sources, opens links and parses code, then returns a signed stamp (pass, fail or inconclusive) saying exactly what is wrong, with time and method. The stamp is kept in a public log. No AI model decides the result. It never checks work it produced. Free daily quota; credit keys from $1 at llpro.ai/pay/credit; x402 accepted. Send the key as Authorization: Bearer <llk_ key>. We charge only while this tool passes today's known-answer test; in testing it answers free.
| Name | Type | Req | Description |
|---|---|---|---|
| claims | array | – | Optional explicit items: {type:'arithmetic', expression, claimed} or {type:'quote', source_url, quote} or {type:'value', source_url, value} |
| kind | string | – | – |
| language | string | – | For code: python or json get a syntax check |
| output | string | yes | The work to check, as text (max 100000 chars). Equations written as '12 * 4 = 48' are re-computed. |
| private | boolean | – | If true the public log shows only a hash of each finding's detail; you still get the full detail |
| producer | object | yes | Who made the work: {agent_id, model}. Required; used for the independence rule. |
| sources | array | – | Optional cited sources: {url, quote?} |
No output schema declared.
No examples provided.
countersign_verify Verify a stamp ~171
Confirm that a Countersign stamp someone shows you is real before you trust it. Use it when another agent hands you work with a stamp id: give the id, and optionally the exact work text to prove the stamp covers that text and nothing else. Returns the logged stamp, whether its signature is valid and, with the text, whether it matches. It checks the log's copy, not the copy you were shown: compare the returned verdict and output_sha256 with that copy. Free, read-only; it does not re-check the work itself (countersign_stamp does that).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Stamp id: the id field returned by countersign_stamp |
| output | string | – | Optional: the exact work text the stamp should cover; its sha256 is compared with the stamp |
No output schema declared.
No examples provided.
feedback_submit Send feedback to LLPRO ~206
Tell LLPRO what failed, what was missing or what would improve this service. Read daily by the service owner and turned into a fix or an answer; shipped ideas are credited on https://llpro.ai/changelog and earn a contributor mark on Agent Record. Not for support requests that need a reply: write support@llpro.ai for those. Do not send secrets.
| Name | Type | Req | Description |
|---|---|---|---|
| credit | boolean | – | Default true: credit your agent id on the changelog if the idea ships. Send false to opt out. |
| message | string | – | Anything else, in your own words. |
| rating | integer | – | – |
| tool | string | – | Which tool or endpoint this is about. |
| what_failed | string | – | What did not work, and the call that failed (tool, arguments, what you expected). |
| what_missing | string | – | What you needed and could not get. |
| what_would_improve | string | – | One concrete change that would make this better. |
No output schema declared.
No examples provided.
launchpad_progress Report progress on a plan ~104
Report where you are on a Launchpad plan and get the next step, an on-track check and, if you are stuck, a way round. Needs the launch_id and token from launchpad.start.
| Name | Type | Req | Description |
|---|---|---|---|
| launch_id | string | yes | – |
| reason | string | – | Only with status stuck. |
| status | string | – | – |
| step | string | – | A step id from your plan. Leave out to ask where you are. |
| token | string | yes | – |
No output schema declared.
No examples provided.
launchpad_start Start here: get a plan for a goal ~147
Stuck? Start here. Give your goal and any limits; get back a concrete plan (LLPRO tools first, then registries and the open web), the first task to run, and a token to report progress. Free. The goal is read for keywords only and is never stored. Anything that spends, signs, sends, shares, connects or deletes is marked as needing your owner's approval.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | A stable name for you. Used only to count return visits. |
| constraints | object | – | Optional limits. They only ever make the plan stricter. |
| goal | string | yes | What you are trying to get done, in a sentence or two. |
No output schema declared.
No examples provided.
How do I install the Countersign MCP server?
Countersign is a hosted endpoint at https://countersign.llpro.ai/mcp?via=mcp-registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · countersign.llpro.ai
claude mcp add --transport http ai-llpro-countersign-countersign 'https://countersign.llpro.ai/mcp?via=mcp-registry'
What is the Countersign MCP server?
Countersign is an MCP server listed in the public MCP registry as ai.llpro.countersign/countersign. Signed AI checks. Free daily quota; credit keys from $10 at llpro.ai/pay/credit; x402 accepted. This page covers its hosted endpoint (https://countersign.llpro.ai/mcp?via=mcp-registry).
Is the Countersign MCP server safe to use?
Countersign scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Countersign MCP server expose?
Countersign exposes 7 tools: countersign_stamp, countersign_verify, countersign_log, agent_readiness_audit, feedback_submit, and 2 more. Their descriptions and schemas cost roughly 1,428 tokens of context every time the server is loaded.
Does the Countersign MCP server require authentication?
No. We connected to Countersign without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Countersign MCP server still maintained?
Countersign is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Countersign MCP server?
VerifyMCP ran 13 checks on Countersign, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.