three.ws Agent Payments
NPM · @THREE-WS/AGENTCORE-PAYMENTS-MCP · SCANNED SEP 20
Governed x402 payment sessions: pay any endpoint with budget, allowlist & per-tx caps, no key.
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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 909 tokens (~181/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 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 three.ws Agent Payments MCP server?
three.ws Agent Payments runs locally as an npm package, launched with npx -y @three-ws/agentcore-payments-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 · @three-ws/agentcore-payments-mcp
claude mcp add nirholas-agentcore-payments-mcp -- npx -y @three-ws/agentcore-payments-mcp
{
"mcpServers": {
"nirholas-agentcore-payments-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/agentcore-payments-mcp"
]
}
}
} {
"servers": {
"nirholas-agentcore-payments-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/agentcore-payments-mcp"
]
}
}
} codex mcp add nirholas-agentcore-payments-mcp -- npx -y @three-ws/agentcore-payments-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nirholas-agentcore-payments-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@three-ws/agentcore-payments-mcp"
],
"enabled": true
}
}
} openclaw mcp add nirholas-agentcore-payments-mcp --command npx --arg -y --arg @three-ws/agentcore-payments-mcp
mcp_servers:
nirholas-agentcore-payments-mcp:
command: "npx"
args: ["-y", "@three-ws/agentcore-payments-mcp"] {
"McpServers": {
"nirholas-agentcore-payments-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@three-ws/agentcore-payments-mcp"
]
}
}
} assistant mcp add nirholas-agentcore-payments-mcp -t stdio -c npx -a -y @three-ws/agentcore-payments-mcp
{
"mcpServers": {
"nirholas-agentcore-payments-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/agentcore-payments-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.
- 19 Sept 26 −3
- Stability: pass → 0.77 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 0
- Stability: pass → 0.97 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/@three-ws/agentcore-payments-mcp@0.1.4
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 |
|---|---|
| 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 →
cancel_payment_session Cancel a payment session and refund unused budget ~73
Cancel an active payment session. The un-spent portion of the budget is immediately refunded to your credit balance. Already-completed payments are not reversed. Idempotent — safe to call on an already-cancelled session. Requires THREE_WS_SESSION.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | UUID of the session to cancel. |
No output schema declared.
No examples provided.
check_payment_session Check a payment session's budget and status ~105
Inspect a payment session: budget, amount spent, remaining budget, status (active/exhausted/expired/cancelled), expiry time, allowlist, and per-tx ceiling. Optionally include recent payment executions. Requires THREE_WS_SESSION (only the session owner can read it).
| Name | Type | Req | Description |
|---|---|---|---|
| include_executions | boolean | – | If true, include the 10 most recent payment executions for this session. |
| session_id | string | yes | UUID of the payment session to inspect. |
No output schema declared.
No examples provided.
create_payment_session Create a funded agent payment session ~303
Create a platform-managed payment session that funds agent x402 payments from your credits. The agent never needs a private key — it uses the returned session token to call pay_with_session. Governance enforces your budget_usd ceiling, optional per-payment cap (max_per_tx_usd), URL allowlist, and time expiry. Un-spent budget is automatically refunded on cancel or expiry. Returns: session object + token (shown once — store securely). Requires THREE_WS_SESSION.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Optional: restrict this session token to a specific agent identity UUID. |
| allowed_hosts | array | – | If set, only allow payments to endpoints at these hosts (e.g. ["api.weather.com"]). Empty = any host. |
| budget_usd | number | yes | Total budget in USD to allocate to this session (drawn from your credits). Min $0.001, max $1000. |
| expiry_seconds | integer | – | Session lifetime in seconds. After expiry, payments are rejected. Default: 3600 (1 hour). |
| label | string | – | Human-readable label for this session (e.g. "Research run #4"). |
| max_per_tx_usd | number | – | Optional per-payment ceiling in USD. Payments exceeding this are rejected before any money moves. |
| metadata | object | – | Optional arbitrary metadata to attach to this session for bookkeeping. |
| network | string | – | Settlement network for x402 payments. Solana USDC only. |
No output schema declared.
No examples provided.
list_payment_sessions List payment sessions and spending stats ~88
List your payment sessions with aggregate spending stats. Filter by status. Stats include: total budget allocated, total spent, active/exhausted/expired counts, settled payment count, and unique endpoints paid. Requires THREE_WS_SESSION.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of sessions to return (max 100). |
| status | string | – | Filter by session status. Omit to return all sessions. |
No output schema declared.
No examples provided.
pay_with_session Pay an x402 endpoint via a payment session ~190
Execute an x402 micropayment against a paid API or MCP endpoint using a Payment Session token. The platform signs the Solana USDC transfer — no private key needed by the agent. Governance enforces budget limits, URL allowlists, and per-tx ceilings before any money moves. Endpoints that respond without a 402 are called for free. Returns the endpoint's response + payment receipt. Uses PAYMENT_SESSION_TOKEN env var if token is not passed inline.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | JSON body for POST requests. |
| idempotency_key | string | – | Optional idempotency key to prevent double-billing on retries. |
| method | string | – | HTTP method. Default: GET. |
| token | string | – | Payment session token (starts with "pss_"). Falls back to PAYMENT_SESSION_TOKEN env var. |
| url | string | yes | The x402 endpoint URL to pay and call. |
No output schema declared.
No examples provided.
What is the three.ws Agent Payments MCP server?
three.ws Agent Payments is an MCP server listed in the public MCP registry as io.github.nirholas/agentcore-payments-mcp. Governed x402 payment sessions: pay any endpoint with budget, allowlist & per-tx caps, no key. This page covers its npm package (@three-ws/agentcore-payments-mcp).
Is the three.ws Agent Payments MCP server safe to use?
three.ws Agent Payments scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 three.ws Agent Payments MCP server expose?
three.ws Agent Payments exposes 5 tools: create_payment_session, pay_with_session, check_payment_session, list_payment_sessions, cancel_payment_session. Their descriptions and schemas cost roughly 759 tokens of context every time the server is loaded.
Is the three.ws Agent Payments MCP server still maintained?
three.ws Agent Payments 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.