io.github.voidly-ai/pay-mcp
NPM · @VOIDLY/PAY-MCP · SCANNED SEP 25
USDC-backed agent payments. Transfer, escrow, x402 paywall, streams, subs. 28 tools.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 96 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
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 3 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1961 tokens (~70/item across 28 items; 28 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% 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 14 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "agent_pay_self" implies "pay" 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 28 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.voidly-ai/pay-mcp server?
io.github.voidly-ai/pay-mcp runs locally as an npm package, launched with npx -y @voidly/pay-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @voidly/pay-mcp
claude mcp add voidly-ai-pay-mcp -- npx -y @voidly/pay-mcp
{
"mcpServers": {
"voidly-ai-pay-mcp": {
"command": "npx",
"args": [
"-y",
"@voidly/pay-mcp"
]
}
}
} {
"servers": {
"voidly-ai-pay-mcp": {
"command": "npx",
"args": [
"-y",
"@voidly/pay-mcp"
]
}
}
} codex mcp add voidly-ai-pay-mcp -- npx -y @voidly/pay-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"voidly-ai-pay-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@voidly/pay-mcp"
],
"enabled": true
}
}
} openclaw mcp add voidly-ai-pay-mcp --command npx --arg -y --arg @voidly/pay-mcp
mcp_servers:
voidly-ai-pay-mcp:
command: "npx"
args: ["-y", "@voidly/pay-mcp"] {
"McpServers": {
"voidly-ai-pay-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@voidly/pay-mcp"
]
}
}
} assistant mcp add voidly-ai-pay-mcp -t stdio -c npx -a -y @voidly/pay-mcp
{
"mcpServers": {
"voidly-ai-pay-mcp": {
"command": "npx",
"args": [
"-y",
"@voidly/pay-mcp"
]
}
}
} 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.
- 25 Sept 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.77 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 25 Sept 2026 · Analysed npm/@voidly/pay-mcp@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Deprecated | 1 |
| Stale | 31 |
| 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 →
agent_escrow_open ~82
Voidly Pay: Open an escrow hold. Locks `amount` credits from the caller's wallet. Auto-expires past `deadline_hours`.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| deadline_hours | number | – | default 24, max 168 (7 days) |
| memo | string | – | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
agent_escrow_refund ~54
Voidly Pay: Refund an open escrow back to the sender. Caller must be the original sender.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| escrow_id | string | yes | – |
| reason | string | – | optional ≤280 chars |
No output schema declared.
No examples provided.
agent_escrow_release ~41
Voidly Pay: Release an open escrow to its recipient. Caller must be the original sender.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| escrow_id | string | yes | – |
No output schema declared.
No examples provided.
agent_pay ~101
Voidly Pay: Sign + settle a one-shot transfer. Amount is in CREDITS (1 credit = 1,000,000 micro). Returns the transfer receipt.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | credits (e.g. 0.5) |
| expires_in_minutes | number | – | envelope expiry (default 30) |
| memo | string | – | optional, ≤280 chars |
| to | string | yes | recipient did:voidly:... |
No output schema declared.
No examples provided.
agent_pay_activity ~57
Voidly Pay: Most-recent state changes across all primitives (transfers, escrows, hires, streams, subscriptions). Public; no signing.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | 1-200, default 50 |
No output schema declared.
No examples provided.
agent_pay_batch ~53
Voidly Pay: Atomic multi-recipient transfer. items: [{to, amount, memo?}]. All-or-nothing. Returns batch summary + per-item receipts.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
agent_pay_feed ~63
Voidly Pay: Incremental, append-only feed of settled transfers. Use `since` cursor from the previous response's next_since.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | 1-200, default 50 |
| since | string | – | ISO cursor |
No output schema declared.
No examples provided.
agent_pay_get ~44
Voidly Pay: Look up a transfer by id. Returns the ledger row including signature, envelope_hash, and status.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| transfer_id | string | yes | – |
No output schema declared.
No examples provided.
agent_pay_health ~33
Voidly Pay: System-frozen flag + counts of wallets and 24h-settled transfers.. Returns JSON.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
agent_pay_health_check ~148
Voidly Pay: One-call trust report. Aggregates /v1/pay/health + /v1/pay/manifest.json + (optionally) the on-chain vault USDC balance into a structured pass/fail breakdown. Returns ok:true only if every individual check passes — system not frozen, manifest declares a Stage 2 vault, vault is on Base mainnet, source verified on Sourcify, vault holds USDC. Use this before relying on the rail for anything you care about settling.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| rpcUrl | string | – | Public Base RPC. Default: https://mainnet.base.org |
| skipChain | boolean | – | Skip the on-chain vault balance read. |
No output schema declared.
No examples provided.
agent_pay_leaderboard ~70
Voidly Pay: Top earners or spenders. metric: earned_24h | earned_total | spent_24h | spent_total | hires_24h.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | 1-200, default 25 |
| metric | string | – | – |
No output schema declared.
No examples provided.
agent_pay_manifest ~31
Voidly Pay: Discovery manifest: every endpoint, schema, defaults, and MCP tool list.. Returns JSON.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
agent_pay_self ~30
Voidly Pay: Get the SDK's own DID, public key, and current balance.. Returns JSON.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
agent_pay_stats ~33
Voidly Pay: Platform-wide aggregates — capabilities, hires, value settled, top providers, recent activity.. Returns JSON.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
agent_pay_trust ~51
Voidly Pay: Derived provider+requester stats for a DID — completion rate, rating avg, total earned. Useful before a hire decision.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| did | string | – | default self |
No output schema declared.
No examples provided.
agent_payment_history ~59
Voidly Pay: Paginated history of transfers for a DID (defaults to self).. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | ISO cursor |
| did | string | – | – |
| limit | number | – | default 20, max 200 |
No output schema declared.
No examples provided.
agent_stream_finalize ~86
Voidly Pay: Requester-side: finalize a stream. Acknowledges the metered total + last seq + last hash. Settles metered amount to provider, refunds rest to requester.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_hash | string|null | – | – |
| expected_seq | number | yes | – |
| metered_total_micro | number | yes | – |
| stream_id | string | yes | – |
No output schema declared.
No examples provided.
agent_stream_meter ~132
Voidly Pay: Provider-side: append a signed meter entry to an open stream. seq starts at 1 and increments. prev_hash is the last entry's this_hash (or null for seq=1). Returns this_hash for chaining the next.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| delta | number | yes | credits to add to the meter |
| prev_hash | string | – | previous entry's this_hash, or null for seq=1 |
| seq | number | yes | monotonically increasing, ≥1 |
| stream_id | string | yes | – |
| units | number | – | optional unit count (e.g. tokens used) |
No output schema declared.
No examples provided.
agent_stream_open ~107
Voidly Pay: Open a metered payment stream. Locks `budget` credits as a max. Provider appends signed meter entries. Use for per-token / per-second billing.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | yes | max credits |
| deadline_minutes | number | – | default 60 |
| description | string | – | – |
| provider | string | yes | provider's did:voidly:... |
| unit_label | string | – | e.g. 'tokens', 'ms', 'bytes' |
No output schema declared.
No examples provided.
agent_subscribe ~94
Voidly Pay: Create a recurring subscription. Pulls `amount_per_period` from caller's balance every `period_seconds`. Auto-pauses after 3 consecutive failures.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_per_period | number | yes | – |
| description | string | – | – |
| period_seconds | number | yes | min 60 |
| periods_total | number | – | optional cap; omit for unlimited |
| provider | string | yes | – |
No output schema declared.
No examples provided.
agent_subscription_cancel ~46
Voidly Pay: Cancel a subscription. Either party (requester or provider) may cancel.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | – |
| subscription_id | string | yes | – |
No output schema declared.
No examples provided.
agent_wallet_balance ~57
Voidly Pay: Read the wallet for a DID. Returns balance, locked, caps, frozen flag. If `did` omitted, defaults to self.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| did | string | – | did:voidly:... (optional) |
No output schema declared.
No examples provided.
agent_wallet_ensure ~45
Voidly Pay: Idempotent: create wallet for a DID if it doesn't exist. Useful before sending the first payment.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| did | string | yes | – |
No output schema declared.
No examples provided.
agent_webhook_delete ~35
Voidly Pay: Revoke a webhook subscription owned by the caller.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | string | yes | – |
No output schema declared.
No examples provided.
agent_webhook_subscribe ~106
Voidly Pay: Subscribe to pay events via HMAC-signed webhook. Returns webhook_id and a `secret` (returned ONCE) for signature verification.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| did_filter | string | – | only fire when this DID is involved |
| events | array | – | filter: ['transfer.settled', 'stream.finalized', ...]; omit for all |
| url | string | yes | https only (loopback blocked) |
No output schema declared.
No examples provided.
agent_x402_fetch ~100
Voidly Pay: Fetch a URL; if it returns HTTP 402, parse the quote, transfer, retry. Returns the FINAL response status and body. `max_amount` caps how much the agent will pay.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | optional request body |
| max_amount | number | – | max credits to pay (default 0.01) |
| method | string | – | default GET |
| url | string | yes | – |
No output schema declared.
No examples provided.
agent_x402_quote ~112
Voidly Pay: Server-side: create an x402 quote. Returns a payment_required_response that the server should serve verbatim with HTTP 402.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | credits |
| description | string | – | – |
| method | string | – | HTTP method (optional) |
| recipient | string | – | where to send the money (default: self) |
| resource | string | yes | URL path or label |
| ttl_seconds | number | – | default 600, max 3600 |
No output schema declared.
No examples provided.
agent_x402_verify ~91
Voidly Pay: Server-side: verify + consume an x402 payment. Pass the X-Payment header value the caller sent. Atomic; UNIQUE replay protection at the DB.. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_header | string | – | value of the X-Payment header |
| quote_id | string | – | redundant if payment_header carries it |
| transfer_id | string | – | redundant if payment_header carries it |
No output schema declared.
No examples provided.
What is the io.github.voidly-ai/pay-mcp server?
io.github.voidly-ai/pay-mcp is listed in the public MCP registry as io.github.voidly-ai/pay-mcp. USDC-backed agent payments. Transfer, escrow, x402 paywall, streams, subs. 28 tools. This page covers its npm package (@voidly/pay-mcp).
Is the io.github.voidly-ai/pay-mcp server safe to use?
io.github.voidly-ai/pay-mcp scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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.voidly-ai/pay-mcp server expose?
io.github.voidly-ai/pay-mcp exposes 28 tools: agent_pay_self, agent_wallet_balance, agent_wallet_ensure, agent_pay, agent_pay_batch, and 23 more. Their descriptions and schemas cost roughly 1,961 tokens of context every time the server is loaded.
Is the io.github.voidly-ai/pay-mcp server still maintained?
io.github.voidly-ai/pay-mcp is still listed as active in the MCP registry. We last reached this channel on 25 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 io.github.voidly-ai/pay-mcp server under?
io.github.voidly-ai/pay-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.