# A-Pay Protocol (remote · apay-network.vercel.app)

Universal HTTP 402 Micropayment Protocol & Autonomous Economic Settlement Engine for AI Agents

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `apay-network.vercel.app`: 65/100 (this document), [markdown](https://verifymcp.io/servers/neuralaisofficial-lang-apay/api-mcp.md), [page](https://verifymcp.io/servers/neuralaisofficial-lang-apay/api-mcp)
- pypi · `apay`: 63/100, [markdown](https://verifymcp.io/servers/neuralaisofficial-lang-apay/apay.md), [page](https://verifymcp.io/servers/neuralaisofficial-lang-apay/apay)

## Channel facts

- Endpoint: `https://apay-network.vercel.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.8`

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

- **Endpoint Security**: 63/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 5 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.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 347 tokens (~69/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the A-Pay Protocol MCP server?

A-Pay Protocol is a hosted endpoint at https://apay-network.vercel.app/api/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 neuralaisofficial-lang-apay 'https://apay-network.vercel.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "neuralaisofficial-lang-apay": {
      "url": "https://apay-network.vercel.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "neuralaisofficial-lang-apay": {
      "type": "http",
      "url": "https://apay-network.vercel.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.neuralaisofficial-lang-apay]
url = "https://apay-network.vercel.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "neuralaisofficial-lang-apay": {
      "type": "remote",
      "url": "https://apay-network.vercel.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add neuralaisofficial-lang-apay --url 'https://apay-network.vercel.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  neuralaisofficial-lang-apay:
    url: "https://apay-network.vercel.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "neuralaisofficial-lang-apay": {
      "Transport": "http",
      "Url": "https://apay-network.vercel.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add neuralaisofficial-lang-apay -t streamable-http -u 'https://apay-network.vercel.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "neuralaisofficial-lang-apay": {
      "type": "http",
      "url": "https://apay-network.vercel.app/api/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-29 (score 65, +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-28 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-27 (score 64)

First indexed and scored.

## MCP tools (5)

### `apay_request` (~80 tokens)

Probe and automatically pay HTTP 402 crypto micropayments on Base Layer 2 with USDC or $APAY within pre-configured budget limits.

Input parameters:

- `headers` (object): Optional additional HTTP headers
- `json_body` (object): Optional JSON request body
- `method` (string)
- `url` (string, required): The target endpoint URL

### `apay_get_wallet_status` (~42 tokens)

Inspect the agent's active non-custodial wallet address, network, current spending guardrails, and total spent in USDC and $APAY.

### `apay_set_budget` (~110 tokens)

Configure agent safety invariants and spending guardrails. Prevents runaway loops or overcharging.

Input parameters:

- `daily_budget_apay` (number): Maximum $APAY token rolling 24-hour spending budget
- `daily_budget_usdc` (number): Maximum USDC rolling 24-hour spending budget
- `max_per_call_apay` (number): Maximum $APAY token allowance for a single API call
- `max_per_call_usdc` (number): Maximum USDC allowance for a single API call

### `apay_inspect_endpoint` (~59 tokens)

Inspect an endpoint to check if it requires an A-Pay micropayment, inspect the exact price quote, currency, and payout receiver without spending any funds.

Input parameters:

- `url` (string, required): The URL to probe for HTTP 402 payment requirements

### `apay_get_balance` (~56 tokens)

Inspect the agent's live on-chain balances on Base Layer 2, including native ETH (for gas), USDC, and $APAY tokens.

Input parameters:

- `address` (string): Optional target EVM address to inspect balances for

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/neuralaisofficial-lang-apay/api-mcp#diagnostics

## Score history

- 2026-09-29: 65
- 2026-09-28: 64
- 2026-09-27: 64

## Common questions

### What is the A-Pay Protocol MCP server?

A-Pay Protocol is an MCP server listed in the public MCP registry as io.github.neuralaisofficial-lang/apay. Universal HTTP 402 Micropayment Protocol & Autonomous Economic Settlement Engine for AI Agents. This page covers its hosted endpoint (https://apay-network.vercel.app/api/mcp).

### Is the A-Pay Protocol MCP server safe to use?

A-Pay Protocol 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 A-Pay Protocol MCP server expose?

A-Pay Protocol exposes 5 tools: apay_request, apay_get_wallet_status, apay_set_budget, apay_inspect_endpoint, apay_get_balance. Their descriptions and schemas cost roughly 347 tokens of context every time the server is loaded.

### Does the A-Pay Protocol MCP server require authentication?

No. We connected to A-Pay Protocol without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the A-Pay Protocol MCP server still maintained?

A-Pay Protocol is still listed as active in the MCP registry. We last reached this channel on 29 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://apay-network.vercel.app/api/mcp
- Changelog RSS feed: https://verifymcp.io/servers/neuralaisofficial-lang-apay/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/neuralaisofficial-lang-apay/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/neuralaisofficial-lang-apay/api-mcp