io.github.Merit-Systems/agentcash
NPM · AGENTCASH · SCANNED SEP 25
Generic MCP server for calling x402-protected APIs with automatic payment handling
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 Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects mppx 0.4.12, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 46 of 238 dependencies flagged as unhealthy. 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 59 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1981 tokens (~180/item across 11 items; 11 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 Management77
- Stability observed for 23 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
- Structured output schemas are declared (18% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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.Merit-Systems/agentcash MCP server?
io.github.Merit-Systems/agentcash runs locally as an npm package, launched with npx -y agentcash. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · agentcash
claude mcp add merit-systems-agentcash -- npx -y agentcash
{
"mcpServers": {
"merit-systems-agentcash": {
"command": "npx",
"args": [
"-y",
"agentcash"
]
}
}
} {
"servers": {
"merit-systems-agentcash": {
"command": "npx",
"args": [
"-y",
"agentcash"
]
}
}
} codex mcp add merit-systems-agentcash -- npx -y agentcash
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"merit-systems-agentcash": {
"type": "local",
"command": [
"npx",
"-y",
"agentcash"
],
"enabled": true
}
}
} openclaw mcp add merit-systems-agentcash --command npx --arg -y --arg agentcash
mcp_servers:
merit-systems-agentcash:
command: "npx"
args: ["-y", "agentcash"] {
"McpServers": {
"merit-systems-agentcash": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"agentcash"
]
}
}
} assistant mcp add merit-systems-agentcash -t stdio -c npx -a -y agentcash
{
"mcpServers": {
"merit-systems-agentcash": {
"command": "npx",
"args": [
"-y",
"agentcash"
]
}
}
} 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 −3
- 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
- 23 Sept 26 −3
- CVE-2026-63627 affects this package: medium ▼ security
- CVE-2026-63628 affects this package: medium ▼ security
- Known CVEs: pass → fail ▼ 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 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.
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/agentcash@0.13.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 →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-727h-3vm5-qwq6 | CVE-2026-63627 | medium | yes | |
| GHSA-vc9j-9wph-qghj | CVE-2026-63628 | medium | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 238 packages
| Packages resolved | 238 |
|---|---|
| Stale | 46 |
| 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 →
bridge Bridge Between Networks ~92
Bridge USDC between supported networks using the current wallet. Requires a source network, destination network, and amount. Use this when funds are on one supported network and the user needs them moved to another. Bridging is subject to fees.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | The amount of USDC to bridge |
| from | string | yes | The network to bridge from |
| to | string | yes | The network to bridge to |
No output schema declared.
No examples provided.
check_endpoint_schema Check Endpoint Schema ~218
Get the input/output schema and auth mode (paid or SIWX) for a single endpoint. Call this to see exactly what fields the request body expects and what the response contains. Returns the schema from the origin's OpenAPI spec. Optionally pass sample_input_body to probe the endpoint live (without payment) for an exact price quote — do this when pricing is range-based or quote-based, or when you're unsure about the input schema. Treat auth mode as advisory: fetch handles both SIWX and paid routes.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | Optional. A sample request body to probe the endpoint live (without payment) for exact pricing. Use when pricing is range-based or quote-based, or when you need to verify the input schema. Omit to ge… |
| headers | object | – | Additional headers to include as a key-value pair |
| method | string | – | HTTP method to check. If omitted, all methods declared in the spec are returned. |
| url | string | yes | The endpoint URL |
No output schema declared.
No examples provided.
discover_api_endpoints Discover API Endpoints ~237
List available endpoints at an API origin. Returns endpoint URLs with descriptions of what each does and the auth mode for each (paid or SIWX). Works with any origin, not just the registered ones. Call this when you need to see what routes are available at an origin — whether it's one of the registered origins or any other origin you've identified as useful. Treat the auth mode as guidance for what the route may require; fetch handles both SIWX and payment. The response always indicates whether guidance is available. Guidance is documentation published by the API provider explaining how endpoints work together, edge cases, and usage tips. compact guidance is included automatically; set include_guidance=true to force-include full usage documentation when you need to compose two or more endpoints or need clarification on how the origin works.
| Name | Type | Req | Description |
|---|---|---|---|
| includeGuidance | boolean | – | Request the origin's usage guidance. true=always include, false=never include, omit=auto (included when compact). Guidance explains how to compose multiple endpoints and covers edge cases. |
| url | string | yes | The origin URL to discover endpoints on (e.g. https://stableenrich.dev) |
No output schema declared.
No examples provided.
fetch HTTP fetch with automatic authentication and payment handling. Makes the request, retries with SIGN-IN-WITH-X when the route exposes a SIWX challenge, and only pays if the route still returns 402. Re… ~275
HTTP fetch with automatic authentication and payment handling. Makes the request, retries with SIGN-IN-WITH-X when the route exposes a SIWX challenge, and only pays if the route still returns 402. Returns response data along with payment details (price, tx hash) if a payment was made. For endpoints you haven't called before in this session, you MUST call check_endpoint_schema first to confirm the request body schema. Skipping this causes 400 errors from wrong field names.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | Request body. Can be a string or an object that will be stringified. |
| headers | object | – | Additional headers to include as a key-value pair |
| maxAmount | number | – | Maximum amount (in USD) to pay per request. Aborts if the endpoint requests more. Defaults to $5. Pass a higher value for known-expensive endpoints. |
| method | string | – | HTTP method. Defaults to GET for fetch operations. |
| paymentNetwork | string | – | Chain to use for SIWX and payment when applicable. If not specified, the network will be auto-detected. |
| paymentProtocol | string | – | Payment protocol to use when payment is required. If not specified, the payment protocol will be auto-detected. |
| timeout | integer | – | Request timeout in milliseconds |
| url | string | yes | The endpoint URL |
No output schema declared.
No examples provided.
get_balance Get Balance ~48
Get your total USDC balance across all supported networks. Auto-creates the wallet on first use (~/.agentcash/wallet.json). Use this before paid API calls to confirm you have funds available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_settings Get Settings ~26
Get current user settings. Returns persisted values from ~/.agentcash/settings.json with defaults applied.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_accounts Get Accounts ~90
List wallet accounts for each supported network. Returns the network, address, balance, and deposit link for every supported network so you can see where to fund the wallet. Auto-creates the wallet on first use (~/.agentcash/wallet.json). If onboardingCta is present, show its message to the user — it means they haven't onboarded yet and need to either visit the onboard link or deposit directly.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
redeem_invite Redeem Invite ~66
Redeem an invite code for free USDC on Base. One-time use per code. Returns amount received and transaction hash. Use get_balance after to verify funds, or list_accounts if you need the per-network deposit links as well.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The invite code |
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount with unit (e.g., "5 USDC") |
| redeemed | boolean | yes | – |
| txHash | string | yes | Transaction hash on Base |
No examples provided.
report_error Report Error ~108
EMERGENCY ONLY. Report critical MCP tool bugs. Do NOT use for normal errors (balance, network, 4xx) — those are recoverable.
| Name | Type | Req | Description |
|---|---|---|---|
| errorMessage | string | yes | Error message |
| fullReport | string | – | Detailed report with context, logs, repro steps |
| resource | string | – | Resource URL |
| stack | string | – | Stack trace |
| summary | string | yes | 1-2 sentence summary |
| tool | string | yes | MCP tool name |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Confirmation message |
| reportId | string | yes | Unique report ID for tracking |
| submitted | boolean | yes | – |
No examples provided.
search Search APIs ~148
Search for relevant paid API services by describing what you need in natural language. Returns the best matching origins with endpoint details and pricing. The top result includes the full input/output schema so you can call it immediately via fetch. Only use this when you DON'T already know which registered origin to use. If the task clearly maps to a registered origin (e.g. people search → StableEnrich, image generation → StableStudio), skip search and go straight to discover_api_endpoints on that origin. Search is for discovering NEW or UNKNOWN capabilities outside the registered origins.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Natural language description of what you need (e.g. "send physical mail", "generate music", "flight prices") |
No output schema declared.
No examples provided.
update_settings Update Settings ~81
Update user settings (persisted to ~/.agentcash/settings.json). Currently supports maxAmount — the maximum USD amount allowed per fetch request. If a fetch response requests more than this, the payment is rejected. Returns the current settings after applying changes.
| Name | Type | Req | Description |
|---|---|---|---|
| maxAmount | number | – | Maximum amount (USD) to pay per fetch request. Current default: $5. |
No output schema declared.
No examples provided.
What is the io.github.Merit-Systems/agentcash MCP server?
io.github.Merit-Systems/agentcash is an MCP server listed in the public MCP registry as io.github.Merit-Systems/agentcash. Generic MCP server for calling x402-protected APIs with automatic payment handling. This page covers its npm package (agentcash).
Is the io.github.Merit-Systems/agentcash MCP server safe to use?
io.github.Merit-Systems/agentcash scores 72 out of 100 on VerifyMCP. We recorded 2 known advisories against 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.Merit-Systems/agentcash MCP server expose?
io.github.Merit-Systems/agentcash exposes 11 tools: fetch, get_balance, list_accounts, check_endpoint_schema, redeem_invite, and 6 more. Their descriptions and schemas cost roughly 1,389 tokens of context every time the server is loaded.
Is the io.github.Merit-Systems/agentcash MCP server still maintained?
io.github.Merit-Systems/agentcash 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.Merit-Systems/agentcash MCP server under?
io.github.Merit-Systems/agentcash declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.