Agent402 MCP Server

Agent402.Tools: 500+ tools, metered models and finished reports for AI agents

The paid door for AI agents: 500+ tools, metered models and finished reports, paid per call in USDC over x402 and MPP, or by card. Open source, self-hostable, MCP-native.

Operated by Havok Holdings LLC · Live · Why pay here · Receipts · Status · Security · Company

Try it in 30 seconds: claude mcp add agent402 -- npx -y agent402-mcp, or paste https://agent402.tools/mcp into any MCP client. The free tier needs no wallet. Verified setup blocks for Cursor, VS Code, Windsurf, Cline, Roo Code, Codex CLI, Gemini CLI, Continue, ElizaOS and AgentCore: agent402.tools/guides/agent-hosts (shortlinks agent402.sh/<host>, e.g. agent402.sh/cursor).

Who pays: agents pay per call (from $0.001; models metered under a quoted ceiling and settled at actual usage); people buy finished reports ($2 to $5) and monitors ($5 a month) by card; sites charge crawlers with the tollbooth.

Listed on Smithery

What Agent402 is

Agentic Finance is software agents paying and getting paid on their own: discovering a service, paying per request from a wallet over open protocols (x402, MPP), receiving a verifiable receipt, and earning per request in return. Agent402 is its applied layer - explainer: agent402.tools/agentic-finance · glossary.

What makes it different: Agent402 is open-source and self-hostable - and a single integration gives a buyer three free primitives over the whole x402 ecosystem:

• Find - /api/find?q={task} resolves a task description to the best-matching tools (route, price, schema, ready example).
• Route - POST /api/route is the neutral Smart Order Router: rank tools across every x402 seller crawled (auto-discovered from the Coinbase CDP Bazaar), health-aware, with include=external to exclude us.
• Leaderboard - GET /api/leaderboard is the public on-chain ranking of every x402 seller by Base USDC settled volume - calls served, totalUsd, unique buyers per seller. Pipeline: Bazaar → eth_getLogs → per-call ceiling → aggregate by payTo. Hourly snapshot.

Plus the catalog - 500+ strong: search/answer as the MCP front door, then 500+ tools and curated skill packs (multi-tool workflows callable as MCP prompts) - all runnable yourself, plus agent402-tollbooth - an open pay-per-crawl gate for the other side of x402.

Two doors, two price lists. Agents pay per call in USDC (x402 / MPP) or free via proof-of-work, and a finished report costs $0.60 to $2.00 that way. People pay by card: the same reports at agent402.tools/reports (company dossier, 13F fund report, insider flow, market brief, deep research, FDA recall, domain audit) are $2 to $5, monitors that re-run on change at /monitors are $5 a month, and prepaid credits at /credits are one a402_ key that pays every tool by card (Authorization: Bearer a402_…, debited per successful call; supported by agent402-mcp via AGENT402_CREDITS_KEY and agent402-client via { creditsKey }). The card price includes payment processing: Stripe charges 2.9% + $0.30 per charge, so under about a dollar the fee costs more than the report. An agent paying per call pays the lower tool price for the same report.

