Finance · Remote MCP server
Agentic Payments Sandbox
Approval layer for AI agent payments: rules, budgets, human approvals. Sandbox, test credentials.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.pinkwallet/agentic-payments-sandbox- Version
- 0.1.0
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- com.pinkwallet
- Namespace
- Namespace verified by the MCP Registry via the domain pinkwallet.com · how
- Website
- pinkwallet.com/agentic/
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://agentic-sandbox.pinkwallet.com/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Agentic Payments Sandbox
Agentic Payments Sandbox is a remote MCP server: there is nothing to install. Its endpoint is https://agentic-sandbox.pinkwallet.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More finance servers
| Server | Runs |
|---|---|
| agentgates.aiConfidential compute and inference sold to agents over x402 USDC, plus an agent wallet over MCP. | Remote · HTTPLive check: sign-in required |
| Agentguard47Read-only MCP server for coding-agent traces, alerts, costs, usage, and budget health. | Local · stdio |
| Agentic AiDeal intelligence for agents: SEC-verified financials, validation, institutional deal scoring. | Remote · HTTPLive check: ✓ handshake |
| Agentic CommerceMCP server for Boson Protocol - on-chain agentic commerce for physical & digital goods. | Remote · HTTPLive check: ✓ handshake |
| Agentic Terminal DirectoryVerified merchants accepting agentic payments on Lightning/L402/BOLT12/USDT - search, verify, pay. | Remote · HTTPLive check: ✓ handshake |
| Agentic Wallet Guardian V3Explainable ALLOW/WARN/BLOCK risk decisions for AI agent actions before execution, signed as OAA. | Local · stdio |
| agentic-payNon-custodial payment engine for AI agents - BTC, ETH, USDT, USDC, XRP, XMR, ZEC. | Local · stdio |
| AgenticBooksStartup books from live bank and billing feeds: P&L, balances, approvals, period close. | Remote · HTTPLive check: sign-in required |