Skip to content

Countersign MCP server

ai.llpro.countersign/countersigncountersign.llpro.aistreamable-httpv1.0.3Scanned

Signed AI checks. Free daily quota; credit keys from $10 at llpro.ai/pay/credit; x402 accepted.

9 tools: 8 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 8 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

8 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Countersign MCP server can do

The Countersign MCP server is published by countersign.llpro.ai, a domain the MCP Registry verified. It has 9 tools. It can create or change data (8 tools: countersign_stamp, countersign_verify, feedback.submit, feedback_submit and 4 more), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 1.0.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 8Claude Code: ask
  • countersign_stampUse when you need an independent, signed check of work you or another agent produced (a report, calculation, summary, filing draft or code) before relying on it or handing it on.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Use when you need an independent, signed check 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. It never checks work it produced. Past the free daily limit: pay per call with x402 (USDC on Base), or with no wallet use a prepaid credit key: send Authorization: Bearer <llk_ key> (buy from $10 by card at https://llpro.ai/pay/credit).
  • countersign_verifyConfirm that a Countersign stamp someone shows you is real before you trust it.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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).
  • feedback_submitTell LLPRO what failed, what was missing or what would improve this service.No findings

    Why it is in this group

    • The name "feedback_submit" says "submit": a word for a change.
    Description, as the server wrote it
    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.
  • feedback.submitTell LLPRO what failed, what was missing or what would improve this service.No findings

    Why it is in this group

    • The name "feedback.submit" says "submit": a word for a change.
    Description, as the server wrote it
    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.
  • launchpad_progressReport where you are on a Launchpad plan and get the next step, an on-track check and, if you are stuck, a way round.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • launchpad_startStuck?No findings

    Why it is in this group

    • The name "launchpad_start" says "start": a word for a change.
    Description, as the server wrote it
    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.
  • launchpad.progressReport where you are on a Launchpad plan and get the next step, an on-track check and, if you are stuck, a way round.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • launchpad.startStuck?No findings

    Why it is in this group

    • The name "launchpad.start" says "start": a word for a change.
    Description, as the server wrote it
    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.
Only reads 1Show 1 read-only tool
  • countersign_logRead 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 yourse…No findings

    Why it is in this group

    • The name "countersign_log" says "log": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:20 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (8 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://countersign.llpro.ai/mcp?via=mcp-registry: tools/list returned 9 tools to an anonymous client, including countersign_stamp (write), countersign_verify (write), feedback.submit (write), feedback_submit (write), launchpad.start (write) and 3 more

    What this check looks for

Posture changes

  1. Nov 15, 2026
    • Tools that change things, listed without credentials: 2 to 8

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools2 changed.~2 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 8.View diff
    • Tools that change things, listed without credentials: 2 to 8
  4. Tools6 added.+6 addedView diff

Install

Pinned to version 1.0.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http countersign https://countersign.llpro.ai/mcp?via=mcp-registry
claude mcp add --transport http countersign https://countersign.llpro.ai/mcp?via=mcp-registry

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__countersign__countersign_log"
    ],
    "ask": [
      "mcp__countersign__countersign_stamp",
      "mcp__countersign__countersign_verify",
      "mcp__countersign__feedback_submit",
      "mcp__countersign__launchpad_start",
      "mcp__countersign__launchpad_progress"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as countersign. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.llpro.countersign/countersign/verify?hash=06085d5542b0d5bca0ef26249d6d4886d90ad03d00c6174e221fa16b65d77f9a" | jq -e '.changed == false'

Pinned hash 06085d5542b0, from Nov 19, 2026, 19:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.llpro.countersign/countersign/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.llpro.countersign/countersign
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.llpro.countersign/countersign.svg)](https://radar.anlyon.com/servers/ai.llpro.countersign/countersign)

Source: MCP Registry. Synced Nov 19, 2026, 19:17 UTC.

Countersign MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Countersign MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 8 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Countersign MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Countersign MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Countersign MCP server have?

9 tools: 8 write, 1 read. countersign_stamp, countersign_verify, feedback.submit, feedback_submit, launchpad.start, launchpad_start, launchpad.progress, launchpad_progress and 1 more.

Does the Countersign MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Countersign MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Countersign MCP server changed its tools?

Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.