MCP Server Enables AI Agents to Make Real Purchases with Ephemeral Virtual Cards

A developer has created an MCP server that enables AI agents to make real purchases using ephemeral virtual Visa cards. This addresses a key limitation in current agent frameworks: while agents can browse, search, compare, and select products, they typically cannot complete checkout processes.
How It Works
The agent calls the MCP tool with a purchase intent that includes merchant, amount, and description. The request goes to the user for approval via MFA. Upon approval, a virtual Visa card is issued just-in-time with specific constraints:
- Locked to the specified merchant
- Capped at the approved amount
- 15-minute time-to-live (TTL)
The agent receives the card credentials, completes checkout, and the card self-destructs after use.
Security Architecture
The system uses two separate financial rails:
- User → Stripe → PayClaw balance (funding)
- PayClaw → Lithic-issued virtual Visa → merchant (spending)
Real card credentials never enter the agent's context by architectural design, not just policy. The rails don't intersect.
Security Benefits for Self-Hosted Setups
For users running local models, this approach limits potential damage from prompt injection attacks. The worst-case scenario is limited to:
- One transaction only
- Bounded by the approved amount
- Limited to the approved merchant
- Within a 15-minute window
This contrasts with having persistent card numbers sitting in context.
Key Differences from Previous Tools
This approach differs from the ClawHub tool that was pulled, which collected actual card PANs in the agent chat context. This new system issues ephemeral virtual cards from a BaaS provider, ensuring the agent never has access to real credentials.
Technical Stack
- TypeScript MCP server
- Lithic for card issuing
- Stripe for funding
The tool uses standard MCP tool registration and should work with anything running an MCP client, including Claude, LM Studio with MCP support, and other compatible systems.
Current Status
A dev sandbox is currently available. The developer is seeking feedback on architecture, security model, use cases, and general testing in the sandbox environment.
📖 Read the full source: r/LocalLLaMA
👀 See Also

PeaDB: Redis-Compatible Database Coded with AI Assistants in C++20
A developer created PeaDB, a Redis 7.2.5 drop-in replacement written in C++20 using Codex, Copilot, and Claude, implementing ~147 commands with persistence, replication, and cluster support. Benchmarks show performance close to Redis.

Exasol Releases MCP Server for Database Context in AI Agent Workflows
Exasol has released an MCP Server that enables databases to provide context to AI agents about available data, business rules, and safe interaction methods. The server is read-only by default, supports high-concurrency workflows, and can be deployed on-prem, in cloud, or hybrid environments.

context-link v1.0.0: Local MCP server reduces Claude Code token usage by 91%
context-link v1.0.0 is a local MCP server that indexes codebases with Tree-sitter to serve Claude only the exact symbols, dependencies and structure needed, reducing token usage by 91% in specific cases and 70-80% across full tasks.

Claude Command Center: Open-Source Dashboard for Claude Code Analytics
Claude Command Center is a local dashboard that reads your ~/.claude/ directory to display Claude Code session data, costs, and MCP server configurations. Built entirely using Claude Code with an Express backend and React frontend, it requires zero configuration and runs locally with no cloud or telemetry.