A-Pay Protocol
PYPI · APAY · 2 COMPONENTS · SCANNED SEP 29
Universal HTTP 402 Micropayment Protocol & Autonomous Economic Settlement Engine for AI Agents
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 33 dependencies flagged as unhealthy. View diagnostics → Pass
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 1 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 366 tokens (~73/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
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.
pypi · apay
claude mcp add neuralaisofficial-lang-apay -- uvx apay
{
"mcpServers": {
"neuralaisofficial-lang-apay": {
"command": "uvx",
"args": [
"apay"
]
}
}
} {
"servers": {
"neuralaisofficial-lang-apay": {
"command": "uvx",
"args": [
"apay"
]
}
}
} codex mcp add neuralaisofficial-lang-apay -- uvx apay
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"neuralaisofficial-lang-apay": {
"type": "local",
"command": [
"uvx",
"apay"
],
"enabled": true
}
}
} openclaw mcp add neuralaisofficial-lang-apay --command uvx --arg apay
mcp_servers:
neuralaisofficial-lang-apay:
command: "uvx"
args: ["apay"] {
"McpServers": {
"neuralaisofficial-lang-apay": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"apay"
]
}
}
} assistant mcp add neuralaisofficial-lang-apay -t stdio -c uvx -a apay
{
"mcpServers": {
"neuralaisofficial-lang-apay": {
"command": "uvx",
"args": [
"apay"
]
}
}
} 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.
- 28 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Sept 26 48
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 29 Sept 2026 · Analysed pypi/apay@0.1.8
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 33 packages
| Packages resolved | 33 |
|---|---|
| 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 →
apay_get_balance ~40
Inspect the agent's live on-chain balances on Base Layer 2, including native ETH (for gas), USDC, and $APAY tokens.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
apay_get_wallet_status ~40
Inspect the agent's active non-custodial wallet address, current spending guardrails, and total spent in USDC and $APAY.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
apay_inspect_endpoint ~59
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to probe for HTTP 402 payment requirements |
No output schema declared.
No examples provided.
apay_request ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Target endpoint URL to fetch or query |
No output schema declared.
No examples provided.
apay_set_budget ~110
Configure agent safety invariants and spending guardrails. Prevents runaway loops or overcharging.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
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.