Log inSubmit server
AiFinPay logo

AiFinPay

MCP tools for agent identity, wallet discovery, payment history, settlement routes, and owner-controlled HTTP API payments.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install AiFinPay

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "aifinpay": {
      "command": "npx",
      "args": [
        "-y",
        "@aifinpay/mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 13 tools correctly (16d ago).

Overview

The AiFinPay MCP server exposes agent identity, wallet, payment, quota, settlement, and deployment tools through MCP. It can read local wallet information and construct non-signing settlement invoices, while owner-enabled payment mode can fetch approved HTTP resources using configured limits. Polygon is the default EVM chain; Solana support is present as a candidate flow with disabled canonical records. Use it when an agent needs controlled access to paid APIs or visibility into its AiFinPay payment state.

Use cases

  • Read an agent’s public wallet addresses
  • Inspect payment history and spending quotas
  • Fetch owner-approved paid HTTP resources
  • Build non-signing settlement invoices
  • Resolve Agent Passport wallet bindings

Key features

  • MCP tools for identity and wallet discovery
  • Owner-controlled paid HTTP fetching
  • Payment history and quota inspection
  • EVM, Solana, and Casper invoice construction
  • Agent Passport identity resolution
  • Deployment and settlement status lookup

Tools13

What AiFinPay lets your agent do. Expand a tool for its parameters.

Verified live~3.0k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 44d

What it can do

From the 13 tools this server returned when we ran it; 13 declare their own safety hints.

Runs commands · 1Can delete or modify data · 1Handles credentials · 1Makes network requests · 3Read-only tools · 11
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age170 days
Maintainers2

Observed 2026-10-27 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @aifinpay/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads2.9kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed13Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How AiFinPay works

What AiFinPay does

The AiFinPay MCP server gives an AI agent an MCP interface for payment infrastructure and related account data. It covers public wallet addresses, owner linking, quotas, payment history, Agent Passport resolution, settlement routes, invoices, and deployment status. The package is relevant to the 💰 Finance & Fintech category because it connects agent workflows with API payments and blockchain settlement records.

The server also includes a merchant-facing model elsewhere in the repository: HTTP 402 paywalls and per-request monetization are supported through the gate packages. The MCP surface described here is primarily agent-facing. It does not expose private keys or seed phrases through public tools.

How it works

The MCP process runs locally and uses configured wallet files and owner settings. In its default state, it is read-only: address and account data can be inspected, but quote creation or invoice construction does not itself complete a payment. Settlement invoice tools produce and validate non-signing EVM, Solana, or Casper invoices.

Payment execution is conditional. The owner must enable payments and set spending limits and approved gateway origins before payable_fetch can sign and broadcast a locally controlled purchase. That tool performs a GET request against an owner-approved AIFP-1 merchant and buys a prepaid batch on the explicitly configured EVM v1.4 chain, with Polygon as the default.

The Solana flow supports native SOL and classic SPL USDC or USDT in the candidate implementation. It requires an explicitly selected Solana cluster or mode, a fee and rent budget, and keys kept by the operator. The same local wallet ledger can cover EVM and Solana unresolved purchases.

Setup and configuration

Run the MCP package with npx @aifinpay/mcp. Node and Python SDKs are available separately through @aifinpay/agent and aifinpay-agent. The repository also provides packages for merchant gating and agent skills.

A basic installation does not require payment activation. To expose an operational paid-fetch path, the owner sets AIFINPAY_PAYMENTS_ENABLED=1, AIFINPAY_MAX_USD, AIFINPAY_DAILY_USD, and AIFINPAY_GATEWAY_ORIGINS, along with a native gas cap. The documented development mode, AIFINPAY_MODE=dev, adds a development-only quote inspection tool.

Tools and capabilities

The AiFinPay MCP server currently registers tools for:

  • Reading EVM, Solana, and Casper public addresses, and reloading local wallet files.
  • Linking an agent to its owner dashboard with a one-time claim URL.
  • Reading quotas, indexed or retained payment history, and runtime-verified settlement routes.
  • Resolving public Agent Passport identities and verified wallet bindings.
  • Fetching an approved paid resource when owner payment controls are active.
  • Building non-signing settlement invoices for EVM, Solana, and Casper.
  • Reading deployment addresses, program IDs, and settlement status across supported ecosystems.

Limitations and notes

Payment tools are intentionally restricted by owner configuration. Without that configuration, the MCP server signs no payment. The owner claim operation signs only an AiFinPay claim challenge for the agent’s own address and does not move funds.

Solana records remain disabled in the canonical registry. The source tests use injected synthetic approved records, so they do not prove that a deployed program is active or that a funded network accepts payments. High-level payment execution refuses before signing or making an HTTP request when the selected registry record is unavailable. Treat the Solana implementation as a candidate flow rather than an enabled production route.

The package versions in the repository are local source versions and do not establish publication or registry status. Release, dependency-lock, and deployment verification are separate concerns.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about AiFinPay

AiFinPay is an MCP server that connects AI agents to local wallet and payment infrastructure for approved HTTP API access. Its main tools read public addresses, quotas, payment history, Agent Passport identities, settlement routes, deployment data, and non-signing invoices, with owner-enabled paid fetching for configured merchants.

Run `npx @aifinpay/mcp` to start the MCP package. The repository also provides `pip install aifinpay-agent` for Python and `npm install @aifinpay/agent` for the Node or TypeScript SDK.

Set `AIFINPAY_PAYMENTS_ENABLED=1` and configure `AIFINPAY_MAX_USD`, `AIFINPAY_DAILY_USD`, and `AIFINPAY_GATEWAY_ORIGINS`, plus a native gas cap. Without owner payment configuration, the server remains read-only and `payable_fetch` cannot complete purchases.

Yes, AiFinPay can be used with Cursor as a standard MCP server because it runs through the normal `npx @aifinpay/mcp` command and has no documented client-specific requirement.

Solana payment execution is included as a candidate flow, supporting native SOL and classic SPL USDC or USDT.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAiFinPay AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/aifinpay?style=directory)](https://allmcps.com/mcp/aifinpay)
HTML Embed
<a href="https://allmcps.com/mcp/aifinpay"><img src="https://allmcps.com/api/badge/aifinpay?style=directory" alt="AiFinPay on AllMCPs" /></a>