# io.github.iamalanlui/apipay (remote · apifare.com)

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

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `apifare.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/iamalanlui-apipay/apifare.md), [page](https://verifymcp.io/servers/iamalanlui-apipay/apifare)
- npm · `apifare-mcp`: 72/100, [markdown](https://verifymcp.io/servers/iamalanlui-apipay/apifare-mcp.md), [page](https://verifymcp.io/servers/iamalanlui-apipay/apifare-mcp)

## Channel facts

- Endpoint: `https://apifare.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 591 tokens (~73/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 69% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http iamalanlui-apipay 'https://apifare.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "iamalanlui-apipay": {
      "url": "https://apifare.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "iamalanlui-apipay": {
      "type": "http",
      "url": "https://apifare.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.iamalanlui-apipay]
url = "https://apifare.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "iamalanlui-apipay": {
      "type": "remote",
      "url": "https://apifare.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add iamalanlui-apipay --url 'https://apifare.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  iamalanlui-apipay:
    url: "https://apifare.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "iamalanlui-apipay": {
      "Transport": "http",
      "Url": "https://apifare.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add iamalanlui-apipay -t streamable-http -u 'https://apifare.com/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 65, +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.

### 2026-09-17 (score 64, +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.

### 2026-09-16 (score 63, 0)

- [security] Tool “check_balance” rewrote its description, which is the text the model reads

### 2026-09-15 (score 63, +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.

### 2026-09-14 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-13 (score 62)

First indexed and scored.

## MCP tools (8)

### `search_apis` (~74 tokens)

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.

Input parameters:

- `query` (string, required): What kind of API you need, in plain words

### `call_api` (~76 tokens)

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.

Input parameters:

- `params` (object): Params object per the API's manifest
- `slug` (string, required): API slug from search_apis, e.g. "web-search"

### `get_vault_link` (~91 tokens)

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.

Input parameters:

- `provider` (string, required): API slug from search_apis, e.g. "fal"

### `check_balance` (~33 tokens)

Check the remaining apifare prepaid credit balance (1 credit = $0.01) and get the top-up link.

### `topup` (~82 tokens)

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.

Input parameters:

- `amount_usd` (integer): Optional whole-dollar amount; defaults to the mandate's refill amount and is clamped to it

### `vendor_call` (~129 tokens)

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.

Input parameters:

- `body` (object): JSON body for write methods
- `method` (string): HTTP method (default GET)
- `path` (string, required): The vendor's own API path, e.g. "v9/projects"
- `vendor` (string, required): Vendor name, e.g. "vercel"

### `secret_transfer` (~61 tokens)

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.

Input parameters:

- `from` (object, required)
- `to` (object, required)

### `secret_generate` (~45 tokens)

Generate a random secret and place it directly at a vendor resource SERVER-SIDE — the value never enters this conversation.

Input parameters:

- `bytes` (integer)
- `to` (object, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/iamalanlui-apipay/apifare#diagnostics

## Score history

- 2026-09-20: 65
- 2026-09-19: 65
- 2026-09-18: 64
- 2026-09-17: 64
- 2026-09-16: 63
- 2026-09-15: 63
- 2026-09-14: 62
- 2026-09-13: 62

## Common questions

### 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.

## Links

- Remote endpoint: https://apifare.com/mcp
- Repository: https://github.com/iamalanlui/apifare-mcp
- Changelog RSS feed: https://verifymcp.io/servers/iamalanlui-apipay/apifare.xml
- Changelog JSON feed: https://verifymcp.io/servers/iamalanlui-apipay/apifare.json
- HTML version of this page: https://verifymcp.io/servers/iamalanlui-apipay/apifare