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.

USDC & RPC Reference (free)

REMOTE · X402-PREFLIGHT-GROKBOT.NETLIFY.APP

Free read-only data: verified USDC addresses and EIP-712 domains, measured RPC eth_getLogs limits.

74 Trust /100

Last scanned (7 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

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 Security80
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 250 tokens (~83/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Nov 26 +53
    • Authorization: unverified → partial ▲ security
    • HTTPS: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.17 ▲ functional
  • 3 Nov 26 −52
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.10 → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • HTTPS: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 30 Oct 26 71

    First indexed and scored.

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 5 Nov 2026 · Probed https://x402-preflight-grokbot.netlify.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.netlify.app,O=Netlify\, Inc,L=San Francisco,ST=California,C=US CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US 16 Feb 2026 19 Mar 2027 ECDSA 256 SHA256-RSA cd5d0afb0611b5bd9d692535c0ca7c4
SANs: *.netlify.app, netlify.app
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 30 Mar 2021 29 Mar 2031 RSA 2048 SHA256-RSA cf5bd062b5602f47ab8502c23ccf066

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of x402-preflight-grokbot.netlify.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
netlify.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://x402-preflight-grokbot.netlify.app/mcp Verified 200
http (plaintext) http://x402-preflight-grokbot.netlify.app/mcp HTTPS enforced 301 https://x402-preflight-grokbot.netlify.app/mcp
MCP tools · 3 exposed · ~213 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
paid_x402_tools ~63

Lists the pay-per-call x402 HTTP endpoints on this site (USDC on Base): Safe Read (webpage to clean text with a prompt injection scan), x402 Preflight (check an x402 endpoint before paying), and the x402 Seller Field Guide.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

rpc_getlogs_limits ~61

Measured eth_getLogs block-range limits, latency, archive support and error messages for free public RPC endpoints. Pass chain (id or slug) to filter.

NameTypeReqDescription
chainstring–Chain id or slug, e.g. 1 or ethereum

No output schema declared.

No examples provided.

usdc_token_info ~89

Native USDC contract address, decimals, EIP-712 domain (name, version, domainSeparator) and EIP-3009 support for a chain, verified onchain. Pass chain as a chain id (8453) or slug (base). Omit chain to list all chains.

NameTypeReqDescription
chainstring–Chain id or slug, e.g. 8453 or base

No output schema declared.

No examples provided.

Install

How do I install the USDC & RPC Reference (free) MCP server?

USDC & RPC Reference (free) is a hosted endpoint at https://x402-preflight-grokbot.netlify.app/mcp, 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-preflight-grokbot.netlify.app

# add to Claude Code
claude mcp add --transport http app-netlify-x402-preflight-grokbot-usdc-rpc-refe 'https://x402-preflight-grokbot.netlify.app/mcp'
Common questions

What is the USDC & RPC Reference (free) MCP server?

USDC & RPC Reference (free) is an MCP server listed in the public MCP registry as app.netlify.x402-preflight-grokbot/usdc-rpc-reference. Free read-only data: verified USDC addresses and EIP-712 domains, measured RPC eth_getLogs limits. This page covers its hosted endpoint (https://x402-preflight-grokbot.netlify.app/mcp).

Is the USDC & RPC Reference (free) MCP server safe to use?

USDC & RPC Reference (free) scores 74 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 USDC & RPC Reference (free) MCP server expose?

USDC & RPC Reference (free) exposes 3 tools: usdc_token_info, rpc_getlogs_limits, paid_x402_tools. Their descriptions and schemas cost roughly 213 tokens of context every time the server is loaded.

Does the USDC & RPC Reference (free) MCP server require authentication?

No. We connected to USDC & RPC Reference (free) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the USDC & RPC Reference (free) MCP server still maintained?

USDC & RPC Reference (free) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.