Time your agents can prove.
Clockchain MCP gives any AI agent consensus-anchored time, tamper-evident receipts, and on-chain verification. 31 tools across six modules, one endpoint.
Six modules
Every tool is typed, idempotent where it writes, and degrades with grace.
Time
Consensus block time and height. The network's consented clock, not a single server's. Provable after the fact.
Notarization
Anchor any hash to an append-only ledger, then verify it against the immutable on-chain block.
Scheduler
Time-triggered smart contracts. Non-custodial: the caller's wallet signs, the server holds no key.
Audit
Audit trails, compliance reports (EU AI Act Art. 12, SEC 17a-4, ISO 27001), and portable evidence packages.
Agent identity
Attest agent actions into self-verifying receipts; resolve and verify identity valid at a point in time.
Commitments
Issue, checkpoint, attest, settle. Every commitment's outcome, kept or broken, on the record.
Why it holds up
- Consensus time. Every timestamp is the network's consented block time. Anyone can re-check it, no single clock to trust.
- Self-verifying receipts. A receipt carries its own payload and anchor. Recompute the hash, compare to the on-chain block. Proof, not a screenshot.
- Tamper-evident. Change one byte and verification fails. The ledger is append-only, the immutable block is authoritative.
Install
Hosted endpoint. Connect any MCP client in under a minute.
1 · Get a testnet token
Mint an instant testnet token (delegated, writes spend testnet credits), or bring your own Clockchain API key.
2 · Add the server, any MCP client
The config block is identical everywhere: Claude Code, Cursor, Claude Desktop, Codex.
{
"mcpServers": {
"clockchain": {
"type": "http",
"url": "https://mcp.clockchain.network/mcp",
"headers": { "x-api-key": "<YOUR_TOKEN>" }
}
}
}CLI shortcut where one works (Claude Code):
claude mcp add clockchain --transport http https://mcp.clockchain.network/mcp \
--header "x-api-key: <YOUR_TOKEN>"3 · Verify
Open a new session, run /mcp (you should see clockchain with all 31 tools), then ask: "use clockchain to get the current consensus time."
Health & status
Liveness: GET mcp.clockchain.network/health, no auth. Live status and the capability catalog sit in the app's Live Benchmarking view.
Presently recorded on a single-validator testnet: the event hash, on-chain anchor, and consensus timestamp are real and independently verifiable. Multi-validator supermajority attestation activates at mainnet.