# Countersign by Signalry (remote · countersign.signalry.ai)

Countersign by Signalry: live checks of an agent's done claim. First call: start {subject}

- Trust score: 75/100 (medium)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `countersign.signalry.ai`: 75/100 (this document), [markdown](https://verifymcp.io/servers/ai-signalry-countersign/countersign-2.md), [page](https://verifymcp.io/servers/ai-signalry-countersign/countersign-2)

## Channel facts

- Endpoint: `https://countersign.signalry.ai/mcp?ref=mcp-registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1217 tokens (~135/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Countersign by Signalry MCP server?

Countersign by Signalry is a hosted endpoint at https://countersign.signalry.ai/mcp?ref=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.

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "ai-signalry-countersign": {
      "type": "http",
      "url": "https://countersign.signalry.ai/mcp?ref=mcp-registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-signalry-countersign]
url = "https://countersign.signalry.ai/mcp?ref=mcp-registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-signalry-countersign": {
      "type": "remote",
      "url": "https://countersign.signalry.ai/mcp?ref=mcp-registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-signalry-countersign --url 'https://countersign.signalry.ai/mcp?ref=mcp-registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-signalry-countersign:
    url: "https://countersign.signalry.ai/mcp?ref=mcp-registry"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-signalry-countersign": {
      "Transport": "http",
      "Url": "https://countersign.signalry.ai/mcp?ref=mcp-registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-signalry-countersign -t streamable-http -u 'https://countersign.signalry.ai/mcp?ref=mcp-registry'
```

### Other

```json
{
  "mcpServers": {
    "ai-signalry-countersign": {
      "type": "http",
      "url": "https://countersign.signalry.ai/mcp?ref=mcp-registry"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 75, +4)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_reply_gate” rewrote its description, which is the text the model reads
- [security] Tool “find_tools” rewrote its description, which is the text the model reads
- [security] Tool “get_track_record” rewrote its description, which is the text the model reads
- [security] Tool “request_key” rewrote its description, which is the text the model reads
- [security] Tool “start” rewrote its description, which is the text the model reads
- [security] Tool “verify_claim” rewrote its description, which is the text the model reads
- [security] Tool “try_check” rewrote its description, which is the text the model reads
- [security] Tool “submit_claim” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 165 → 135
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] Schema quality: fair → good
- [functional] New prompt “check_site”
- [functional] New prompt “see_example”
- [functional] New tool “show_example”
- [cosmetic] “start” added an optional parameter “api_key”
- [cosmetic] “try_check” reworded the description of “subject”

### 2026-11-19 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 70, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “verify_claim” rewrote its description, which is the text the model reads
- [security] Tool “try_check” rewrote its description, which is the text the model reads
- [security] Tool “submit_claim” rewrote its description, which is the text the model reads
- [security] Tool “request_key” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 150 → 165
- [functional improvement] Tool coverage: 33% → 47%
- [functional] Server version: 0.1.1 → 0.1.2
- [functional] New tool “start”
- [cosmetic] “verify_claim” added an optional parameter “api_key”
- [cosmetic] “submit_claim” added an optional parameter “api_key”
- [cosmetic] “request_key” reworded the description of “public”

### 2026-11-16 (score 69, +4)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “find_tools” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 358 → 150
- [functional improvement] Tool coverage: 11% → 33%
- [functional] New tool “request_key”
- [cosmetic] “submit_claim” added an optional parameter “full”

### 2026-11-15 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 65)

First indexed and scored.

## MCP tools (9)

### `show_example` (~55 tokens)

Shows one real claim from the public ledger that counts as verified now: statement, the checks this service ran, verdict and receipt URL. No arguments; writes nothing. Use it to see a receipt before checking a host of your own.

### `try_check` (~85 tokens)

Checks a public hostname live now: an https GET of / (status only) and its TLS certificate. Takes a bare hostname such as docs.example.org. No key; writes nothing. Returns the start and submit_claim arguments that would record the same checks.

Input parameters:

- `subject` (string, required): bare public hostname, e.g. docs.example.org (no scheme, path, port or IP)

### `start` (~116 tokens)

Issues a csk_ key and files a first claim with it in one call: https://<subject>/ answers 200 with valid TLS, checked now; it counts if both pass. subject: a bare hostname the caller operates. Writes a key and one unlisted claim (no new key with api_key).

Input parameters:

- `api_key` (string): ks-1: a csk_ key you already hold; start files the first claim with it
- `subject` (string, required): bare hostname you operate, e.g. docs.example.org

### `submit_claim` (~145 tokens)

Records a claim about work (a deploy is live, a page contains a text, a PR merged) and runs its checks now. It counts only if the checks pass, a check targets what the statement names, and a key is sent (Bearer or api_key); no key yet: start, or request_key {public: true}.

Input parameters:

- `api_key` (string): mf-1: your csk_ key, for clients that set headers only at connect (the header wins when both are sent)
- `checks` (array, required)
- `full` (boolean): true: whole claim; default compact
- `statement` (string, required)
- `subject` (string, required)

### `verify_claim` (~72 tokens)

Re-runs the checks of the caller's own claim and appends a receipt. Needs the caller's key.

Input parameters:

- `api_key` (string): mf-1: your csk_ key, for clients that set headers only at connect (the header wins when both are sent)
- `id` (string, required)

### `check_reply_gate` (~47 tokens)

Checks a drafted reply before it says live or done: cited claims must be verified and fresh. Read-only.

Input parameters:

- `fresh_within` (string)
- `text` (string, required)

### `get_track_record` (~35 tokens)

An agent's public track record, or the ranked table when agent is omitted. Read-only.

Input parameters:

- `agent` (string)

### `request_key` (~91 tokens)

Issues a csk_ key without filing a claim: {} or {public: true} returns an unbound key now; {agent} a claimable link. Then start {subject, api_key} or submit_claim.

Input parameters:

- `agent` (string): claimable-link path (proof later)
- `public` (boolean): true or omitted with no agent: a csk_ key now (identity unbound)

### `find_tools` (~39 tokens)

Lists the other tools (request_agent_key, get_status, search_claims, more) with arguments. Read-only.

Input parameters:

- `query` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-signalry-countersign/countersign-2#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 75
- 2026-11-19: 71
- 2026-11-18: 70
- 2026-11-17: 69
- 2026-11-16: 69
- 2026-11-15: 65
- 2026-11-14: 65

## Common questions

### What is the Countersign by Signalry MCP server?

Countersign by Signalry is an MCP server listed in the public MCP registry as ai.signalry/countersign. Countersign by Signalry: live checks of an agent's done claim. First call: start {subject}. This page covers its hosted endpoint (https://countersign.signalry.ai/mcp?ref=mcp-registry).

### Is the Countersign by Signalry MCP server safe to use?

Countersign by Signalry scores 75 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 by Signalry MCP server expose?

Countersign by Signalry exposes 9 tools: show_example, try_check, start, submit_claim, verify_claim, and 4 more. Their descriptions and schemas cost roughly 685 tokens of context every time the server is loaded.

### Does the Countersign by Signalry MCP server require authentication?

No. We connected to Countersign by Signalry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Countersign by Signalry MCP server still maintained?

Countersign by Signalry 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 by Signalry MCP server?

VerifyMCP ran 13 checks on Countersign by Signalry, 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.

## Links

- Remote endpoint: https://countersign.signalry.ai/mcp?ref=mcp-registry
- Website: https://countersign.signalry.ai/start?ref=mcp-registry
- Changelog RSS feed: https://verifymcp.io/servers/ai-signalry-countersign/countersign-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-signalry-countersign/countersign-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-signalry-countersign/countersign-2.json
- HTML version of this page: https://verifymcp.io/servers/ai-signalry-countersign/countersign-2
