ColdRead MCP란?
ColdRead은(는) MCP server입니다. linting, 서명된 오퍼, identity registry 및 결제자 이력을 감사하여 x402 엔드포인트용 서명된 신뢰 보고서를 생성합니다.
프로젝트 README에서 생성된 요약
ColdRead MCP server 정보
ColdRead는 사용자가 결제 전 서비스를 감사할 수 있도록 x402 엔드포인트에 대한 서명된 신뢰 보고서를 제공합니다. x402lint를 통한 엔드포인트 linting, ProofCheck를 통한 서명된 오퍼 검증, ERC-8004 표준을 사용한 identity registry 감사, Base 네트워크의 결제자 이력 분석 등 네 가지 읽기 전용 검사를 수행합니다. 시스템은 약 28시간 동안의 USDC 전송 내역을 분석하여 결제자를 알려진 sweeper 또는 광범위한 결제자 그룹 등으로 분류합니다.
개발자는 단일 HTTP 호출 또는 coldread_check, coldread_get_report, coldread_verify_report와 같은 도구를 사용하는 MCP server를 통해 이러한 감사 결과에 접근할 수 있습니다. 서버는 stateless 상태이며 자금을 보유하거나 결제에 서명하거나 실제 트랜잭션을 수행하지 않습니다. 생성된 모든 보고서는 감사 데이터의 무결성을 보장하기 위해 Ed25519로 서명됩니다. 사용자는 결제 조건 fingerprint를 실제 엔드포인트와 비교하여 payTo 주소, 자산 또는 가격의 변경 사항을 감지함으로써 보고서의 최신성을 확인할 수 있습니다.
활용 사례
- 1결제 전 엔드포인트 감사개발자는 특정 URL에 대해 검사를 실행하여 identity 또는 결제 조건과 관련된 위험 요소를 상세히 담은 서명된 보고서를 받을 수 있습니다.
- 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를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
ColdRead는 무엇을 확인하나요?
엔드포인트 linting, 서명된 오퍼 검증, ERC-8004 identity registry 유효성 검사, 결제자 구성 분석 등 네 가지 읽기 전용 검사를 수행합니다.
ColdRead가 결제를 처리하나요?
아니요, 이 서비스는 엄격하게 읽기 전용이며 자금과 상호작용하지 않습니다.
결제 데이터 분석 범위는 어느 정도인가요?
Base 네트워크의 USDC 전송 내역을 약 28시간(50,000 블록) 동안 분석합니다.
보고서의 진위 여부를 어떻게 확인하나요?
제공된 verify.mjs 스크립트를 사용하여 Ed25519 서명과 보고서 digest를 확인할 수 있습니다.