# Recognitium MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.recognitium%2Frecognitium
Registry id: `mcp-registry/com.recognitium/recognitium`
Status: auth-required (checked 2026-10-27T01:34:23.888Z)

## Measurements (30 days)

- Uptime: 99.53%
- Checks: 213
- Outages (90 days): 2

## Install

```json
{
  "mcpServers": {
    "recognitium-mcp-server": {
      "type": "http",
      "url": "https://api.recognitium.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http recognitium-mcp-server https://api.recognitium.com/mcp
```

## Tools (11)

- `agent_cv`: An agent's public CV read straight from its chain: identity, witness anchors, settled market history, distinct counterparties (wash-resistant reputation). Publi
- `chain_tip`: Read the authority chain's current head (sequence number + tip hash). Public, free. The external anchor against rollback.
- `check_silence`: Proof-of-absence: was the rail demonstrably alive over [from_ns, to_ns], so absence of a receipt is evidence of absence of an event? Only a 'covered' verdict pr
- `lineage_trace`: Recall by lineage over the hosted biography. Given a sealed state's receipt_id: 'descendants' returns the CONTAMINATION SET (every memory derived from it, succe
- `memory_history`: Read the biography: every sealed state of each memory in order, each backed by a receipt. Not the memory itself — the unforgeable record of what it has been. Me
- `memory_seal`: Seal the current state of a named memory into the agent's biography (1 tick per changed state; free no-op when unchanged). Hash the memory locally and send name
- `memory_verify`: Boot-time integrity check of the agent's memory against its sealed biography. Send entries: [{name, data_hash}] for every memory currently held. Per memory: VER
- `prove_anteriority`: Prove specific content is the content behind an existing receipt: supply the content's SHA-256 and the receipt_id. PROVEN = this exact content existed no later 
- `seal_hash`: Seal a SHA-256 fingerprint into the production receipt chain (1 tick). Hash your content locally; only the 32-byte fingerprint reaches the rail. Proves WHEN the
- `tick_balance`: The caller's private tick meter: balance, escrow, lifetime totals. Metered auth; ticks are non-transferable — a meter reading, not a wallet.
- `verify_receipt`: Verify a Recognitium receipt. Public, free, no key. Give a receipt_id (looked up on the rail) or a full receipt object. The chain hash re-derives offline with S

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.