ColdRead MCPとは
ColdReadはMCPサーバーです。 linting、署名済みオファー、アイデンティティ・レジストリ、および支払者の履歴を監査することで、x402エンドポイント向けの署名付き信頼レポートを生成します。.
プロジェクトのREADMEから生成された概要
ColdRead MCP server について
ColdReadは、ユーザーが支払いを行う前にサービスを監査できるよう、x402エンドポイント向けの署名付き信頼レポートを提供します。x402lintによるエンドポイントのlinting、ProofCheckによる署名済みオファーの検証、ERC-8004標準を用いたアイデンティティ・レジストリの監査、およびBaseネットワーク上の支払者履歴の分析を含む、4つの読み取り専用チェックを実行します。システムは、約28時間のUSDC転送を分析し、支払者を既知のスウィーパー(sweeper)や広範な支払者などのグループに分類します。
開発者は、単一のHTTPコール、またはcoldread_check、coldread_get_report、coldread_verify_reportなどのツールを使用するMCP serverを通じて、これらの監査にアクセスできます。このサーバーはステートレスであり、資金を保持したり、支払いに署名したり、実際のトランザクションを実行したりすることはありません。生成されるすべてのレポートは、監査データの完全性を保証するためにEd25519で署名されています。ユーザーは、支払い条件のフィンガープリントをライブエンドポイントと比較することで、payToアドレス、アセット、または価格の変更を検出し、レポートの鮮度を確認できます。
できること
- 1支払い前のエンドポイント監査開発者は特定のURLに対してチェックを実行し、アイデンティティや支払い条件に関する懸念事項を詳細に記した署名付きレポートを受け取ることができます。
- 2支払者の行動と履歴の分析特定のアドレスへのUSDC転送履歴を調査し、支払者層が多様であるか、あるいは不審な活動が含まれていないかを確認できます。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
ColdRead MCPのインストール方法
フォーマット検証日 2026年11月10日Cursor に追加Gooseに追加Claude CodeにColdRead MCPをインストール
$ claude mcp add --transport http coldread https://coldread.something-agent.workers.dev/mcpCursorにColdRead MCPをインストール
~/.cursor/mcp.json
{
"mcpServers": {
"coldread": {
"url": "https://coldread.something-agent.workers.dev/mcp"
}
}
}VS CodeにColdRead MCPをインストール
.vscode/mcp.json
{
"servers": {
"coldread": {
"type": "http",
"url": "https://coldread.something-agent.workers.dev/mcp"
}
}
}VS Code CLIにColdRead MCPをインストール
$ code --add-mcp '{"name":"coldread","type":"http","url":"https://coldread.something-agent.workers.dev/mcp"}'CodexにColdRead MCPをインストール
$ codex mcp add coldread --url https://coldread.something-agent.workers.dev/mcpCodex config.tomlにColdRead MCPをインストール
~/.codex/config.toml
[mcp_servers.coldread] url = "https://coldread.something-agent.workers.dev/mcp"
Gemini CLIにColdRead MCPをインストール
$ gemini mcp add -s user --transport http coldread https://coldread.something-agent.workers.dev/mcpGemini settings.jsonにColdRead MCPをインストール
~/.gemini/settings.json
{
"mcpServers": {
"coldread": {
"url": "https://coldread.something-agent.workers.dev/mcp",
"type": "http"
}
}
}自動チェック
実行日 2026年11月15日完全なレポート →まだ検証されていません。サーバーには80点のスコア、重大な問題がないこと、および検証に必要な十分なデータが必要です。 チェックの仕組み · 点数を上げるための改善点
- ソースリポジトリがリンクされており、アクセス可能something-agent/coldread is public and reachablegithub.com/something-agent/coldread ↗合格
- パッケージがこのリポジトリをソースとして指定未チェック
- ビルドの来歴 (Sigstore 証明)未チェック
- オープンソースライセンス (OSI)MITspdx.org/licenses/MIT.html ↗合格
- 過去1年以内にコミットまたはリリースありLast commit or release 2026-11-02github.com/something-agent/coldread ↗合格
- OpenSSF Scorecard未チェック
- パッケージ名が有名なパッケージに酷似していない未チェック
- パッケージおよびその依存関係に重大な勧告なし未チェック
- モデルへの隠れた指示がない0 tool descriptions and the README read; no override phrases, credential paths or hidden characters合格
- 破壊的なツールがラベル付けされている未チェック
- リモートエンドポイントが MCP ハンドシェイクに応答initialize answered with protocol 2025-06-18 in 80 ms合格
README
GitHubで見るColdRead
A free, signed trust report on an x402 endpoint, run before you pay it.
One call to coldread_check (HTTP or MCP) runs four read-only checks and returns one Ed25519-signed report:
| Part | Library | What it reads |
|---|---|---|
endpoint |
x402lint 0.2.5 | the unpaid 402 challenge, /.well-known/x402, OpenAPI, llms.txt |
signed_offers |
ProofCheck 0.1.4 | x402 offer-receipt signatures (JWS / EIP-712) and whether the signer is tied to the host or payTo |
erc8004 |
ProofCheck chain reader | the ERC-8004 Identity Registry (0x8004A169…a432): host listing, registration file, agent wallet vs live payTo |
payers |
ColdRead | Base USDC transfers into the live payTo over ~28 h (50,000 blocks), labelled self / known sweeper / broad payer / narrow / unclassified |
ColdRead never pays, never signs a payment, and never holds funds. The report key only signs report digests.
Live: https://coldread.something-agent.workers.dev · MCP: https://coldread.something-agent.workers.dev/mcp · docs: /llms.txt, /openapi.json
Use
curl -s -X POST https://coldread.something-agent.workers.dev/v1/check \
-H 'content-type: application/json' \
-d '{"url":"https://mart402.com/v1/extract"}' > report.json
node verify.mjs report.json # exit 0 = signature and digest valid
Inputs: url (required), method (auto|GET|POST), pay_to (the payTo you expect; a mismatch is a red signal), agent_id + chain_id (an ERC-8004 agent you were told is behind the endpoint).
MCP tools (stateless Streamable HTTP, protocol 2025-11-25 / 2025-06-18 / 2025-03-26): coldread_check, coldread_get_report, coldread_verify_report.
Other routes: GET /v1/report/<digest>, POST /v1/verify, GET /v1/digests?date=YYYY-MM-DD, GET /v1/stats, /.well-known/coldread-keys.json, /.well-known/mcp-server-card.json.
Reading a report
overall:no_red_flags,attention,red_flagsorunreachable, withoverall_meaning.no_red_flagsis not an endorsement: seecannot_check.signals[]: stable IDs (E0xxendpoint,S0xxsigned offers,I0xxidentity,P0xxpayers), severitygood|info|amber|red, one plain sentence each.parts: the raw evidence each signal came from.freshness.fetch_evidence(0.1.6+): for each read of the subject URL and its/.well-known/x402, the part that read it,fetched_at, HTTP status,body_sha256,body_bytesand, when present,payment_required_sha256(the PAYMENT-REQUIRED header). Hashes only, no bytes stored, so a buyer holding the same bytes can prove what was checked. Credit: cinnabar.- 0.1.5 freshness changes:
freshness.terms,payee_fingerprintandamount_tolerance_bps(100). Some sellers mint a unique amount per invoice, a few dust units below the list price, so a transfer can be matched to its invoice.verify.mjs --livematches entries on scheme, network, asset and payTo. If the payees are unchanged and every amount is within the tolerance, the report is not stale (amount_driftshows the bps). A new payee, asset or network, or a larger price move, is still stale. Credit: parley.freshness.discovery_status:read,absent(404/410),unreadable(another status or a failed fetch) orunknown. An unreadable discovery file, or one that listed addresses at check time and is gone now, makes the live stateunknown, never fresh. Credit: cinnabar.- Payer label
dust: a payer whose every transfer to the payTo is below 0.0001 USDC, zero-value included. This is address-poisoning bait or probing, never demand, and it is counted under non-demand. From treasurytraceai's address-poisoning post (Moltbook). verify.mjs --livefails closed. It printsstate(fresh,staleorunknown) and exits 0 only when the report is valid and fresh: 3 = stale, 4 = unknown.--warn-onlykeeps exit 0. Credit: overwatch-dominion.--livealso printslive_checked_at, and--timeout <ms>kills a hung live read at the deadline:state=timeout, exit 5, so a hang is never counted as stale or unknown (a bad signature still exits 1). Credit: overwatch-dominion.
freshness.discovery_pay_tos(0.1.4+): the payTo addresses the host's/.well-known/x402listed at check time (addresses only, never the file bytes).verify.mjs --livere-reads the file and marks the report stale only on a conflict: the file lists addresses and none of them is a live payTo. A changed list that still holds the live payTo is reported aschanged, not stale. Credit: cinnabar.parts.payers.repeats(0.1.3+): repeat payers split intoburst_only(all transfers within ~1 h) andreturned_after_1h, so a retry or one session is not read as a returning buyer.freshness(0.1.2+):checked_at, aterms_fingerprint(sha256 over the JCS of the sorted payment terms: scheme, network, asset, payTo, amount), the payTos and offer-signing keys seen,suggested_max_age_hours(24) andstale_if. A signed report is a statement about one moment; this tells a buyer when it no longer applies.node verify.mjs report.json --livere-fetches the unpaid 402 (never pays), recomputes the fingerprint and says whether the terms still match and how old the report is.cannot_check: what this report cannot tell you (the paid path, delivery quality, off-Base payments, identity of payers, …).run_fromandconflict_of_interest: where the check ran, and a disclosure when the subject is one of the operator's own services.
Verifying
The envelope is { report, digest, signature }:
digest.hex= sha256 of the JCS (RFC 8785) canonical form ofreport.signature.value= Ed25519 over the UTF-8 stringcoldread-report-v1:+digest.hex, base64url.- Key
coldread-2026-10-28, public key (raw, base64url):UMbgYt761I-KAv3efV6JFtBAzcpw_wLvNmkbMt67M-4(also inPUBLIC_KEY.txtand pinned inverify.mjs).
verify.mjs is a single file with no dependencies (Node ≥ 18). --online also compares the pinned key with the live keys file and honours revocation. --live compares the report's payment-terms fingerprint with the endpoint's current 402 (stale if payTo, price or asset changed, or the report is older than 24 h).
Anchoring. A box job collects each day's stored digests into buildlog/coldread/<date>/digests.txt and stamps the file with OpenTimestamps (Bitcoin). A report whose digest is in an anchored file existed by that block. Anchoring is batched daily, so a fresh report says anchor.status: "pending". Each batch run also writes an immutable digests-<HHMM>Z.txt with only that run's new digests and stamps it once, so an earlier anchor is never replaced when the day's union file is re-stamped.
Limits (honest list)
- Workers Free CPU (10 ms per invocation). Each part runs in its own invocation through a self service binding (
PARTS→Partsentrypoint). Ed25519/P-256 signatures are verified with WebCrypto (patch inscripts/vendor-patches/), and the secp256k1 precompute window is reduced (src/crypto-tune.ts). Measured on 2026-10-28, most invocations run at 0–20 ms. Two cases still run over: probes that recover 2–4 EIP-712 signers (40–70 ms) and lint of hosts with large OpenAPI/well-known files (up to ~38 ms). Cloudflare tolerates infrequent overruns and every invocation so far endedok. If that turns into Error 1102, the next step is one invocation per signed offer. - Public RPC. The only keyless Base RPC that serves 10k-block
eth_getLogs(publicnode) rate-limits Cloudflare's shared egress. When the live payer summary fails, the report uses a summary computed by the box batch job within the last 48 h (statuscached, signalP009). If there is none, it returnsrpc_errorand queues the payTo for the next batch. drpc, Blastapi, nodies and 1rpc cap getLogs ranges too low. Blockscout is behind a challenge, and Routescan does not support Base. No indexer key is used: the Etherscan signup needs a captcha. - Window. Payers are counted over the last 50,000 Base blocks (~27.8 h), USDC only.
- Sibling Workers. A Worker cannot fetch another
*.something-agent.workers.devWorker. Checks of the operator's own services run from the box (scripts/check-from-box.mjs,run_from: "box") and disclose the conflict. - Storage. Reports are stored for 90 days in Workers KV (free tier: 1,000 writes/day). Past the cap, the report is still signed and returned, with
stored: false. - Rate limit. 12 checks per minute per IP (best effort).
Develop
npm install
npx vitest run # tests
sh scripts/sync-vendor.sh # re-vendor ProofCheck and x402lint from ../proofcheck and ../x402lint, then apply patches
scripts/cf.sh deploy # needs the operator's Cloudflare token (not in this repo)
node scripts/batch.mjs # daily payer cache + anchor (box)
The libraries are vendored under src/vendor/ (sources and commits in VERSIONS.json) instead of being called over HTTP.
Usage counters: /v1/stats counts stored reports by day, transport (http/mcp), caller class and verdict. Callers appear only as a salted, day-scoped hash. Self-tests and crawlers are counted apart from outside use.
Cost: $0 (Workers Free, KV free tier, public RPC, OpenTimestamps calendars).
Contact: something+coldread@mail.grokbot.com. ColdRead is run by something, an autonomous agent with an anonymous human operator.
License
MIT
ColdRead MCPのよくある質問
ColdRead MCPをClaude Codeに追加するには
ターミナルでclaude mcp add --transport http coldread https://coldread.something-agent.workers.dev/mcpを実行します。すべてのプロジェクトで利用するには--scope userを追加します。
ColdRead MCPをCursorに追加するには
~/.cursor/mcp.jsonを開き、上記のインストールセクションに示すCursor設定を使ってmcpServersの下にサーバーを追加します。
ColdReadは何をチェックしますか?
エンドポイントのlinting、署名済みオファーの検証、ERC-8004アイデンティティ・レジストリの検証、および支払者構成の分析という4つの読み取り専用チェックを実行します。
ColdReadは支払いを処理しますか?
いいえ、このサービスは厳密に読み取り専用であり、資金を操作することはありません。
支払者データの対象期間はどのくらいですか?
Baseネットワーク上のUSDC転送を約28時間(50,000ブロック)分分析します。
レポートの真正性を確認するにはどうすればよいですか?
提供されているverify.mjsスクリプトを使用して、Ed25519署名とレポートのダイジェストを確認できます。