exhibit402-mcp
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., "@exhibit402-mcp certify the current content of https://example.com"
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.
exhibit402-mcp
MCP server for exhibit402, a live x402-paid web-evidence service. It lets an agent pay USDC on Base to permanently certify what a public URL serves right now, and to re-verify existing certificates.
How a capture works: two independent observers on different networks capture the URL at the same frozen instant. Byte-identical captures get tier CERTIFIED. Differing captures get tier WITNESSED, with a pixel agreement percentage and a diff map. Either way the evidence (screenshot plus a signed manifest) is stored permanently on Arweave, an RFC 3161 timestamp token is included, and an ERC-721 certificate is minted on Base to the wallet that paid.
Machine-readable service docs: /llms.txt and /openapi.json.
Tools
Tool | What it does | Price (USDC on Base) |
| Pays for a capture, then polls the claim ticket until the certificate is final (up to about 6 minutes). Returns the certificate JSON: tier, token id, ar:// links, hashes. | $1.00 ( |
| Re-verifies any exhibit402 certificate: the service re-downloads the stored bytes, recomputes every SHA-256, and checks the on-chain record. Returns a machine-readable verdict. | $0.02 |
If certify_url hits its polling timeout, it still returns the claim_url. Claim tickets are durable and free to read: fetch the claim URL later with a plain GET to collect the finished certificate. You are not charged twice.
Refund policy (disclosed by the service): rejected captures (oversize, unreachable page, content screen) refund automatically minus a $0.10 fee; service faults refund in full. WITNESSED is a deliverable, not a failure, and is not refunded.
Related MCP server: bounty-mcp
Setup
You need one environment variable:
EXHIBIT402_WALLET_KEY: an EVM private key (hex) for a wallet that holds USDC on Base (chain id 8453). The wallet needs no ETH; x402 settles via EIP-3009 and the facilitator pays gas. The key stays in your process environment and is never logged.
Without the key the server still starts and lists its tools, and every call returns a clear setup error instead of failing silently.
Claude Code (one line)
claude mcp add exhibit402 --env EXHIBIT402_WALLET_KEY=0xYOUR_KEY -- npx -y exhibit402-mcpClaude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"exhibit402": {
"command": "npx",
"args": ["-y", "exhibit402-mcp"],
"env": { "EXHIBIT402_WALLET_KEY": "0xYOUR_KEY" }
}
}
}Cursor
Add to .cursor/mcp.json:
{
"mcpServers": {
"exhibit402": {
"command": "npx",
"args": ["-y", "exhibit402-mcp"],
"env": { "EXHIBIT402_WALLET_KEY": "0xYOUR_KEY" }
}
}
}Pricing summary
Action | Price |
Full-page capture | $1.00 |
Viewport capture (1280x800) | $0.50 |
Verify a certificate | $0.02 |
Rejected capture refund fee | $0.10 kept, rest refunded |
All payments are x402 (USDC on Base, eip155:8453). Payment settles before the capture starts; polling the claim ticket is free.
Notes for operators
EXHIBIT402_URLoverrides the service base URL (defaulthttps://exhibit402.dylan-caponi.workers.dev). You will not normally need it.Fulfillment is normally 30 to 120 seconds, up to about 5 minutes with a cold observer or a retry round.
A
verified: falseverdict fromverify_certificateis a delivered result and is charged. Malformed ids, unknown ids, and gateway outages are not charged.The service refuses private and internal addresses before payment.
License
MIT
Available Tools
2 toolscertify_urlCertify a URL (paid capture)A
Permanently certify what a public web page serves right now. Pays with x402 (USDC on Base): $1.00 for mode 'fullpage' (default, whole page) or $0.50 for mode 'viewport' (first 1280x800 screen). Two independent observers capture the URL at one frozen timestamp; matching captures are tier CERTIFIED, differing ones are WITNESSED (with pixel agreement percent and diff map). Evidence is stored permanently on Arweave and an ERC-721 certificate is minted on Base to the paying wallet. This tool polls the claim ticket for up to about 6 minutes (fulfillment is normally 30-120 seconds). If it times out, the returned claim_url is durable: fetch it later with a plain GET to collect the result. Rejected captures refund automatically minus a $0.10 fee; service faults refund in full.
Inputs: url (required), mode.
verify_certificateVerify a certificate (paid, $0.02)A
Re-verify any exhibit402 certificate for $0.02 (x402, USDC on Base). Pass the certificate's ERC-721 token id (digits), its Arweave manifest tx id (43 chars), or the exhibit402 job id (uuid). The service re-downloads the permanently stored screenshot and signed manifest, recomputes every SHA-256 from the actual bytes, and compares against the manifest and the on-chain record. Returns a machine-readable verdict: verified true/false plus per-check results (manifest_resolves, screenshot_hash, observer_agreement, onchain_sha256, rfc3161_timestamp). A false verdict is a delivered result and is charged; malformed ids, unknown ids, and gateway outages are not charged.
Inputs: id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools, certify_url and verify_certificate, have completely distinct purposes: one creates a certification, the other validates an existing one. There is no overlap or ambiguity in their functionality.
Both tool names follow a consistent verb_noun pattern (certify_url, verify_certificate), using clear, action-first naming that is predictable and readable.
With only 2 tools, the server feels minimal but is appropriate for its narrow focus on certification and verification. It falls into the borderline 'thin' range, yet the tools are purposeful and not redundant.
The core lifecycle of certification—creating and verifying—is covered. Minor gaps exist (e.g., no ability to list certificates or revoke them), but these are not essential for the primary workflow of certifying and checking authenticity.
Related MCP Connectors
Paid agent work and paid verification, settled in USDC. Verified outcomes get signed receipts.
Live uptime and source-URL verification for AI agents, with per-call x402/USDC paid endpoints.
Live uptime and source-URL verification for AI agents, with per-call x402/USDC paid endpoints.
Live uptime and source-URL verification for AI agents, with per-call x402/USDC paid endpoints.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables paid web-extraction tools for agents, settling each request in USDC on Base with no account or API key.653 npmMIT
- AlicenseAqualityCmaintenanceLets agents query anchored ground-level capture data, verify provenance, and commission new captures, paying per request in USDC on Base or Arc via x402.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to verify SHA-256 artifact digests and decode Base USDC transfer transactions, returning trustworthy PASS/PARTIAL/FAIL verdicts for paid API calls and deliverables.7 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to call pay-per-use web tools over Streamable HTTP—converting URLs to Markdown, extracting metadata and links, checking URL status, DNS, email domains, WHOIS, robots.txt, and generating domain reports—with per-call USDC payments on Base via x402 and no API keys.MIT