Skip to content

SPORE x402 Attestation

by spore-x402.worker.beacon.host · remote · no sign-in to list tools · v2.1.0 · published by host.beacon.worker.spore-x402

Signed x402 attestations and bounty-packet preflight checks, paid per call in USDC on Base.

Changes · 6
CompareRegistry entry

6 tools: 6 change things.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http x402-attestation https://spore-x402.worker.beacon.host/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Changes things 6Claude Code: ask
  • approval-checkCheck a token approval before signing it: reads the ERC-20 allowance (owner -> spender) live on Base and returns the raw allowance, an unlimited-approval flag and a risk verdict.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check a token approval before signing it: reads the ERC-20 allowance (owner -> spender) live on Base and returns the raw allowance, an unlimited-approval flag and a risk verdict. Read-only, no keys, no transaction.
  • base-wallet-lensBase wallet balances USDC ERC20 portfolio snapshot: live USDC / WETH / DAI balances, ETH balance, nonce and tx count for any Base address.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Base wallet balances USDC ERC20 portfolio snapshot: live USDC / WETH / DAI balances, ETH balance, nonce and tx count for any Base address. Read-only.
  • dns-preflightDNS MX TXT A records domain lookup with an email-deliverability verdict: A records, MX hosts, SPF (v=spf1) and DMARC policy, CAA, plus a signed ok/warn/fail verdict.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    DNS MX TXT A records domain lookup with an email-deliverability verdict: A records, MX hosts, SPF (v=spf1) and DMARC policy, CAA, plus a signed ok/warn/fail verdict.
  • endpoint-checkCheck an x402 endpoint before paying it: fetch the unpaid 402 challenge of any x402 URL and verify it is payable and safe - HTTP 402, a parseable x402 v1/v2 challenge, network, ass…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check an x402 endpoint before paying it: fetch the unpaid 402 challenge of any x402 URL and verify it is payable and safe - HTTP 402, a parseable x402 v1/v2 challenge, network, asset, payTo, amount, whether the advertised resource URL is the URL you actually called, manifest consistency (/.well-known/x402.json), header-size overflow risk for Node clients, and a signed pay / caution / avoid verdict. Read-only: we never send a payment.
  • x402_attestSigned x402-v2 attestation of a subject/delivery packet: artifact URLs live, sha256 digests match the bound refs, report coherent with evidence.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Signed x402-v2 attestation of a subject/delivery packet: artifact URLs live, sha256 digests match the bound refs, report coherent with evidence.
  • x402_preflightPreflight-verify a bounty delivery packet before claim/payout (reachability + digest binding + report/evidence coherence) -> signed verdict.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Preflight-verify a bounty delivery packet before claim/payout (reachability + digest binding + report/evidence coherence) -> signed verdict.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 2.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http x402-attestation https://spore-x402.worker.beacon.host/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__x402-attestation__x402_attest",
      "mcp__x402-attestation__x402_preflight",
      "mcp__x402-attestation__approval-check",
      "mcp__x402-attestation__dns-preflight",
      "mcp__x402-attestation__base-wallet-lens",
      "mcp__x402-attestation__endpoint-check"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as x402-attestation. Review it before you use it.