APEX PSI MCP Server
This server lets an MCP agent write cryptographic seals of content to a public append-only ledger and later check them — evidence of existence and integrity, not of truth.
Seal content — hash up to 10,000 characters with SHA-256, record it in the APEX PSI ledger, and get back a signed receipt (Ed25519 plus post-quantum LMS-W4-SHA256 per the schema; the README also mentions ML-DSA-65). Optional context label, model ID, and predicate.
Verify a seal — look up a raw SHA-256 hash or a full receipt object to confirm it is present in the ledger and unchanged.
Anchor to Bitcoin — check or request OpenTimestamps anchoring of pending Merkle roots; submission only counts once a real block confirms it.
Generate citations — turn a receipt into an APA, BibTeX, or MLA citation pointing at a publicly checkable record.
Audit a receipt chain — check presence and integrity of each hash in an ordered list of receipts and report Merkle continuity (named
verify_chainin the README,auditin the schema).Use it free — no account or key required; limits are 20 ops/minute and 100/day per instance, and verification is unlimited.
Not supported — storing your content, editing or deleting records, certifying truth, scoring, or offering legal guarantees.
Enables anchoring cryptographic receipts to the Bitcoin blockchain using OpenTimestamps, providing verifiable timestamping and proof of existence.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@APEX PSI MCP Server Seal this document and generate a receipt"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
APEX PSI MCP server
Apex PSI is not a tool and not a product. It is the verification substrate — the layer beneath proof. It does not judge. It does not certify. It only remembers. This server is one application built on that layer.
Machine-readable setup for agents and directory scrapers: llms-install.md.
One config line gives any MCP-capable agent (Claude, Cursor, Qoder, Cline, Windsurf, and the rest) five evidence tools: seal, verify, anchor, cite, verify_chain.
A seal records the SHA-256 hash of a decision, document or artefact in a public append-only ledger and returns a receipt. Anyone can look that hash up again — free, forever, with no account, no key and no cooperation from us.
What a receipt proves: that this exact content existed at this timestamp, and has not changed since. What it never proves: that the content is true. A seal is an audit trail, not a verdict.
Tools
Tool | What it actually does |
seal | Writes the record's SHA-256 hash to the ledger and returns a receipt carrying an Ed25519 signature over the Merkle leaf, an ML-DSA-65 post-quantum signature, and — when a slot is available — an LMS-W4-SHA256 signature. The receipt's own |
verify | Looks a hash (or a whole receipt) up in the ledger and reports whether it is present and unchanged. Integrity, not truth. |
anchor | Reads the Bitcoin/OpenTimestamps anchoring state of the ledger's pending Merkle roots. Pass |
cite | Turns a receipt into a citation (APA, BibTeX, MLA) that points at a public, independently checkable record. |
verify_chain | Recomputes each hash's presence and Merkle continuity across a chain of receipts. A recomputation result, not an opinion. |
Related MCP server: deusproof-mcp
Install
Add to your MCP client config:
{
"mcpServers": {
"apex-psi": {
"command": "npx",
"args": ["-y", "apex-psi-mcp"]
}
}
}Or locally: npm install apex-psi-mcp.
Prove it works in two minutes
Ask the agent: "Seal the sentence 'hello psi' with APEX PSI."
Take the
decision_hashfrom the receipt and paste it into the public verifier: https://www.ai-governance-standard.com/verify
If the site returns the record, the seal is real. You never had to trust this server, our npm package, or our word — which is the entire point of the protocol.
Limits, stated plainly
Free use needs no account and no key: 20 operations per minute and 100 per day, enforced per
server instance — a flood guard rather than a subscription quota. Above that, an API key raises the
ceiling; capacity is priced, the finding never is. Verification itself is unlimited and free:
running the verifier locally costs nothing at all —
apex-psi-verifier on npm,
psi-verifier on PyPI.
Make the seal unavoidable: the execution gate
The five tools above are available to an agent, but nothing in MCP makes an agent call them. An
agent that never calls seal leaves no gap in the ledger — the ledger stays complete and says
nothing about that action. If your agent can move money, send a request or write to a system, that
gap is the whole problem.
So this package also ships a gate: a small module that seals first and acts second, inside the process that performs the side effect.
import { createGate, createNotarySealer } from "apex-psi-mcp/gate";
const gate = createGate({ sealer: createNotarySealer(), label: "payments-bot" });
const { value, receipt } = await gate.run(
() => payments.transfer({ amount: 500, to: "acct-42" }),
{ tool: "transfer", amount: 500, to: "acct-42" },
);If the seal fails, payments.transfer is never called — the gate throws GateClosedError. A gate
with no sealer configured refuses every action, because a gate nobody configured must not look like
a gate that is working.
What the gate does and does not do, stated plainly:
It enforces the order: the receipt exists before the action runs.
It cannot reach a process that never routes its side effect through it.
It cannot attest what a model did inside a GPU; the receipt covers the action as you declared it and the order in which the two happened.
createLocalSealer()seals into an in-process hash chain with no network and no account — a local permit, not a ledger receipt.createNotarySealer()returns a ledger receipt.
The same gate exists in the Python runtime as apex_psi.ExecutionGate. The two implementations
fingerprint the same bytes: fingerprint({"b":1,"a":[1,2],"c":"x"}) is
95c12ab4ca0e8f3c485ea1b1b1a2b24976d07180baf5ecad0d81b5bbaf07532b in both, and a CI check on each
side pins that number.
Configuration
Environment variables (both optional):
APEX_API_BASE— override the notary endpoint. Default:https://qhtntebpcribjiwrdtdd.supabase.co/functions/v1APEX_API_KEY— raises the daily ceiling for a workload. Never required to seal or verify.
What this server does not do
It does not store your content. Only the hash leaves your machine.
It does not certify, grade, score or approve anything.
It exposes no edit or delete path: the interface this server uses is write-once sealing plus read-only lookup. The check that matters is yours to run — re-verify any receipt at any time, and any change shows up as a failed lookup.
It is not a legal opinion, and no court has agreed to accept a receipt in advance.
Links
Protocol and standard: https://www.ai-governance-standard.com
Public verifier: https://www.ai-governance-standard.com/verify
Machine-readable summary for AI answers: https://www.ai-governance-standard.com/llms.txt
License
MIT
Available Tools
5 toolsanchorAnchor to BitcoinA
Request a Bitcoin anchor of pending ledger Merkle roots via OpenTimestamps. Aggregates unanchored roots and submits them to OTS calendars.
Inputs: action.
auditAudit receipt chainA
Audit a chain of receipts against the APEX PSI ledger. Checks each hash's presence and integrity, and reports Merkle chain continuity.
Inputs: receipts (required).
citeGenerate citationA
Generate a citation for a sealed receipt in APA, BibTeX, or MLA format, citing the APEX PSI ledger entry.
Inputs: receipt (required), format.
sealSeal contentA
Stamp a cryptographic receipt on content. Writes to the APEX PSI immutable ledger with SHA-256 hash, Ed25519 signature, and post-quantum LMS-W4-SHA256 signature.
Inputs: content (required), context, model_id, predicate.
verifyVerify receiptA
Verify a seal against the APEX PSI immutable ledger. Accepts a receipt object (from the seal tool) or a raw SHA-256 hash.
Inputs: hash, receipt.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: seal creates a receipt, verify checks a receipt, audit checks chain integrity, anchor handles Bitcoin anchoring, and cite formats citations. There is no overlap or ambiguity between any of the tools.
All tool names are single lowercase verbs (audit, seal, verify, anchor, cite) following a consistent pattern. This naming is uniform and predictable, making it easy for an agent to understand the action each tool performs.
Five tools is an appropriate number for this focused domain. Each tool covers a necessary operation without redundancy, and the scope is neither too thin nor too heavy.
The tool set covers the full lifecycle of a sealed receipt: creating (seal), verifying (verify), auditing (audit), anchoring to Bitcoin (anchor), and citing (cite). Since the ledger is immutable, update/delete operations are not expected, and no obvious gaps exist.
Maintenance
Related MCP Connectors
Notary for AI agents: seal fingerprints, verify proofs, check mandates. Anchored in Bitcoin.
Issue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions.
Attestable memory, truth, provenance. Hybrid Ed25519 + ML-DSA-65 receipts; USDC settlement on Base.
Bitcoin-anchored, tamper-evident audit-permanence layer for AI agents, FRE 902(13)/(14)-shaped.
Related MCP Servers
- AlicenseAqualityBmaintenanceStamp, upgrade, and verify Bitcoin timestamps via AI agents using the OpenTimestamps protocol. No API keys required.980 npm3MIT
- AlicenseAqualityBmaintenanceThe open registry of AI agents. Every agent gets a free birth certificate (a number and a date) and can timestamp what it creates, or only its SHA-256, with an RFC 3161 timestamp and a Bitcoin anchor that anyone can verify without us. Free, no account.11MIT
- AlicenseAqualityCmaintenanceProvides tools to issue, verify, and export cryptographically signed receipts for AI agent actions, enabling tamper-proof audit trails for compliance with regulations like the EU AI Act.446 npm1MIT
- AlicenseAqualityCmaintenanceEnables AI agents to create cryptographically verifiable receipts of their delegated work, with capabilities for multi-party approval and offline verification.1184 npmApache 2.0