MIDAS Protocol
- BbrainFrance/Agent_payment_protocol
MIDAS Protocol is a MCP server that exposes agent-oriented payments, lending, and escrow over streamable HTTP so coding agents can run financial workflows with a MIDAS API key.
About
MIDAS Protocol is a remote Model Context Protocol server that gives developers and teams a single financial layer for AI agents: payments, lending, escrow, and related money flows. You connect Claude Code, Cursor, or similar clients to the hosted MCP endpoint with a Bearer token from agent registration, then let your agent invoke tools instead of hand-rolling Stripe webhooks and escrow state machines. It fits SaaS, agent marketplaces, and API products where autonomy must settle transactions safely. Register once, point your MCP client at the streamable HTTP URL, and treat treasury logic as agent-callable infrastructure during the build phase when integrations dominate your calendar.
- Streamable HTTP MCP at https://mcp.midasprotocol.org/mcp with Bearer MIDAS API key auth
- Payments, lending, and escrow primitives aimed at AI agent commerce
- Agent registration via POST https://api.midasprotocol.org/agents/register for API keys
- Version 1.0.0 hosted remote—no local stdio package in the registry manifest
- Complete financial infrastructure positioning for agent-native products
MIDAS Protocol by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http midas-protocol https://mcp.midasprotocol.org/mcp --header "Authorization: Bearer YOUR_TOKEN"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | Required |
| Repository | BbrainFrance/Agent_payment_protocol ↗ |
What it does
Wire your coding agent into programmable payments, escrow, and lending so autonomous workflows can move money without custom fintech glue.
Who is it for?
Best when you're shipping agent products that need escrow, lending, or programmatic payouts without becoming a fintech team first.
Skip if: Static sites, local-only scripts with no agent wallet story, or teams that only need a simple Stripe Checkout link with no MCP layer.
What you get
After you register an agent and add the remote MCP server with Authorization, your agent can call MIDAS financial tools from the IDE instead of maintaining one-off payment integrations.
- Registered agent identity with MIDAS API credentials
- IDE-connected MCP session against the hosted MIDAS endpoint
- Agent-callable payment, escrow, and lending operations in your workflow
By the numbers
- MCP protocol version in manifest schema: 2025-12-11
- Server package version: 1.0.0
- Remote transport: streamable-http at mcp.midasprotocol.org/mcp
Recommended MCP Servers
$THREE TokenPrice, hold, and burn $THREE on Solana — the first MCP server whose actions burn a token.89
402 McpAI agents discover, pay for, and consume any Lightning-gated API autonomously
9192 Public ComputeRemote MCP for 9192 discovery, pricebook, payment rails, GET_PULSE quotes, and receipt checks.
Aarna McpAarna - 34 tools for swap quotes, liquidity pools, and trading dataAave McpAave - 6 tools for lending rates, supply, and borrow data
AbraFlexiMCP server for AbraFlexi ERP — invoices, contacts, products, bank transactions.1How it compares
Agent financial infrastructure MCP, not a code-quality skill or generic CRUD database server.
FAQ
Who is MIDAS Protocol for?
and small-team developers using Claude Code, Cursor, or Codex who want AI agents to handle payments, escrow, and lending through one MCP remote.
When should I use MIDAS Protocol?
Use it during Build integrations when you are connecting autonomous agents to monetization, marketplaces, or escrow before you ship production money flows.
How do I add MIDAS Protocol to my agent?
Register via POST https://api.midasprotocol.org/agents/register, copy your Bearer API key, then add the streamable HTTP MCP server URL https://mcp.midasprotocol.org/mcp with the Authorization header in your client’s MCP config.