io.github.evidai/agent-payment
NPM · AGENT-PAYMENT-MCP · SCANNED SEP 20
Stripe-style USDC billing for any API. 8 free demo services no signup. Non-custodial.
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 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 108 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1823 tokens (~303/item across 6 items; 6 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 Management93
- Stability observed for 28 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
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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.evidai/agent-payment MCP server?
io.github.evidai/agent-payment runs locally as an npm package, launched with npx -y agent-payment-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 · agent-payment-mcp
claude mcp add evidai-agent-payment -- npx -y agent-payment-mcp
{
"mcpServers": {
"evidai-agent-payment": {
"command": "npx",
"args": [
"-y",
"agent-payment-mcp"
]
}
}
} {
"servers": {
"evidai-agent-payment": {
"command": "npx",
"args": [
"-y",
"agent-payment-mcp"
]
}
}
} codex mcp add evidai-agent-payment -- npx -y agent-payment-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"evidai-agent-payment": {
"type": "local",
"command": [
"npx",
"-y",
"agent-payment-mcp"
],
"enabled": true
}
}
} openclaw mcp add evidai-agent-payment --command npx --arg -y --arg agent-payment-mcp
mcp_servers:
evidai-agent-payment:
command: "npx"
args: ["-y", "agent-payment-mcp"] {
"McpServers": {
"evidai-agent-payment": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"agent-payment-mcp"
]
}
}
} assistant mcp add evidai-agent-payment -t stdio -c npx -a -y agent-payment-mcp
{
"mcpServers": {
"evidai-agent-payment": {
"command": "npx",
"args": [
"-y",
"agent-payment-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.
- 20 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.
- 18 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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 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 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.
- 10 Sept 26 −3
- Stability: pass → 0.83 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
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/agent-payment-mcp@0.9.1
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 95 packages
| Packages resolved | 95 |
|---|---|
| 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 →
call_service ~693
Invoke an upstream API service through LemonCake's pay-per-call proxy. Each successful call automatically debits USDC from your wallet via the permit you signed. LemonCake never holds your USDC — the transfer is direct wallet → provider on Base. PRECONDITIONS: • LEMON_CAKE_PERMIT env var must be set for real services. Get one in ~30 seconds at https://lemoncake.xyz/start/v2 (sign in with Google, sign 1 EIP-712 permit, copy the blob). If missing, the tool returns a structured PERMIT_MISSING error with how-to-fix steps. • DEMO MODE: any serviceId starting with `demo_` works WITHOUT a permit and hits real free upstreams (Wikipedia / httpbin / Open-Meteo / Nominatim / MyMemory / dictionaryapi / worldtimeapi / open.er-api). 8 demos cover search / echo / fx / translate / weather / geocode / time / dictionary — useful for Glama Inspector or new-user trial. They are marked with `mode: "demo"` and incur no charge. • serviceId must come from list_services. BEHAVIOR: • Returns the upstream response body verbatim (JSON or text), plus the X-Charge-Id and X-Amount-Usdc headers reported by the proxy. • HTTP 402 Payment Required is returned as a normal result (NOT thrown) so the agent can autonomously stop spending when the daily $25 permit cap is exhausted. • Pass the same idempotencyKey to retry safely without double-charging. • This tool spends real money and contacts an external service — it is non-idempotent by default and has external side effects. x402-COMPATIBLE INTERFACE: • Successful calls include an `x402Receipt` field with { scheme, chain, asset, amount, recipient, paymentIntentId, settledAt }. Same shape as on-chain x402 receipts so the agent's payment-handling logic is portable. • If upstream returns an x402 challenge (WWW-Authenticate: x402, X-402-* headers, or body.x402), it's parsed into `x402Challenge` for the agent to reason about. • If upstream returns 202 + Retry-After + X-Payment-Status: p…
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | JSON request body (only used for POST/PUT/PATCH). |
| idempotencyKey | string | – | Optional idempotency key (UUID recommended). Identical keys within the proxy's retention window return the cached result without re-charging. |
| method | string | – | HTTP method to use against the service. Defaults to GET. |
| path | string | – | Sub-path on the service (e.g. "/search", "/v1/completions"). Defaults to "/". |
| serviceId | string | yes | ID of the service to call (obtain from list_services). |
No output schema declared.
No examples provided.
check_balance ~137
Check the current on-chain USDC balance of the wallet that owns the configured permit. PRECONDITIONS: • DEMO MODE (no LEMON_CAKE_PERMIT): returns a canned $1.00 demo balance so trial users see something useful before signing. • LIVE: queries Base USDC.balanceOf(owner) directly + reports remaining daily permit cap. LemonCake's backend doesn't store the balance — it's read from the chain. Use BEFORE call_service to confirm sufficient funds and remaining daily cap. Returns: { balanceUsdc, dailyCap, remainingToday, ownerAddress, [mode], [note] }
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_tax ~235
Run a Japanese tax compliance check on a single transaction. No authentication required. Performs three checks in one call: 1. Validates the qualified-invoice registration number (T-number) against the NTA registry. 2. Determines whether source-withholding (源泉徴収) applies based on the service description. 3. If withholding applies, computes the withholding amount and net payable. Intended for Japanese corporations that pay AI / API services and need to file withholding correctly under the qualified-invoice (インボイス制度) regime. Returns: { invoice: { valid, name, ... }, withholding: { required, rate, amount, net } } Errors: invalid registrationNumber returns invoice.valid = false (not an exception).
| Name | Type | Req | Description |
|---|---|---|---|
| grossAmountJpy | number | yes | Gross transaction amount in JPY, tax inclusive. |
| registrationNumber | string | yes | Qualified-invoice registration number issued by the Japanese NTA (e.g. "T1234567890123"). |
| serviceDescription | string | yes | Plain-text description of what was purchased. Used to classify whether source-withholding applies. |
No output schema declared.
No examples provided.
get_service_stats ~78
Return public usage statistics for every approved service on the marketplace. No authentication required. Use this AFTER list_services and BEFORE call_service to pick a service based on real-world traction (call counts, USDC revenue, last-used timestamp). Returns: an array of { serviceId, callCount, totalRevenueUsdc, lastCalledAt }.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_services ~272
List approved API services available on the LemonCake marketplace. No authentication required. Use this BEFORE call_service to discover serviceId values and per-call USDC pricing. When LEMON_CAKE_PERMIT is missing, 8 demo services are prepended: demo_search → Wikipedia opensearch demo_echo → httpbin.org/anything demo_fx → live FX rates (open.er-api) demo_translate → 80+ languages (MyMemory) demo_weather → current weather any lat/lon (Open-Meteo) demo_geocode → place name → lat/lon (OpenStreetMap Nominatim) demo_time → IANA timezone time + DST (worldtimeapi) demo_dictionary → English definitions / synonyms (dictionaryapi.dev) All real upstreams, no auth, free. Live users (permit set) see real marketplace entries; demo_* IDs remain callable directly. Each item: { id, name, provider, type ('API' | 'MCP'), pricePerCall, [usage], [mode] }. Errors: HTTP-level errors are returned as `Error: API <status>: <body>`.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of services to return (default 50, max 100). |
No output schema declared.
No examples provided.
setup ~195
Show the LemonCake MCP first-run setup guide. No authentication required. Call this tool FIRST to learn what is missing and how to obtain a permit. If LEMON_CAKE_PERMIT is not set, the server is in DEMO MODE: list_services returns 8 free demo services (search / echo / fx / translate / weather / geocode / time / dictionary) powered by real upstreams (Wikipedia, httpbin, Open-Meteo, Nominatim, etc.). call_service and check_balance respond with mock data so you can verify integration before signing. Returns the current credential status (permit presence), demo-mode flag, and step-by-step instructions for getting a permit at /start/v2, including a sample MCP client config snippet ready to paste. Returns: { version, apiUrl, mode, credentials, availableTools, setupSteps, permitUrl, docs } Errors: none — this tool always succeeds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.evidai/agent-payment MCP server?
io.github.evidai/agent-payment is an MCP server listed in the public MCP registry as io.github.evidai/agent-payment. Stripe-style USDC billing for any API. 8 free demo services no signup. Non-custodial. This page covers its npm package (agent-payment-mcp).
Is the io.github.evidai/agent-payment MCP server safe to use?
io.github.evidai/agent-payment scores 84 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 io.github.evidai/agent-payment MCP server expose?
io.github.evidai/agent-payment exposes 6 tools: setup, list_services, call_service, check_balance, check_tax, get_service_stats. Their descriptions and schemas cost roughly 1,610 tokens of context every time the server is loaded.
Is the io.github.evidai/agent-payment MCP server still maintained?
io.github.evidai/agent-payment 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.
What licence is the io.github.evidai/agent-payment MCP server under?
io.github.evidai/agent-payment declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.