Sovereign AI Services

Model Context Protocol

Plug the verification layer into an AI agent — five MCP tools

One MCP server for Claude, Cursor, Goose, Cline, Continue and custom agents: seal, verify, anchor, cite, audit. The server is written and runs from source. It is not published to a package registry yet, so there is no install count and no install command that resolves.

Not publishedno install count exists

Install

Three steps. No code changes.

The server runs locally over stdio. Your keys never leave your machine — only digests and signatures are published.

Step 01

Run the installer

One command would provision a keypair, a member number and a wallet for your agent.

Terminal — does not resolve yet

npx @apex/nation-mcp install

That package name is not registered on npm and returns 404, so this command fails today. It is printed as the intended entry point, not as something that works. Until the name is published by this platform, a stranger could publish a package under it — install nothing by this name from a registry.

Step 02

Add to your MCP config

Config file — ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "apex-nation": {
      "command": "NOT-PUBLISHED",
      "args": ["@apex/nation-mcp IS NOT PUBLISHED — this name is unregistered on npm"]
    }
  }
}

Step 03

Restart your agent and start signing

  • Every AI decision now gets a platform receipt
  • Verify any receipt at /verify
  • Zero code changes to your existing prompts
Open the verifier

Tool surface

Five tools exposed to the agent

Each tool is a bounded operation over the public API: seal a digest, verify a receipt, request an anchor, format a citation, audit a chain. Nothing in the set grants the platform authority over the agent's content, and nothing in it meters or charges the call — no payment processor is connected anywhere on this platform.

seal

Would sign submitted content and return a platform receipt.

Parameters
The content or file the agent wants sealed, plus an optional label.
Returns
A receipt ID, the SHA-256 digest and an Ed25519 signature.
agent: seal(content: "Approved refund #8812", label: "decision")
-> receipt_id: rcpt_7f2a...  digest: 9c1b...
-> verify at /verify

verify

Would check a hash or receipt against the record. The same check is live today over HTTP at /api/public/v1/verify.

Parameters
A receipt ID or a content digest, and optionally the original content.
Returns
Whether the digest is on the record, with the signing key and the ledger position.
agent: verify(receipt_id: "rcpt_7f2a...")
-> on_ledger: true
-> signed_by: ed25519:4b8d...

anchor

Would submit a seal to Bitcoin via OpenTimestamps.

Parameters
A receipt ID that already exists on the public ledger.
Returns
An OpenTimestamps proof and the pending or confirmed anchor state.
agent: anchor(receipt_id: "rcpt_7f2a...")
-> ots_proof: base64:AE9wZW5U...
-> state: pending_confirmation

cite

Would return a citation string for a sealed item.

Parameters
A receipt ID.
Returns
A formatted citation string with a permanent verification URL.
agent: cite(receipt_id: "rcpt_7f2a...")
-> "Sealed 2026-08-07T00:04Z · digest 9c1b..."
-> https://sovereign-ai.services/r/rcpt_7f2a...

audit

Would return the seals recorded for a listing.

Parameters
A listing slug or public key, plus an optional date range.
Returns
A chronological list of receipts with digests and anchor states.
agent: audit(entity: "acme-labs", since: "2026-07-01")
-> receipts returned in date order
-> chain_head: 3ad0...

Distribution

No installs have been counted, because nothing has been published

There is no registry listing, no install telemetry and no distribution record. When the server is published, the count will be read from the registry rather than written into this page.

What was here before

A headline reading “1,200+ total installs · 180+ this week · 10+ countries”, a gold “Live” badge carrying “1,200+ installs (updated weekly)”, and ten countries listed as reported territories. None of it came from anything. The server exists as compiled source; the package name it advertised returns 404 on npm, so no one could have installed it by that name, and no endpoint anywhere counts installs. Publishing a number nobody measures is the exact failure this platform exists to make impossible, so it is removed.

Registry membership is free and confers no legal rights in any physical jurisdiction. This is a commercial software platform, not a state.