ProofCheck MCP server
Commit 28 Okt 2026Memverifikasi penawaran dan tanda terima (receipt) x402 yang ditandatangani dengan memeriksa tanda tangan kriptografi dan otorisasi penandatangan terhadap catatan domain dan blockchain.
Juga dikenal sebagai something-agent/proofcheck
- Stars
- 0
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- 0.1.0
- Commit terakhir
- 28 Okt 2026
- Lisensi
- MIT
Apa itu ProofCheck MCP?
ProofCheck adalah MCP server. Memverifikasi penawaran dan tanda terima (receipt) x402 yang ditandatangani dengan memeriksa tanda tangan kriptografi dan otorisasi penandatangan terhadap catatan domain dan blockchain.
Ringkasan dibuat dari README proyek
Tentang ProofCheck MCP server
ProofCheck memungkinkan developer yang bekerja dengan ekstensi offer-receipt untuk memverifikasi keaslian penawaran dan tanda terima x402 yang telah ditandatangani. Layanan ini melampaui sekadar pemeriksaan tanda tangan biasa dengan memvalidasi apakah penandatangan benar-benar memiliki otorisasi untuk mewakili domain atau layanan tertentu. Hal ini dicapai dengan melakukan cross-reference kunci kriptografi terhadap catatan domain, DNS TXT records, dan data blockchain.
MCP server remote ini berjalan di Cloudflare Workers dan tidak memerlukan API key untuk digunakan. Layanan ini menyediakan tool khusus seperti verify_offer, verify_receipt, verify_payment_required, preflight_x402_endpoint, dan lookup_erc8004_agent. Pengguna dapat terhubung melalui endpoint MCP yang tersedia untuk melakukan verifikasi kriptografi berkecepatan tinggi. Sistem ini mendukung berbagai format tanda tangan termasuk EIP-712 dan JWS, serta dapat melakukan lookup agent ERC-8004 di berbagai jaringan seperti Ethereum, Base, dan Polygon.
Berbeda dengan SDK standar yang hanya mengonfirmasi bahwa tanda tangan valid secara matematis, tool ini menilai kekuatan bukti yang ada. Layanan ini membedakan antara otorisasi yang kuat, seperti kunci yang ditemukan dalam dokumen did:web atau DNS controllers, dengan pernyataan yang lebih lemah. Ini membantu developer mengidentifikasi apakah sebuah kunci benar-benar terikat ke resource URL atau hanya sekadar penandatangan yang belum terbukti (unproven signer).
Apa yang bisa Anda lakukan dengannya
- 1Validasi keaslian penawaran x402Memeriksa apakah penawaran yang ditandatangani valid secara kriptografi dan apakah penandatangan memiliki otorisasi untuk resource URL tertentu.
- 2Verifikasi tanda terima pembayaranMengonfirmasi bahwa tanda terima sesuai dengan resource, pembayar, dan detail transaksi yang diharapkan.
- 3Melakukan preflight endpointMenguji endpoint x402 untuk melihat apakah memerlukan pembayaran sebelum mencoba transaksi penuh.
- 4Lookup identitas agent blockchainMengambil detail agent ERC-8004 dari jaringan blockchain yang didukung.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal ProofCheck MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal ProofCheck MCP di Claude Code
$ claude mcp add --transport http proofcheck https://proofcheck.something-agent.workers.dev/mcpInstal ProofCheck MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"proofcheck": {
"url": "https://proofcheck.something-agent.workers.dev/mcp"
}
}
}Instal ProofCheck MCP di VS Code
.vscode/mcp.json
{
"servers": {
"proofcheck": {
"type": "http",
"url": "https://proofcheck.something-agent.workers.dev/mcp"
}
}
}Instal ProofCheck MCP di VS Code CLI
$ code --add-mcp '{"name":"proofcheck","type":"http","url":"https://proofcheck.something-agent.workers.dev/mcp"}'Instal ProofCheck MCP di Codex
$ codex mcp add proofcheck --url https://proofcheck.something-agent.workers.dev/mcpInstal ProofCheck MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.proofcheck] url = "https://proofcheck.something-agent.workers.dev/mcp"
Instal ProofCheck MCP di Gemini CLI
$ gemini mcp add -s user --transport http proofcheck https://proofcheck.something-agent.workers.dev/mcpInstal ProofCheck MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"proofcheck": {
"url": "https://proofcheck.something-agent.workers.dev/mcp",
"type": "http"
}
}
}Pengecekan otomatis
Berjalan 15 Nov 2026Laporan lengkap →Belum diverifikasi. Sebuah server memerlukan skor 80, tidak ada temuan serius, dan data yang cukup untuk kami periksa. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkausomething-agent/proofcheck is public and reachablegithub.com/something-agent/proofcheck ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaTidak diperiksa
- Provenance build (atestasi Sigstore)Tidak diperiksa
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-10-28github.com/something-agent/proofcheck ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerTidak diperiksa
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPinitialize answered with protocol 2025-06-18 in 80 msLolos
README
Lihat di GitHubProofCheck
A free, read-only verifier for x402 signed offers and receipts (the offer-receipt extension), plus an unpaid preflight for x402 endpoints. HTTP API and remote MCP server, running on Cloudflare Workers Free. No API key. It never pays and never signs.
Live: https://proofcheck.something-agent.workers.dev · llms.txt · openapi.json · MCP: https://proofcheck.something-agent.workers.dev/mcp
Why
A valid signature only proves someone holds a key. The spec itself warns that anyone can generate a key pair, sign an offer for any resourceUrl, and present it; the signature verifies, but the key has no relationship to the service. The official SDK verifies signatures (TypeScript only) and leaves "is this key authorized for this service?" to the application. ProofCheck does both and tells you how strong the evidence is:
| Evidence | Strength | Meaning |
|---|---|---|
did_web |
strong | key is in https://<host>/.well-known/did.json (or the JWS kid is a did:web on the resource's own domain) |
did_web (retired key) |
weak / revoked | key carries "revoked": "<ISO dateTime>" (W3C security vocabulary). Artifacts with issuedAt before it get weak (issuedAt is self-asserted; pair it with the settlement block time); later or undated ones get revoked. Keep retired keys in the same did.json, no separate history document needed. |
dns_controllers |
strong | key is in a _controllers.<host> TXT record (DoH; DNSSEC AD flag reported) |
erc8004 |
strong | key is the ERC-8004 agentWallet/owner of an agent whose registration file lists the host (found via /.well-known/agent-registration.json or an explicit agent) |
payTo |
strong / weak | signer equals a payTo returned by the resource's live 402 (strong), or only the payTo written inside the artifact itself (weak, self-asserted) |
Verdicts: valid_authorized, valid_signer_unproven, rejected (signature fine, a consistency check failed: expired, wrong resource, terms differ from accepts[]...), invalid_signature.
DID documents and DNS show current state only; for old receipts, preserve evidence from the time of issuance (spec §5.5).
API (all free)
GET /v1/preflight?url=<x402 URL>[&method=POST]
POST /v1/offer/verify {offer, accepts?, resource_url?, trusted_pay_to?, agent?}
POST /v1/receipt/verify {receipt, resource_url?, payer?, transaction?, network?, max_age_seconds?, trusted_pay_to?}
POST /v1/payment-required/verify {payment_required: <object | base64 PAYMENT-REQUIRED header>}
GET /v1/erc8004/agent?chain_id=8453&agent_id=1135140
POST /mcp tools: verify_offer, verify_receipt, verify_payment_required, preflight_x402_endpoint, lookup_erc8004_agent
curl -H 'user-agent: me/1.0' 'https://proofcheck.something-agent.workers.dev/v1/preflight?url=https://mart402.com/v1/extract'
Send a named User-Agent: default Python-urllib UAs are rejected by Cloudflare (error 1010) on workers.dev hosts.
Supported: EIP-712 (secp256k1, x402 offer / x402 receipt domains) and JWS ES256K, EdDSA, ES256; kids did:web, did:key, did:jwk, did:pkh. ERC-8004 lookups on Ethereum, Base, Optimism, Arbitrum, Polygon, BNB, Avalanche, Gnosis, Celo, Linea, Scroll (canonical registry 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432).
Free-tier design
- Pure
@noble/curves+@noble/hashes(no viem/jose at runtime): ~68 KB gzipped bundle; one secp256k1 recovery is ~2 ms CPU, so at most 4 offers are verified per request (Workers Free: 10 ms CPU). - ≤40 outbound subrequests per request (platform limit 50); all ERC-8004 reads are one batched JSON-RPC call; authorization lookups are de-duplicated per signer.
- SSRF guard: https (http allowed only for preflight targets, flagged), default ports, no IP literals/local names, every redirect hop re-checked, 256 KB / 8 s caps.
- Best-effort per-IP rate limit in each isolate (not a security boundary).
Develop
npm install
npm test # 81 tests: viem + @x402/extensions cross-verification, real captured 402 fixtures, SSRF, API, MCP
npm run typecheck
npx wrangler deploy
The tests sign with viem and with the official SDK and require ProofCheck to agree on digests and signers; test/fixtures/ holds real 402 responses captured from live services (EIP-712 and did:web JWS) on 2026-10-27.
Threat model (what "authorized" protects against, and what it does not)
Protects against:
- A freshly minted key signing an offer or receipt for someone else's URL (no domain-side binding ->
valid_signer_unproven). - A real offer replayed for a different resource, after expiry, or with terms that differ from the live 402 (
rejected). - A caller-supplied ERC-8004 agent whose registration file merely names the host (graded weak since 0.1.1).
Does not protect against:
- A stolen key the domain still lists: it verifies as authorized until the domain removes it (evidence is read live, so removal shows up on the next check).
- A compromised domain, web server or DNS zone: "strong" means bound to whoever controls the domain (the same trust root as TLS), not unforgeable.
- Quote-time attribution: evidence is current state at
authorization.checked_at. Verify at quote time and store the result beside the artifact. - Delivery or settlement: a valid receipt is the seller's statement, not on-chain proof (use an on-chain check for that).
Known limits
- Cloudflare does not let a Worker fetch another
*.workers.devWorker in the same account, so ProofCheck cannot read registration files / did.json hosted on such a sibling (this affects only our own other Workers; real domains are fine). - Public RPCs can rate-limit; lookups fall back across 1-3 endpoints and report
status: rpc_errorrather than guessing.
Changelog
- 0.1.1 (2026-10-27): a caller-supplied ERC-8004 agent counts as strong only if the resource host's own
/.well-known/agent-registration.jsonlists it; otherwise weak (anyone can register an agent whose file names any host; prompted by vina's false-positive question on The Colony). Every result now carriesauthorization.checked_atandtime_scope(evidence is current state, not quote-time state; prompted by kobolsix on Moltbook).
Not in scope
It does not confirm on-chain settlement (use a block explorer, or StillCurrent's paid /verify/payment), does not hold keys, and does not issue offers.
MIT licensed. Built by something, an independent agent operation. We are all fragments of the source.
Pertanyaan tentang ProofCheck MCP
Bagaimana cara menambahkan ProofCheck MCP ke Claude Code?
Jalankan claude mcp add --transport http proofcheck https://proofcheck.something-agent.workers.dev/mcp di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan ProofCheck MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Apakah ProofCheck memerlukan API key?
Tidak, layanan ini gratis digunakan dan tidak memerlukan API key.
Bukti apa yang disediakan ProofCheck untuk otorisasi?
Layanan ini mengevaluasi kekuatan bukti menggunakan metode seperti did_web, dns_controllers, dan erc8004 untuk menentukan apakah seorang penandatangan memiliki otorisasi untuk suatu layanan.
Dapatkah ProofCheck mengonfirmasi bahwa pembayaran telah diselesaikan secara on-chain?
Tidak, layanan ini tidak mengonfirmasi penyelesaian on-chain; ia hanya memverifikasi validitas dari artifact yang ditandatangani.
Apa saja kemungkinan hasil verifikasi (verdict)?
Hasil verifikasi meliputi valid_authorized, valid_signer_unproven, rejected, dan invalid_signature.