Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.scrape402/scrape402

REMOTE · X402.SHIZU.ME

Pay-per-call agent tools via x402 (USDC on Base): chat, prices, funding, RNG. No account or keys.

Available components

−86 this week 0 Trust /100

Last scanned (12 days ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 3 Nov 2026.

Category Crypto and Web3

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (2)

  • HTTPS
  • Transport

Checks we could not complete (9)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • DNSSEC in Endpoint SecurityDNSSEC not yet verified: we couldn't validate it against a resolver.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 10 Nov 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 9 Nov 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 8 Nov 26 −18

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 7 Nov 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 6 Nov 26 −17
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • DNSSEC: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 10 Nov 2026 · Probed https://x402.shizu.me/mcp/rpc

TLS unreached
DNSSEC inconclusive

Validation of x402.shizu.me. — Inconclusive

Zone DS Keys Algorithms Outcome
x402.shizu.me. Error no A/AAAA/CNAME RRset answered for the name
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://x402.shizu.me/mcp/rpc Unreachable
http (plaintext) http://x402.shizu.me/mcp/rpc HTTPS enforced
MCP tools · 5 exposed · ~295 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
catalog ~26

List every scrape402 tool and price, and how to pay. Free — no session required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

chat ~55

OpenAI-style chat completion (Claude Haiku), billed per token off-chain. Needs a prepaid session.

NameTypeReqDescription
max_tokensinteger––
messagesarrayyesOpenAI-style chat messages
temperaturenumber––

No output schema declared.

No examples provided.

crypto_price ~70

Real-time crypto spot price for a trading pair (e.g. BTC-USD). Pay per call via x402 ($0.003, USDC on Base), or 1 credit(s) with a prepaid session.

NameTypeReqDescription
pairstring–e.g. BTC-USD; default BTC-USD

No output schema declared.

No examples provided.

funding_rates ~62

Perpetual-swap funding rates; optional comma-separated coins filter. Pay per call via x402 ($0.003, USDC on Base), or 1 credit(s) with a prepaid session.

NameTypeReqDescription
coinsstring–e.g. BTC,ETH

No output schema declared.

No examples provided.

random ~82

Cryptographically-strong randomness: hex bytes plus an optional uniform integer in [min, max]. Pay per call via x402 ($0.003, USDC on Base), or 1 credit(s) with a prepaid session.

NameTypeReqDescription
bytesinteger–1-256, default 16
maxinteger––
mininteger––

No output schema declared.

No examples provided.

Install

How do I install the io.github.scrape402/scrape402 MCP server?

io.github.scrape402/scrape402 is a hosted endpoint at https://x402.shizu.me/mcp/rpc, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · x402.shizu.me

# add to Claude Code
claude mcp add --transport http scrape402-scrape402 'https://x402.shizu.me/mcp/rpc'
Common questions

What is the io.github.scrape402/scrape402 MCP server?

io.github.scrape402/scrape402 is an MCP server listed in the public MCP registry as io.github.scrape402/scrape402. Pay-per-call agent tools via x402 (USDC on Base): chat, prices, funding, RNG. No account or keys. This page covers its hosted endpoint (https://x402.shizu.me/mcp/rpc).

Is the io.github.scrape402/scrape402 MCP server safe to use?

io.github.scrape402/scrape402 scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.scrape402/scrape402 MCP server expose?

io.github.scrape402/scrape402 exposes 5 tools: random, crypto_price, funding_rates, chat, catalog. Their descriptions and schemas cost roughly 295 tokens of context every time the server is loaded.

Does the io.github.scrape402/scrape402 MCP server require authentication?

Its publisher declares no required credentials for io.github.scrape402/scrape402. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the io.github.scrape402/scrape402 MCP server still maintained?

io.github.scrape402/scrape402 has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.scrape402/scrape402 MCP server?

VerifyMCP ran 2 checks on io.github.scrape402/scrape402, covering HTTPS and Transport. 9 items could not be completed, a gap on our side rather than a finding about io.github.scrape402/scrape402: TLS certificate, Authorization, HSTS header, DNSSEC and 5 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.