mcpbeat Sign in

Apipay MCP Server

by iamalanlui Your server? Claim it
answering

Apipay is answering right now. Last checked 7 min ago. 220 installs a week from npm. It exposes 8 tools. Last commit 13 Sep 2026.

Prepaid balance for AI agents: one key, 4,900+ tools your agent can run today, caps, receipts.

Installs per day peak 12 · avg 0
a month agotoday
Uptime history 7 days of history
7 days agonow
100.0%
Uptime 24h
184 of 184 checks
8
Tools
read from the server
178 ms
Response time
average over 24h
220
Installs / week
npm and PyPI

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 September 2026. No other catalogue keeps this.

15 Sep a tool description was rewritten check_balance

What the code does

We have not read this server's code yet, 4 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Package points at a different repository iamalanlui/apifare-mcp
пакет apifare-mcp ссылается на iamalanlui/apipay

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add apipay --transport http https://apipay.fly.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "apipay": {
      "url": "https://apipay.fly.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.apipay]
url = "https://apipay.fly.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "apipay": {
      "url": "https://apipay.fly.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "apipay": {
      "url": "https://apipay.fly.dev/mcp"
    }
  }
}

This one needs environment variables set before it will start: APIPAY_TOKEN (Bearer token from POST https://apifare.com/v1/signup (shown once)). The author declared them in the registry entry; get the values from the project itself.

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

secret
secret_generate
Generate a random secret and place it directly at a vendor resource SERVER-SIDE — the value never enters this conversation.
secret_transfer
Move a secret from one vendor to another SERVER-SIDE — the value never enters this conversation. Example: fetch a Supabase service_role key and place it as a Vercel env var.
apis
search_apis
Search the apifare catalog of ready-to-call APIs (web search, scraping, weather, and more). Returns each API's slug, params, and per-call price in prepaid credits. Every miss is logged so missing APIs get added.
balance
check_balance
Check the remaining apifare prepaid credit balance (1 credit = $0.01) and get the top-up link.
call
call_api
Call an API from the apifare catalog by slug (find slugs with search_apis). The cost in prepaid credits is deducted automatically and returned with the result.
topup
topup
Top up the apifare balance from the owner's standing auto-refill mandate (if the owner enabled one). Charges within the owner's configured limits and returns the new balance. Without a mandate, returns payment instructions to relay to the user.
vault
get_vault_link
Get a secure one-time link where the user can save their OWN API key for a provider (BYOK). Never ask the user to paste an API key into the chat — always use this link instead. BYOK calls cost a flat 0.1 credits; the user's own provider account pays the provider.
vendor
vendor_call
Call a vendor MANAGEMENT API (supabase, vercel, fly, resend, github, npm, cloudflare, lemonsqueezy) with the owner's vaulted root credential injected server-side. Native request/response; destructive, billing, and member/admin routes are blocked. The root token is never visible.

Endpoints

URLTransportStateLatencyChecked
https://apipay.fly.dev/mcp streamable-http answering 172 ms 7 min ago
https://apifare.com/mcp streamable-http answering 170 ms 7 min ago

Alternatives to Apipay

same job, measured the same way
Agentcard
by agentcard

Prepaid virtual cards for AI agents: one-time cards, spend caps, human approvals.

58 tools answering
Mpp32 MCP Server
by mpp32

Payment layer for AI agents. One MCP, five protocols, thousands of paid APIs your agent can call.

94 installs/wk local only
JMT x402 Agent Tools
by jmthomasofficial

25 x402 paid API tools for AI agents on Base mainnet.

local only
Agentreader MCP
by ajanani1

11 pay-per-call web tools for AI agents, auto-paid in USDC on Base via x402. No API keys.

24 installs/wk local only
Suprsonic MCP
by o-mega-enterprise

One API key, dozens of capabilities for your AI agent. Zero provider auth.

29 installs/wk local only
X402 Endpoints
by digitalweb33333-creator

x402 paid API tools for AI agents on Base: EU/global registries, crypto, wallet & agent trust.

52 tools answering
Proof Layer
by world-999-labs

Signed, hash-chained provenance receipts for AI agent actions.

22 installs/wk local only
Agentpay
by romudille-bit

Budget-capped x402 payments for AI agents: verifiable receipts, trust routing, 17 free tools.

79 installs/wk local only

Apipay — questions

Answers built from our own checks of this server.

What can Apipay do?
It exposes 8 tools, read directly from the server on our last check. Among them: call_api, check_balance, get_vault_link, search_apis, secret_generate, secret_transfer and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Apipay working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 184 of 184 checks got a reply (100.0%), average response time 178 ms. The bar chart above shows every period we have measured.
How do I connect Apipay?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Apipay need an API key?
No. Apipay completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Apipay?
It answers our handshake in 178 ms on average, which is faster than 71% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Apipay?
The npm package apifare-mcp was installed 220 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Apipay open source?
Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.