Tensorfeed X402 Base Mcp
@RipperMercs
Read-only Base mainnet chain reader for x402 payment verification. Confirms on-chain that a USDC settlement matches a claimed x402 receipt (recipient and amount), parses publisher /.well-known/x402 manifests, and lists recent USDC payments to an address. No private keys, verifica
Overview
What is Tensorfeed X402 Base Mcp?
A read-only MCP server for verifying x402 USDC settlements on Base mainnet. It lets any MCP-compatible agent independently audit x402 payment receipts on-chain, parse publisher .well-known/x402 manifests, and check AFTA federation status without private keys, signing, or broadcasts.
How to use Tensorfeed X402 Base Mcp?
Install globally via npm, then add the server to claude_desktop_config.json or use claude mcp add. Configure an optional private RPC URL via the TENSORFEED_RPC_URL environment variable for heavier workloads.
Key features of Tensorfeed X402 Base Mcp
- Read-only chain visibility — no private keys, no signing
- Generic Base tools: balance, usdc_balance, block_number, get_tx_receipt, call, recent_transfers
- x402-native verification: verify_x402_settlement, parse_x402_manifest, probe_x402_endpoint
- TensorFeed flavor tools: verify_afta_federation, tf_payment_lookup, x402_publisher_health, afta_federation_members
- Input validators, output sanitization, 50 KB response cap, RPC allowlist
- No telemetry, no phone-home, no analytics; MIT licensed
Use cases of Tensorfeed X402 Base Mcp
- Verify an on-chain x402 settlement given a tx hash, recipient, and expected USDC amount
- Fetch a publisher’s x402 manifest to understand which endpoints require payment and how
- Probe any HTTPS URL to check if it returns canonical x402 paid 402 response
- Audit USDC transfers to a merchant address over a recent block range
- Check AFTA federation certification for a domain with scored checklist
FAQ from Tensorfeed X402 Base Mcp
How does this differ from Coinbase Base MCP?
Coinbase Base MCP is the transact-side server for proposing swaps, transfers, and x402 payments. This server is the verify-side — it independently confirms on-chain settlement after a payment has been made. They are complementary, not competing.
Does the server require a private key or wallet?
No. The server is read-only; it cannot move funds, sign, or broadcast transactions. It only checks on-chain data.
What RPC endpoint does it use, and can I bring my own?
It defaults to the public Base RPC (https://mainnet.base.org). For heavier workloads, set TENSORFEED_RPC_URL to an Alchemy or Infura URL that matches the allowlist in src/rpc/allowlist.ts.
Does the server phone home or collect telemetry?
No telemetry, no phone-home, no analytics. The server is stateless and only reads from the configured RPC.
How do I report a security issue?
Report security issues to [email protected]. Do not file a public issue or CVE for an unfixed vulnerability.
