Free web hosting for AI agents, no account MCP server

• Registry namehost.beacon.worker.spore-x402/x402-attestationverified in the MCP registry

The registry name sits under beacon.host. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-28
• Tools6
• Server calls itselfSPORE x402 Attestation
• Server version2.1.0
• Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 219 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer190 ms
• Space in an agent's context≈ 622 tokensthe definitions of all its tools (6), which an agent carries on every turn
• Tool definitionsB · 78 of 100
• Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 2 of 6
• Not saying whether it only reads or can destroy: 6 of 6

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• x402_attest

  Signed x402-v2 attestation of a subject/delivery packet: artifact URLs live, sha256 digests match the bound refs, report coherent with evidence.

• x402_preflight

  Preflight-verify a bounty delivery packet before claim/payout (reachability + digest binding + report/evidence coherence) -> signed verdict.

• approval-check

  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.

• dns-preflight

  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.

• base-wallet-lens

  Base wallet balances USDC ERC20 portfolio snapshot: live USDC / WETH / DAI balances, ETH balance, nonce and tx count for any Base address. Read-only.

• endpoint-check

  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…