pursestring
Related Servers
Alternatives to pursestring
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceLocal-first spend controls for AI agents. Budgets, human approvals and a tamper-evident audit trail for any MCP server. Deterministic. No custody.9MIT- AlicenseAqualityCmaintenanceSpending limits for AI agents. Create budgets, enforce limits, track spend across x402, cards, MPP, or any payment rail.7Apache 2.0
- AlicenseNot gradedqualityBmaintenanceGoverns AI agents' spending by enforcing budgets, approvals, and kill switches before any payment, providing an MCP interface for tool calls with policy checks.377 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to route PayPal money-moving requests through deterministic spending rules, AI injection and intent checks, human approvals, and tamper-evident audit logging.16 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables human-in-the-loop authorization for AI agent transactions, allowing real-time approval or denial of purchases based on configurable spending limits, vendor blocklists, daily caps, and category restrictions.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to pay merchants with policy-limited single-use virtual cards funded from fiat or USDC sources, enforcing spending limits, merchant rules, and owner approval. Card numbers stay out of the agent's context, with cards filled into checkout pages or revealed only to the owner.Apache 2.0
TDQS
Scored across 5 tools
Each tool maps to a distinct stage of the spend lifecycle: policy dry-run, intent submission, status polling, card issuance, and payment. The only near-overlap is check_policy_compliance versus submit_purchase_intent, but the descriptions clearly distinguish a non-submitting evaluation from an actual declaration.
All names use consistent snake_case with a clear verb_noun structure: check_policy_compliance, submit_purchase_intent, request_ephemeral_card, send_payment, get_intent_status. The pattern is predictable throughout.
Five tools is well-scoped for this narrow spending-control workflow, with each tool earning its place. There are no redundant or trivial tools.
The core lifecycle is covered: policy check, intent creation, human-in-the-loop status wait, virtual card issuance, and payment. Minor gaps exist around canceling an intent or voiding a card, but the main agent workflow has no dead ends.