agent-web-reader
RemoteAbout agent-web-reader
agent-web-reader is a remote MCP server offering pay-per-call data tools for AI agents. It returns structured web, cryptocurrency and GitHub audit data, with requests paid in USDC on Base through x402.
Key features
- 01Extract readable text and metadata from URLs
- 02Fetch cryptocurrency price and trend signals
- 03Audit GitHub repository discoverability
- 04Pay per request using x402 and USDC
Use cases
- 01Retrieve page text for an agent
- 02Check a cryptocurrency symbol's market signal
- 03Review a GitHub repository's SEO and discoverability
MCP support
The remote MCP endpoint lists three tools: market_signal, web_read and repo_audit. Calls carrying x402 payment return data; unpaid calls receive a payment challenge.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://x402.charliemorrison.dev/mcpclaude mcp add --transport http dev-charliemorrison-agent-web-reader https://x402.charliemorrison.dev/mcp{"mcpServers":{"dev-charliemorrison-agent-web-reader":{"type":"http","url":"https://x402.charliemorrison.dev/mcp"}}}Open in Cursor{"servers":{"dev-charliemorrison-agent-web-reader":{"type":"http","url":"https://x402.charliemorrison.dev/mcp"}}}Open in VS Code{"mcpServers":{"dev-charliemorrison-agent-web-reader":{"type":"http","url":"https://x402.charliemorrison.dev/mcp"}}}{"mcpServers":{"dev-charliemorrison-agent-web-reader":{"serverUrl":"https://x402.charliemorrison.dev/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
3| Parameter | Type | Required | Description |
|---|---|---|---|
| ids | string | Yes | Comma-separated CoinGecko ids (e.g. 'bitcoin,ethereum,solana'), max 25 |
| x402_payment | string | No | Base64 X-PAYMENT header from your x402 wallet (omit to get the payment challenge) |
Details
From the project READMEx402-agent-data
Pay-per-call data tools for AI agents, settled per call in USDC on Base via the x402 protocol. The buyer is another agent: it discovers an endpoint, auto-pays per request (HTTP 402 → payment → data), and gets structured JSON back. No API key, no signup, no account — the seller's only setup is one public wallet address.
Live at https://x402.charliemorrison.dev — also listed as a remote MCP server in the
Official MCP Registry as
dev.charliemorrison/agent-web-reader.
Tools
| Tool | Endpoint | Price | Returns |
|---|---|---|---|
market_signal | GET /signal | $0.005 | Crypto market signal (price/trend/momentum) for a symbol |
web_read | GET /extract | $0.005 | Clean, readable text + metadata extracted from any URL |
repo_audit | GET /audit?owner=&repo= | $0.005 | GitHub repo discoverability/SEO score (0–100) + concrete fixes |
Free, unpaid routes:
GET /— discovery doc (service + paid-endpoint metadata, x402-aware)GET /healthz— livenessGET /.well-known/mcp.json— MCP discovery manifestGET /.well-known/agent.json— A2A Agent CardPOST /mcp— remote MCP server (Streamable HTTP). Lists the three tools; an unpaidtools/callreturns the decoded x402 payment-required challenge, and a call carrying an x402 payment returns the data.
How payment works
- Agent calls a paid route with no payment → server responds HTTP 402 with an
x402 challenge (amount, asset = USDC, network =
base,payToaddress). - Agent's x402 client signs a payment authorization and retries with the
X-PAYMENTheader. - Server verifies/settles via an x402 facilitator and returns the data.
No private key ever lives in this server's config — it only receives. Settlement is delegated to an x402 facilitator (default: a zero-fee, gas-sponsored facilitator; Coinbase CDP facilitator is supported via env and inert unless configured).
Run it
npm install
PAY_TO=0xYourReceivingAddress node server.js # listens on :4021
Environment:
PAY_TO— your receiving wallet (USDC on Base). Required for real revenue.PORT— default4021.CDP_API_KEY_ID/CDP_API_KEY_SECRET— optional; switches settlement to the Coinbase CDP facilitator. Omitted by default.
Why this shape
The buyer is a machine and distribution is a registry — there's no cold human audience to recruit, which is the wall that kills most indie API/tool launches. Seller setup is a single wallet address; every call is zero-marginal-cost public data.
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.