@aifinpay/mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Contacts while installing and starting: nothing
Its tool definitions changed since version 2.16.2. If you approved the earlier ones, read them again.
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @aifinpay/mcp@2.16.3
Installing a package runs its code. Use a sandbox for anything you have not read.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
agent_address
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.
agent_claim_self magic_link_url, label
Link this agent to its owner's AiFinPay dashboard, so the owner sees the agent's balance, payments and receipts. Offer this after creating a wallet. The owner generates a one-time URL at https://dash.aifinpay.io → My Agents → Link an agent → Claim via MCP and gives it to you; pass it here. Do not open the URL in a browser tool: that links nothing. The tool signs only an AiFinPay claim challenge for this agent's own address and moves no funds.
agent_reload
Reload the configured local wallet files after init or a file update, without starting a new conversation. Returns public addresses only. With payments on (the default) it also opens the payment journal for the loaded wallet, so a server that started with an ephemeral wallet can pay right after init, without a restart. Env changes (owner overrides, AIFINPAY_PAYMENTS_ENABLED=0) take effect only after the client restarts the aifinpay MCP server; agent_reload does not read them.
payment_setup_status
Read-only checklist for paying with payable_fetch: wallet (persistent or ephemeral), whether payments are on, the ceiling and each limit with its source (built-in default or the owner's env), the wallet's native balance on the pay chain when readable, the owner's dashboard Controls in `dashboard`, and next_step — exactly one instruction for the first unmet item. First payment in five steps: (1) get the exact endpoint URL from the user (its AIFP-1 402 sets the price; never take a price from the merchant's web pages or a web search); (2) call payment_setup_status; (3) no persistent wallet: run `npx @aifinpay/mcp init` without a terminal, put its printed env into the MCP client config, then call agent_reload (no restart: payments are on by default); (4) tell the owner the address and the amount in `funding`, the answer to how much to send (the smallest batch at today's rate plus the gas cap; if no rate could be read, ask for the batch price in the native currency at today's rate plus the gas cap and name no number), and offer the dashboard link so the owner can claim the agent (agent_claim_self) and set the working limits in Controls; (5) payable_fetch the URL. Payments are on by default within a built-in ceiling of $5 per payment and $20 per 24 hours, only through a persistent wallet, only to merchants registered with AiFinPay via a quote signed by its backend; an unfunded wallet spends nothing. AIFINPAY_MAX_USD and AIFINPAY_DAILY_USD can only lower that ceiling; AIFINPAY_PAYMENTS_ENABLED=0 turns payments off; AIFINPAY_GATEWAY_ORIGINS, when set, is the only list of payable sites. Moves nothing and signs no payment: for a persistent wallet it signs one short AiFinPay read statement to fetch the owner's Controls. Never asks the owner's limits from the model.
payable_fetch url, max_amount_usd, scope, expected_merchant_id
Fetch a GET resource from an AiFinPay merchant, paying its AIFP-1 402 when needed. Always listed: until a persistent wallet exists (npx @aifinpay/mcp init, then agent_reload) it signs nothing and returns the payment_setup_status checklist with the one next step. Payments are on by default within a built-in ceiling of $5 per payment and $20 per 24 hours (the owner can only lower it in env; the working limits are the dashboard Controls after agent_claim_self) and only ever reach a merchant registered with AiFinPay, through a quote signed by the AiFinPay backend; a 402 never chooses who is paid. Without AIFINPAY_GATEWAY_ORIGINS it pays only a merchant whose site AiFinPay reports as DNS-verified, on that very site (or through the AiFinPay hosted gateway); with it, only the origins the owner listed; AIFINPAY_PAYMENTS_ENABLED=0 turns payments off. Buys a prepaid batch through verified v1.4 on the chain the owner set in AIFINPAY_PAY_CHAIN (Polygon by default; other supported networks require explicit owner selection) — in its native currency (POL, SOL, ETH, AVAX, BNB or XRP), or in the stablecoin the owner set in AIFINPAY_PAY_ASSET (e.g. USDC; gas is still native; on Arc only USDC, which is also its gas) — within owner limits, then reuses its receipt. With scope "merchant" one batch covers every path on the site. Pending payments are recovered without sending another transaction. Other payment protocols are unsupported. The price is the AIFP-1 402 of this exact URL, not the merchant's website plans; if the endpoint is not known, ask the user for it instead of browsing the site.
8 more tools
agent_quota merchant_id, include_exhausted
Read this agent's prepaid quota, 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 much prepaid quota do I have left at mrch_x?
agent_history address, passport, network, source, limit, offset
Read an agent's indexed AiFinPay payment history by wallet address, public passport identifier, or both. Defaults to the configured payment chain and its local wallet. Solana history requires the owner-selected cluster; arbitrary wallet transfers are excluded. Receipts include retained prepaid batches and test payments. Never pass a seed, private key or API secret as a passport.
agent_passport_resolve identifier
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.
settlement_routes route_class
Where an agent can pay today. Lists the splitter v1.4 AIFP-1 routes payable_fetch uses first — one per chain the backend serves (read from the issuer's /api/health and /.well-known/x402.json, pinned against the SDK's deployment registry) with chain_id, assets, quote_endpoint and pay_endpoint — then the legacy splitter v1.3 routes from GET /v1/settlement/routes under legacy_v13. "live": true means payable now through payable_fetch on that chain; a v1.3 entry being disabled says nothing about v1.4. AIFP-1 is merchant monetisation: the protocol fee is included in the quoted price and each quote shows the exact split, creator 0%. AIFP-2/x402 is 100% provider / 0% AiFinPay / 0% creator.
settlement_invoice route_class, chain, asset, gross_amount, merchant_wallet, order_id, valid_until
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.
settlement_solana route_class, chain, asset, gross_amount, merchant_wallet, order_id, valid_until
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.
settlement_casper route_class, chain, asset, gross_amount, merchant_wallet, order_id, valid_until
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.
deployment_info ecosystem, environment, network
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.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=22 |
| Source | github.com/AiFinPay/sdk |
| Install scripts | bufferutil, utf-8-validate, utf-8-validate declare them. This runner does not run them. |
| Tarball | sha512-Y46Gw1l9TR2h81G/ZW5CJfL3XZM4bqCppeGvZc0YKeZde3Pdv6zHjRIKvAx1Q1z4r9wJQl8grqaYRXQX0IrwFA== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 2.16.3 | 2026-11-16 | Starts with no setup | 13 |
| 2.16.2 | 2026-11-12 | Starts with no setup | 13 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40aifinpay/mcp)
New version out? Ask for a fresh report.