# A-Pay Protocol (pypi · apay)

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

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

## Components

- remote · `apay-network.vercel.app`: 65/100, [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 (this document), [markdown](https://verifymcp.io/servers/neuralaisofficial-lang-apay/apay.md), [page](https://verifymcp.io/servers/neuralaisofficial-lang-apay/apay)

## Channel facts

- Registry: `pypi`
- Package: `apay`
- Version: `0.1.8`
- Transport: `stdio`

## Trust breakdown

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

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 0 of 33 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 366 tokens (~73/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

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

A-Pay Protocol runs locally as a PyPI package, launched with uvx apay. 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 neuralaisofficial-lang-apay -- uvx apay
```

### Cursor

```json
{
  "mcpServers": {
    "neuralaisofficial-lang-apay": {
      "command": "uvx",
      "args": [
        "apay"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "neuralaisofficial-lang-apay": {
      "command": "uvx",
      "args": [
        "apay"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add neuralaisofficial-lang-apay -- uvx apay
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "neuralaisofficial-lang-apay": {
      "type": "local",
      "command": [
        "uvx",
        "apay"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add neuralaisofficial-lang-apay --command uvx --arg apay
```

### Hermes

```yaml
mcp_servers:
  neuralaisofficial-lang-apay:
    command: "uvx"
    args: ["apay"]
```

### Netclaw

```json
{
  "McpServers": {
    "neuralaisofficial-lang-apay": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "apay"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add neuralaisofficial-lang-apay -t stdio -c uvx -a apay
```

### Other

```json
{
  "mcpServers": {
    "neuralaisofficial-lang-apay": {
      "command": "uvx",
      "args": [
        "apay"
      ]
    }
  }
}
```

## 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-28 (score 63, +15)

- [security improvement] Malware scan: unverified → pass

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

First indexed and scored.

## MCP tools (5)

### `apay_request` (~117 tokens)

Make an HTTP request (GET, POST, etc.) to any API or website. If the endpoint returns an HTTP 402 Payment Required challenge, A-Pay automatically signs the cryptographic payment authorization within your budget limits and unlocks the data in <25ms.

Input parameters:

- `headers` (object): Optional additional HTTP headers
- `json_body` (object): Optional JSON payload for POST/PUT requests
- `method` (string): HTTP request method (default: GET)
- `url` (string, required): Target endpoint URL to fetch or query

### `apay_get_wallet_status` (~40 tokens)

Inspect the agent's active non-custodial wallet address, 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` (~40 tokens)

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

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/neuralaisofficial-lang-apay/apay#diagnostics

## Score history

- 2026-09-29: 63
- 2026-09-28: 63
- 2026-09-27: 48

## 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 PyPI package (apay).

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

A-Pay Protocol scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 29 September 2026. 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 366 tokens of context every time the server is loaded.

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

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

A-Pay Protocol declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/apay/
- Socket report: https://socket.dev/pypi/package/apay
- Changelog RSS feed: https://verifymcp.io/servers/neuralaisofficial-lang-apay/apay.xml
- Changelog JSON feed: https://verifymcp.io/servers/neuralaisofficial-lang-apay/apay.json
- HTML version of this page: https://verifymcp.io/servers/neuralaisofficial-lang-apay/apay