io.github.iamalanlui/apipay
REMOTE · APIFARE.COM · 2 COMPONENTS · SCANNED SEP 20
Prepaid balance for AI agents: one key, 4,900+ tools your agent can run today, caps, receipts.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 591 tokens (~73/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 69% 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 8 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
How do I install the io.github.iamalanlui/apipay MCP server?
io.github.iamalanlui/apipay is a hosted endpoint at https://apifare.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · apifare.com
claude mcp add --transport http iamalanlui-apipay 'https://apifare.com/mcp'
{
"mcpServers": {
"iamalanlui-apipay": {
"url": "https://apifare.com/mcp"
}
}
} {
"servers": {
"iamalanlui-apipay": {
"type": "http",
"url": "https://apifare.com/mcp"
}
}
} [mcp_servers.iamalanlui-apipay] url = "https://apifare.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"iamalanlui-apipay": {
"type": "remote",
"url": "https://apifare.com/mcp",
"enabled": true
}
}
} openclaw mcp add iamalanlui-apipay --url 'https://apifare.com/mcp' --transport streamable-http
mcp_servers:
iamalanlui-apipay:
url: "https://apifare.com/mcp" {
"McpServers": {
"iamalanlui-apipay": {
"Transport": "http",
"Url": "https://apifare.com/mcp"
}
}
} assistant mcp add iamalanlui-apipay -t streamable-http -u 'https://apifare.com/mcp'
{
"mcpServers": {
"iamalanlui-apipay": {
"type": "http",
"url": "https://apifare.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 0
- Tool “check_balance” rewrote its description, which is the text the model reads security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Sept 26 62
First indexed and scored.
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 20 Sept 2026 · Probed https://apifare.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=apifare.com | CN=YE1,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5dbbaff84ce6445dcb0d82bde2d72798fb5 |
| SANs: apifare.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of apifare.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| apifare.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://apifare.com/mcp | Verified | 200 | |
| http (plaintext) | http://apifare.com/mcp | HTTPS enforced | 301 | https://apifare.com/mcp |
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 ~76
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 |
| 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 ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | API slug from search_apis, e.g. "fal" |
No output schema declared.
No examples provided.
search_apis ~74
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 |
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.
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 hosted endpoint (https://apifare.com/mcp).
Is the io.github.iamalanlui/apipay MCP server safe to use?
io.github.iamalanlui/apipay scores 65 out of 100 on VerifyMCP. 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 8 tools: search_apis, call_api, get_vault_link, check_balance, topup, and 3 more. Their descriptions and schemas cost roughly 591 tokens of context every time the server is loaded.
Does the io.github.iamalanlui/apipay MCP server require authentication?
No. We connected to io.github.iamalanlui/apipay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.