Two payment wires, one URL. Every paid endpoint accepts x402 (PAYMENT-SIGNATURE, USDC on 12 chains) and MPP (Machine Payments Protocol, the IETF-track Payment HTTP auth scheme co-authored by Tempo and Stripe): the same 402 carries both, an mppx client pays out of the box, and MPP settles on Base and Celo (USDC), natively on Tempo (USDC.e or PathUSD via Tempo's relay), or by card over MPP (Stripe stripe/charge, offered on routes priced $0.50 and up when the operator configures it). The MPP marketplace lists every MPP seller we can verify live. Details: What is MPP · live MPP settlements.

Framework adapters (drop-in tools for the major agent stacks - auto-payment underneath):

500+ strong - live web search and cited answers as the MCP front door, then ready-to-use web tools and multi-tool skill packs for your AI agent, from one server. Every one tested, priced, and settled on-chain; every one earns its place. Browser rendering, web search, PDFs, images, OCR, live financial/crypto/macro data, SEC EDGAR, deterministic stats, forecasting, and options/bond pricing (Black-Scholes, YTM), compression, and 200+ pure-CPU utilities. Run it yourself for free in 30 seconds (MCP or plain HTTP, no API keys, no signup - the free tier and x402/MPP payments never need a key; only the optional prepaid card credits use one bearer key), connect it to Claude/ChatGPT/any MCP client, and add your own tools in a few lines. Every utility tool is deterministic - no LLM in the serving path - and re-tested against its own example before every release. The model-backed surfaces are explicit and priced as such: the /v1 gateway (metered under a quoted ceiling, or flat tiers) and the finished report products (/v1/research, /v1/dossier, ... below).

Optionally, the same server can charge per call over the x402 protocol (USDC on Base, Solana, Polygon, Arbitrum, Monad, Celo, Avalanche, Sei, Optimism, Stellar & Algorand, plus USDG on Robinhood Chain - 12 chains) - so the instance you self-host for free can also be a hosted, monetized one. That part is opt-in; by default everything runs free.

🟢 Hosted demo: agent402.tools · 📖 Wiki · 📦 npm · 🔌 MCP Registry · 🧩 Smithery

Run it yourself in 30 seconds

Pick whichever fits. They are all free and need no wallet:

1. Zero install - add the hosted connector to Claude (claude.ai → Settings → Connectors → Add custom connector):

https://agent402.tools/mcp

2. One command - run the MCP server locally (the pure-CPU tools work with no key; it pays the tiny proof-of-work for you):

npx -y agent402-mcp
# in Claude Code:  claude mcp add agent402 -- npx -y agent402-mcp

3. Clone and host the whole thing (all 500+ tools as an HTTP API + MCP, free mode, no payments):

git clone https://github.com/MikeyPetrillo/Agent402 && cd Agent402
npm install
FREE_MODE=true npm start          # → http://localhost:3000  (HTTP API + /mcp)

# try a tool over HTTP - no auth in free mode
curl -s -X POST localhost:3000/api/hash -H 'content-type: application/json' \
  -d '{"text":"hello world","algo":"sha256"}'

4. One-click deploy to Railway (full self-hosted instance - adds optional Postgres + Redis plugins for analytics + response caching):

Boots straight from the repo's railway.toml + Dockerfile. Optional plugins are auto-detected via env: add Redis → REDIS_URL enables the upstream response cache (X-Cache: hit|miss), add Postgres → DATABASE_URL enables the public /api/analytics dashboard and the tollbooth waitlist. No env vars required to boot in free mode.

What's in the catalog (500+ tools)

Every tool earns its place: deterministic, tested against its own example on every CI run, priced to market, settled on-chain. CI holds a 400-entry catalog floor and verifies the “500+” claim against the running catalog (scripts/sync-count.js --check). The catalog grows only when a tool is worth calling.

Full schemas live in /openapi.json; a machine-readable catalog is at /api/pricing and /llms.txt. Don't know which tool you need? /api/find?q=<task> resolves a task description to the right tool - route, price, schema, and a ready example - so an agent skips the token-heavy "search around to find a tool" step.

LLM gateway (/v1) - chat, embeddings, rerank, images, speech & finished reports, pay per call

Point any OpenAI SDK at base_url = https://agent402.tools/v1 and pay per call in USDC over x402 or MPP - no API key, no signup, no account (or pay by card with a prepaid credits key, see For humans):

Streaming (stream: true), full tools/function-calling passthrough, an opt-in prompt cache on the chat tiers (cache: true → byte-identical repeats free for 10 minutes), upstream failover chains that end in a canary-proven model, and a free GET /v1/models listing every model with its tier and caps. A real-money canary buys from every one of these surfaces daily - streaming, routing disclosure, and both cache behaviors included.

Finished report products live on the same /v1 prefix: one paid call returns a complete, cited report (JSON, with a sources appendix) rather than a raw model turn. Every report is grounded in primary data the server fetches itself (EDGAR filings, openFDA, DNS/TLS probes, on-chain reads, a live web search) before synthesis; ipo-report is fully deterministic (no model at all):

Reports are wallet-only (x402 / MPP / prepaid credits, never proof-of-work) and take a few minutes to generate. The same reports are sold to people by card at agent402.tools/reports for $1, or $2 for the three biggest. The card price includes payment processing; an agent paying per call over x402 or MPP pays the lower tool price for the same report.

Two companion tools close the loop: POST /api/route/execute ($0.01, with execute-plus $0.05 and execute-max $0.55 tiers for pricier tools) resolves a task description to the best tool and runs it in one paid call, including, with include:"external", tools sold by other x402 sellers (it routes only to sellers with proven on-chain settled volume, pays them on your behalf on the chain you paid on - Base or Algorand - and relays the result; see the Smart Order Router guide), and POST /api/my-usage ($0.005) returns the paying wallet's own purchase history - no wallet parameter; the x402 payment is the identity, so nobody can read another wallet's profile.

For humans: reports, monitors and prepaid credits

The same catalog has a card-paying front door (Stripe Checkout; the operator enables it with STRIPE_SECRET_KEY, otherwise these pages simply do not mount):

The credits key is understood by the SDKs: agent402-mcp reads AGENT402_CREDITS_KEY and agent402-client takes { creditsKey }, so a wallet-less agent can still call every wallet-only tool by card.

Skill packs - 70+ multi-tool workflows

For jobs that span several tools - "audit a domain", "diagnose deliverability", "work up a time-series", "peel an opaque blob" - Agent402 ships curated skill packs: ordered, typed sequences of tool calls with a Claude-ready prompt template. Callable as MCP prompts (prompts/list → prompts/get { name, arguments }) or plain HTTP at GET /api/skill-packs/{slug}/prompt (every slug is listed in the free JSON index at /api/skill-packs.json). A task-shaped query to catalog.search (the hosted connector's search tool; the older search_tools name still works as an alias) returns the matching pack alongside individual tools.

All 100+ packs at /skills · JSON index at /api/skill-packs.json · on MCP the packs appear under prompts/list so any MCP-aware client picks them up automatically.

x402 Index - Find · Route · Leaderboard

Agent402 is also the open routing + ranking layer for the whole x402 ecosystem: it crawls public x402 sellers (the local catalog + an auto-discovered set from the Coinbase CDP Bazaar, refreshed hourly) and exposes them through three free surfaces - same logic as /api/find: discovery primitives shouldn't cost money.

# "I need an OCR tool - find me the cheapest healthy one anywhere on x402"
curl -X POST https://agent402.tools/api/route \
  -H 'content-type: application/json' \
  -d '{"query":"ocr image to text","top":5}'

# "Who are the most-used x402 sellers right now? (on-chain proof, not self-reports)"
curl 'https://agent402.tools/api/leaderboard?top=25&include=external'

Health-aware: sellers whose last few crawls errored are excluded from the router (a buyer routed to a dead seller wastes money). Healthier sellers also break ties at equal match score and price, so flaky-but-cheap sellers lose to reliable ones. Brand-new sellers (no history yet) get the benefit of the doubt.

Operators get 3-rail attribution on the dashboard (/api/stats, /__operator, token-gated - it answers 404 without the operator token): USDC vs. proof-of-work vs. heartbeat-probe traffic are counted separately - and the heartbeat rail is gated on a POW_SECRET-signed token (not a spoofable User-Agent), so the operator view reflects real external demand.

For API sellers: /sell is the front door - list an existing x402-speaking API on the index for free with POST /api/index/register (health-routed, 0% take, self-serve, no signup), or install agent402-tollbooth to put a pay-per-crawl gate in front of a site that isn't x402-native yet.

From code, the agent402-client npm package wraps all of this - find() a tool, then call() it, paying automatically (a built-in proof-of-work for free tools, your x402 wallet for paid ones), with caching and idempotent retries:

npm install agent402-client

import { Agent402 } from "agent402-client";
const a = new Agent402();                       // free tier (proof-of-work)
const out = await a.call("hash", { text: "hello world", algo: "sha256" });

// no wallet? pay wallet-only tools by card with a prepaid credits key from /credits
const b = new Agent402({ creditsKey: "a402_..." });

Plug into your agent framework (zero-dep adapters)

If you're already on one of the stacks below - OpenAI, Anthropic, the Vercel AI SDK, LangChain (JS or Python), LlamaIndex, Strands, Google ADK, or the OpenAI Agents SDK - skip the wiring: there's a drop-in package that turns the Agent402 catalog into native tool objects for your framework, with payment handled underneath (proof-of-work for free tools, x402+USDC when you pass an @x402/fetch):

// e.g. OpenAI - every adapter has the same surface.
import OpenAI from "openai";
import { agent402Tools } from "agent402-openai-tools";

const openai = new OpenAI();
const { tools, execute } = await agent402Tools({ slugs: ["extract", "hash", "render"] });
const res = await openai.chat.completions.create({ model: "gpt-4o-mini", tools, messages: [...] });
// when the model returns a tool call: await execute(call.function.name, JSON.parse(call.function.arguments));

Already a Claude/MCP user? agent402-mcp is still the better path - paste https://agent402.tools/mcp into your client. The adapters are for direct API integrations where MCP isn't available. Sources: adapters/.

OpenClaw agents: drop in skills/openclaw/agent402/SKILL.md - teaches an OpenClaw agent to find, pay (x402 USDC on Base, eleven other chains accepted, or free proof-of-work), and call any of the 500+ tools and packs.

Add your own tool (~15 lines)

A tool is just an object in a kit array. Drop this into any file in src/tools/ (e.g. append to AGENT_TOOLS in src/tools/agent-kit.js) and it's live - routed, schema-published, MCP-exposed, and covered by the "every tool answers its own example" CI check:

{
  route: "POST /api/reverse",
  name: "Reverse text",
  slug: "reverse",
  category: "text",
  price: "$0.001",                       // free via proof-of-work for pure-CPU tools
  description: "Reverse a string. Example: {\"text\":\"abc\"} → {\"reversed\":\"cba\"}",
  discovery: {
    inputSchema: { properties: { text: { type: "string" } }, required: ["text"] },
    example: { text: "abc" },            // CI calls this and checks it works
  },
  handler: (input) => {
    if (typeof input.text !== "string") { const e = new Error('"text" required'); e.statusCode = 400; throw e; }
    return { reversed: [...input.text].reverse().join("") };
  },
}

That's the whole contract: handler(input) returns a JSON-serializable object (or throws an Error with .statusCode for a 4xx). Pure-CPU tools are automatically free-via-proof-of-work; tools that hit the network or disk stay wallet-only. See CONTRIBUTING.md for the full walkthrough.

Optional: charge per call with x402

The same server can require payment per call - useful if you host a public instance. Payments are the default posture: a bare npm start fails closed, exiting unless WALLET_ADDRESS is set - running without payments is the explicit opt-in (FREE_MODE=true npm start). To charge, set WALLET_ADDRESS

• CDP facilitator keys (free at portal.cdp.coinbase.com) and agents pay in USDC on Base (or Solana, Polygon, Arbitrum, Monad, Celo, Avalanche, Sei, Optimism, Stellar, Algorand - or USDG on Robinhood Chain via PAYMENT_NETWORKS=…,robinhood + ROBINHOOD_FACILITATOR_URL) via standard x402 clients:

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client();
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);
const res = await payFetch("https://agent402.tools/api/extract", {
  method: "POST", headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ url: "https://example.com/article" }),
});

MPP dual-stack. The paywall also speaks MPP (Machine Payments Protocol - the IETF-track Payment HTTP auth scheme from tempoxyz/mpp): the same 402 carries a WWW-Authenticate: Payment challenge, Authorization: Payment credentials settle, and settled responses return a Payment-Receipt. MPP has two methods here: evm settles identically to x402 (EIP-3009 USDC, same facilitator, same price); tempo settles natively via Tempo's own relay (TIP-1034/TIP-20, no x402 facilitator involved) - a genuinely separate settlement path, set TEMPO_API_KEY to enable it. An mppx client works out of the box for either method; set MPP_SECRET_KEY to enable the shim on your own instance. Same URL either way - the buyer's client picks the dialect.

Agents without a wallet still use every pure-CPU tool by solving a single-use sha256 proof-of-work (sub-second; the MCP servers do it automatically). Details: wiki: Paying with x402 · Paying with MPP · Paying with Compute.

Why pay here - seven things that are different

Every claim links to the surface that proves it (the one-page version: agent402.tools/why).

Documentation truncated — see the full README on GitHub.