io.github.iamalanlui/apipay
NPM · APIFARE-MCP · 2 COMPONENTS
Prepaid balance for AI agents: one key, 4,900+ tools your agent can run today, caps, receipts.
Available components
Last scanned (3 hours ago)
Scores higher than 43% of npm servers
Category Workflow Automation
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 43 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 862 tokens (~95/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "secret_transfer" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 19 Oct 26 0
- Stability: 0.97 → pass security
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/apifare-mcp@0.4.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
call_api ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| params | object | – | Params object per the API's manifest, e.g. {"q": "latest AI news"} |
| slug | string | yes | API slug from search_apis, e.g. "web-search" |
No output schema declared.
No examples provided.
check_balance ~33
Check the remaining apifare prepaid credit balance (1 credit = $0.01) and get the top-up link.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_vault_link ~125
Get a secure one-time link where the user can save their OWN API key for a provider (BYOK). Use when the user wants to use their existing key (e.g. their fal.ai key) with apifare, or when an API says it is not configured. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | API slug from search_apis, e.g. "fal" |
No output schema declared.
No examples provided.
proxy_call ~218
Call a provider's NATIVE API through the apifare transparent proxy — write the request exactly as the provider's own docs say; apifare injects the auth, meters the prepaid balance, and returns the provider's response verbatim (including native error codes). Providers: dataforseo, open-meteo, apify (no key from the user), and brave/scrapingbee/openweather/fal (uses the user's vaulted key). Example: provider "dataforseo", method "POST", path "v3/serp/google/organic/live/advanced", body per DataForSEO docs.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | JSON body per the provider's docs |
| method | string | – | HTTP method (default GET) |
| path | string | yes | Provider-native path, no leading slash, e.g. "v3/serp/google/organic/live/advanced" |
| provider | string | yes | Proxy provider name, e.g. "dataforseo" |
| query | object | – | Query params per the provider's docs |
No output schema declared.
No examples provided.
search_apis ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What kind of API you need, in plain words, e.g. "search the web" |
No output schema declared.
No examples provided.
secret_generate ~45
Generate a random secret and place it directly at a vendor resource SERVER-SIDE — the value never enters this conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | integer | – | – |
| to | object | yes | – |
No output schema declared.
No examples provided.
secret_transfer ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | object | yes | – |
| to | object | yes | – |
No output schema declared.
No examples provided.
topup ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | integer | – | Optional whole-dollar amount; defaults to the mandate's refill amount and is clamped to it |
No output schema declared.
No examples provided.
vendor_call ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | JSON body for write methods |
| method | string | – | HTTP method (default GET) |
| path | string | yes | The vendor's own API path, e.g. "v9/projects" |
| vendor | string | yes | Vendor name, e.g. "vercel" |
No output schema declared.
No examples provided.
How do I install the io.github.iamalanlui/apipay MCP server?
io.github.iamalanlui/apipay runs locally as an npm package, launched with npx -y apifare-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · apifare-mcp
claude mcp add iamalanlui-apipay -- npx -y apifare-mcp
What is the io.github.iamalanlui/apipay MCP server?
io.github.iamalanlui/apipay is an MCP server listed in the public MCP registry as io.github.iamalanlui/apipay. Prepaid balance for AI agents: one key, 4,900+ tools your agent can run today, caps, receipts. This page covers its npm package (apifare-mcp).
Is the io.github.iamalanlui/apipay MCP server safe to use?
io.github.iamalanlui/apipay scores 72 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.iamalanlui/apipay MCP server expose?
io.github.iamalanlui/apipay exposes 9 tools: search_apis, call_api, get_vault_link, proxy_call, check_balance, and 4 more. Their descriptions and schemas cost roughly 862 tokens of context every time the server is loaded.
Is the io.github.iamalanlui/apipay MCP server still maintained?
io.github.iamalanlui/apipay is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.iamalanlui/apipay MCP server under?
io.github.iamalanlui/apipay declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.