AiFinPay
NPM · @AIFINPAY/MCP · 2 COMPONENTS
Pay for any HTTP API in stablecoins on Polygon and Solana with one MCP call.
Available components
Last scanned (2 hours ago)
Scores higher than 58% of npm servers
Category Crypto and Web3
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 high-severity CVE affects uuid 8.3.2, reached via @aifinpay/agent > @solana/web3.js > jayson > uuid. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 50 of 166 dependencies flagged as unhealthy (1 deprecated). 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 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1104 tokens (~100/item across 11 items; 10 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% of tool parameters carry a description.Partial
- Structured output schemas are declared (70% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 −5
- Stability: pass → 0.60 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 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.
- 17 Oct 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.
- 15 Oct 26 +44
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.83 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ 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 5 Nov 2026 · Analysed npm/@aifinpay/mcp@2.2.2
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 4 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-528h-pc64-c93x | CVE-2026-71429 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-hqr4-qq8f-hg3x | CVE-2026-104182 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-mjw6-4jj6-33hc | CVE-2026-104183 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L | yes |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 166 packages
| Packages resolved | 166 |
|---|---|
| Deprecated | 1 |
| Stale | 49 |
| No linked repository | 1 |
| 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_address ~53
Return the agent's currently derived on-chain addresses. This tool is read-only and never authorizes or signs a payment. Production value movement is available only through the verified SDK v2 settlement executor after trusted deployment pins are released.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| casper | string | – | Casper identity derived from the same seed. Read-only in this MCP RC; no payment signing tool is exposed. |
| evm | string | yes | EVM address used across EVM networks (Polygon, Base, Arbitrum, Optimism, BNB, Unichain, Avalanche, Robinhood, etc.) |
| note | string | – | – |
| solana | string | yes | Solana base58 address |
No examples provided.
agent_history ~141
Read an agent's payment history by EVM address, public passport identifier, or both. Defaults to the current wallet. Transactions are indexed AiFinPay Polygon settlements, not arbitrary wallet transfers. Receipts include retained prepaid batches and test payments. Never pass a seed, private key or API secret as a passport.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| limit | integer | – | – |
| network | string | – | Exact passport wallet network; indexed transactions currently support polygon only |
| offset | integer | – | – |
| passport | string | – | Public @username, AIFP-… number or aifp_agent_… identifier |
| source | string | – | – |
No output schema declared.
No examples provided.
agent_passport_resolve ~70
Resolve an AiFinPay Agent Passport by @username, permanent AIFP number, or immutable agent id. Returns verified public wallet bindings only. Resolution never authorizes a payment.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | @username, AIFP-#########, or aifp_agent_* id |
Structured output declared, but exposes no named fields.
No examples provided.
agent_quota ~113
How many prepaid requests this agent has left, per service. Lists the agent's active quota batches (merchant, resource, used, remaining, expiry). Read-only; never spends, pays, or signs anything. Ask it things like: how many calls do I have left at mrch_x?
| Name | Type | Req | Description |
|---|---|---|---|
| include_exhausted | boolean | – | Also list batches with 0 remaining (still retained, not yet expired). |
| merchant_id | string | – | Optional mrch_… filter — only batches bought from this service. |
Structured output declared, but exposes no named fields.
No examples provided.
agent_reload ~43
Reload the configured local wallet files after init or a file update, without starting a new conversation. Returns public addresses only. Shell environment changes still require reconnecting the MCP process.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
deployment_info ~115
Get AiFinPay deployment details across EVM, Solana, and Casper — addresses, stablecoins, program IDs, and settlement status. Filter by ecosystem (evm/solana/casper), environment (prod/dev), or network name.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Filter by ecosystem. Omit for all. |
| environment | string | – | Filter by environment. Omit for all. |
| network | string | – | Filter by exact network name (e.g. 'optimism', 'mainnet', 'casper-test'). |
No output schema declared.
No examples provided.
settlement_casper ~153
Build and validate a NON-SIGNING Casper settlement invoice. This tool never moves funds. Casper uses Wasm smart contracts and deploys (not EVM transactions). Use the published @aifinpay/agent v2 settlement executor to sign and submit.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | CSPR (native Casper token). |
| chain | string | yes | – |
| gross_amount | string | yes | Gross payer amount in motes (10^-8 CSPR). |
| merchant_wallet | string | yes | Merchant/provider Casper account hex (account-hash-...). |
| order_id | string | yes | – |
| route_class | string | yes | – |
| valid_until | integer | – | Optional Unix seconds, max 20 minutes ahead. |
Structured output declared, but exposes no named fields.
No examples provided.
settlement_invoice ~149
Build and validate a NON-SIGNING v1.3 settlement invoice for EVM chains. This tool never moves funds. Use the published @aifinpay/agent v2 settlement executor to verify bytecode/profile and sign it.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Native symbol, USDC, or USDT if the route advertises it. |
| chain | string | yes | – |
| gross_amount | string | yes | Gross payer amount in base units. |
| merchant_wallet | string | yes | Merchant/provider EVM wallet (0x...). |
| order_id | string | yes | – |
| route_class | string | yes | – |
| valid_until | integer | – | Optional Unix seconds, max 20 minutes ahead. |
Structured output declared, but exposes no named fields.
No examples provided.
settlement_routes ~83
Read AiFinPay's currently runtime-verified v1.3 settlement routes. AIFP-1 is merchant monetisation (99% merchant / 1% AiFinPay / 0% creator). AIFP-2/x402 is 100% provider / 0% AiFinPay / 0% creator.
| Name | Type | Req | Description |
|---|---|---|---|
| route_class | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
settlement_solana ~162
Build and validate a NON-SIGNING Solana settlement invoice. This tool never moves funds. Uses the AiFinPay Solana B2B split program (Anchor). Use the published @aifinpay/agent v2 settlement executor to sign and submit.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | SOL (native) or USDC (SPL token). |
| chain | string | yes | – |
| gross_amount | string | yes | Gross payer amount in base units (lamports for SOL, 6 decimals for USDC). |
| merchant_wallet | string | yes | Merchant/provider Solana base58 public key. |
| order_id | string | yes | – |
| route_class | string | yes | – |
| valid_until | integer | – | Optional Unix seconds, max 20 minutes ahead. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the AiFinPay MCP server?
AiFinPay runs locally as an npm package, launched with npx -y @aifinpay/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 · @aifinpay/mcp
claude mcp add daochild-aifinpay -- npx -y @aifinpay/mcp
What is the AiFinPay MCP server?
AiFinPay is an MCP server listed in the public MCP registry as io.github.daochild/aifinpay. Pay for any HTTP API in stablecoins on Polygon and Solana with one MCP call. This page covers its npm package (@aifinpay/mcp).
Is the AiFinPay MCP server safe to use?
AiFinPay scores 78 out of 100 on VerifyMCP. We recorded 4 known advisories against it as of 5 November 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 AiFinPay MCP server expose?
AiFinPay exposes 10 tools: agent_address, agent_reload, agent_quota, agent_history, agent_passport_resolve, and 5 more. Their descriptions and schemas cost roughly 1,082 tokens of context every time the server is loaded.
Is the AiFinPay MCP server still maintained?
AiFinPay is still listed as active in the MCP registry. We last reached this channel on 5 November 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 AiFinPay MCP server under?
AiFinPay declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.