MicroTap-MCP
19 pay-per-call APIs for AI agents via x402 USDC micropayments on Base — prediction markets (Polymarket, Kalshi), DeFi/crypto data, multi-chain on-chain reads across 5 EVM chains, live weather, and real-time web search. No API key or signup — from $0.001/call. npx -y microtap-mcp
README
microtap-mcp
An MCP server for MicroTap — 19 pay-per-call APIs (Polymarket & Kalshi prediction markets, DeFi/crypto data, multi-chain on-chain reads, live weather, real-time web search) paid for automatically in USDC via the x402 protocol. No signup, no API key, no dashboard — install it, fund a small local wallet, and your AI assistant can start calling paid endpoints on its own.
Quick start
Add it to your MCP client's config. On first run it auto-generates a local EVM wallet — you don't need to create one yourself.
Claude Desktop / Claude Code
{
"mcpServers": {
"microtap": {
"command": "npx",
"args": ["-y", "microtap-mcp"]
}
}
}
Cursor / Windsurf
Same config shape — add the block above under whichever mcpServers config file your client uses.
After adding it, restart your client, then look at the server's startup log (in Claude Desktop: Settings → Developer → microtap → logs) for a line like:
[microtap-mcp] wallet address: 0xabc123...
[microtap-mcp] fund this address with a small amount of USDC on Base mainnet to pay for calls
Send a few dollars of USDC on Base mainnet to that address — at $0.001–$0.05 per call, that covers hundreds of calls. Your assistant can now use any of the 19 tools below; each one pays for itself automatically.
What it does
Every tool call:
- Calls the matching route on
x402tap.com. - If the server responds
402 Payment Required(it always does, the first time), signs a USDC payment for the exact amount requested using the wallet's private key — entirely locally, nothing is sent anywhere except the signed payment itself. - Retries the request with the payment attached and returns the real response.
The private key never leaves your machine. It isn't sent to MicroTap, an LLM provider, or anywhere else — it only signs payment messages locally, the same non-custodial pattern used by other x402 MCP servers in this ecosystem (e.g. BlockRun's).
Tools
| Tool | Route | Price |
|---|---|---|
get_protected_content |
/protected |
$0.001 |
get_weather |
/api/weather |
$0.001 |
generate_text |
/api/generate |
usage-based, max $0.05 |
get_trend_insights |
/api/insights |
$0.001–$0.005 |
ping_heartbeat |
/api/ping |
$0.001 |
search_polymarket_markets |
/api/polymarket-markets |
$0.003 |
get_polymarket_market |
/api/polymarket-market |
$0.002 |
search_kalshi_markets |
/api/kalshi-markets |
$0.003 |
get_kalshi_market |
/api/kalshi-market |
$0.002 |
get_defi_protocol_tvl |
/api/defi-tvl |
$0.003 |
rank_chains_by_defi_tvl |
/api/defi-chains |
$0.002 |
get_crypto_price |
/api/crypto-price |
$0.001 |
get_crypto_market_data |
/api/crypto-market |
$0.002 |
get_crypto_trending |
/api/crypto-trending |
$0.001 |
web_search |
/api/web-search |
$0.003 |
call_multichain_rpc |
/api/rpc |
$0.003 |
get_wallet_balance |
/api/wallet-balance |
$0.002 |
get_gas_price |
/api/gas-price |
$0.001 |
resolve_ens |
/api/ens-resolve |
$0.002 |
Full parameter docs for each route: x402tap.com/openapi.json.
Configuration (all optional)
Set these as environment variables in your MCP client's server config ("env": { ... } alongside "command"/"args") if you need to override a default:
| Variable | Default | Purpose |
|---|---|---|
MICROTAP_MCP_PRIVATE_KEY |
(auto-generated) | Bring your own EVM private key instead of the auto-generated wallet |
MICROTAP_MCP_MAX_VALUE_USDC |
0.10 |
Safety ceiling — refuses to auto-pay above this per call |
MICROTAP_BASE_URL |
https://x402tap.com |
Override the API base URL (mainly for local dev/testing) |
The auto-generated wallet's key is stored at ~/.microtap-mcp/wallet.json (created with 0600 permissions — readable only by your user).
Local development
npm install
npm run build
npm start # runs the compiled server over stdio
Security notes
- The wallet key is only ever used to sign payment messages locally (EIP-712
exactscheme on Base mainnet) — it's never transmitted anywhere. MICROTAP_MCP_MAX_VALUE_USDC(default $0.10) means this server will refuse to auto-approve a payment above that amount for a single call, even if a route's advertised price is ever wrong or unexpectedly high.- All 19 tools are read-only against MicroTap's API surface — none of them can move funds, sign transactions, or write on-chain state (
/api/rpcis restricted server-side to a safelist of read-only JSON-RPC methods).
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。