apipay — prepaid API balance for agents
https://server.smithery.ai/iamalanlui/apipay/mcpOne balance for your agent's APIs. First ask: search the web via resold DataForSEO (slug dataforseo, 0.3 credits, no user search key — live Google results). Second no-key ask: fetch a URL as clean markdown via slug scrape, 0.3 credits, powered by DataForSEO On-Page. Weather is the cheap third SKU: slug open-meteo, 0.1 credits, no user weather key (keep Open-Meteo CC BY 4.0 attribution). apipay is the account layer for AI agents: identity, money, and history in one place. Sign up once (500 free credits, 1 credit = $0.01), add the MCP server, and your agent can discover and call any API in the catalog mid-conversation. Start with a live Google search via dataforseo (0.3 credits), then fetch any URL as markdown via scrape (0.3 credits) — both without the user supplying a provider key. Weather via open-meteo (0.1 credits) is the cheap third option. Costs are metered per call from the prepaid balance; provider failures are auto-refunded. When credits run out the agent gets a structured 402 with a payment link. Bring your own keys for providers we don't resell — Brave (web-search), ScrapingBee (scrapingbee), OpenWeather (weather), and fal — at a flat 0.1 credits/call via secure one-time vault links. Install: `npx -y apipay-mcp` (npm package apipay-mcp, v0.3.3) with `APIPAY_TOKEN` from `POST https://apipay.fly.dev/v1/signup` MCP: https://apipay.fly.dev/mcp
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (4137 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 8 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 0/5 | not seen in a source for over 30 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 55% of peers
- This listing 82 · peer median 81
- Latency
- Faster than 31% of peers
- This listing 496 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Freshness + modern flags −5
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/iamalanlui/apipay/mcpcurl -X POST https://server.smithery.ai/iamalanlui/apipay/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'