Grip MCPofficial
A
licenseA
qualityD
maintenanceProvides a non-custodial USDC wallet on Base for AI agents, with human-in-the-loop approval for every payment.
4
12 npm
MIT
veyra-mcp
by zapxlabs
Related Servers
Alternatives to veyra-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to quote, authorize, submit, and verify agent-to-agent USDC payments on Base through standard MCP tools over stdio.41,757 npmMIT
- AlicenseAqualityBmaintenancePayment infrastructure MCP server enabling AI agents to make gasless USDC payments on Base and JIT single-use virtual card checkouts, with zero-trust card handling, merchant checkout hints, and signed receipts.13138 npm1MIT
- AlicenseAqualityDmaintenanceAn MCP server for USDC payments on Base, enabling AI agents to check balances, send payments, generate payment requests, and view transaction history.41MIT
@arispay/payagent-mcpofficial
AlicenseAqualityAmaintenanceEnables AI agents to call paid APIs and settle HTTP 402 payment challenges with USDC on Base, without private keys ever being involved.7173 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to make payments over x402-priced HTTP APIs using USDC on Monad testnet, with policy enforcement, budgets, and approval workflows, without exposing private keys.6AGPL 3.0
TDQS
A3.7/5.0
Scored across 7 tools
Disambiguation4/5
Each tool targets a distinct action or resource: capabilities, budget, payment sources, and individual payments are clearly separated. The only mild overlap is between get_capabilities and get_budget, since both surface policy/limit information, but their focuses are distinct enough to avoid real confusion.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern: get_, list_, create_, cancel_. Reading operations consistently use get_ for single resources and list_ for collections, making the naming predictable and easy to navigate.
Tool Count5/5
Seven tools is well-scoped for a payment-focused server. Each tool covers a necessary part of the payment lifecycle or policy context without unnecessary duplication or bloat.
Completeness5/5
The surface covers the full agent-relevant payment workflow: discover capabilities, check budget, list payment sources, create a payment, retrieve one payment, list past payments, and cancel when possible. There are no obvious dead ends or missing core operations for the stated purpose.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive