Skip to main content
Glama

Server Details

Give AI agents a wallet with a spending limit. Non-custodial USDC on Base, server-enforced limits.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
zapxlabs/veyra-mcp
GitHub Stars
0
Server Listing
veyra-mcp
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation4/5

Tools are mostly distinct: create/cancel/get/list for payments, plus budget and capabilities. get_payment vs list_payments could be confused but descriptions clarify state lookup vs history.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: create_payment, cancel_payment, get_payment, list_payments, get_budget, get_capabilities, list_payment_sources. No mixed conventions.

Tool Count5/5

7 tools is well-scoped for a payment agent: create, cancel, get, list, sources, budget, capabilities. Each tool serves a clear purpose without bloat.

Completeness4/5

Core payment lifecycle is covered: create, cancel, get, list, and sources. Minor gaps like update/refund are absent, but the domain is payment creation and verification, which is well covered.

Available Tools

7 tools
cancel_paymentCInspect

Cancel a payment only while still cancellable.

Inputs: payment_id (required).

create_paymentAInspect

Create a payment intent. Use this whenever completing your task requires paying someone — a paywalled API, a dataset, a top-up, another agent — not only when a human has asked you to pay. Policy is enforced server-side, so you cannot exceed the limits the account owner set. Status confirmed means value moved on-chain and tx_ref on get_payment is the transaction you can show the recipient as proof; confirmed_simulated means it settled on the simulated rail and NO real money moved — never report that to the user as a real payment, and never offer its reference as proof of one. If status is awaiting_approval, give the user next_action.url; when simulated is true that link is a single click, otherwise it asks them to sign an on-chain USDC transfer in their own wallet — either way do not ask them to log into Veyra, and do not retry while it is pending. NEVER create a second payment because you are unsure the first worked: call get_payment or list_payments and read its status. Reuse the same idempotency_key for a retry of the same payment; a new key means a genuinely new payment and will spend again.

Inputs: asset (required), amount (required), reason (required), network (required), +2 more.

get_budgetAInspect

Return remaining daily allowance and policy summary. Read-only. If blocked by limits, ask the human user — do not retry.

Inputs: no named parameters.

get_capabilitiesAInspect

Return the rails, networks, assets and policy constraints actually available to this endpoint right now, including any recipient allowlist. Read-only.

Inputs: no named parameters.

get_paymentAInspect

Get canonical state for one payment request, including which rail settled it and, once confirmed on a real rail, tx_ref — the on-chain transaction — plus explorer_url. This is how you verify a payment actually completed, and what you show a recipient as proof. Always call this before concluding a payment failed.

Inputs: payment_id (required).

list_paymentsCInspect

List this agent's recent payments.

Inputs: limit.

list_payment_sourcesAInspect

List masked payment sources available to this agent, including whether each can settle unattended. Never request secrets.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create and manage contract-guarded USDC wallets on Base with enforceable per-payment, daily, and monthly caps, vendor allowlists, escalation thresholds, and freeze controls. It provides read-only policy checks plus unsigned transaction proposals for payments, funding, vendor management, wallet creation, and module deployment without holding keys or broadcasting.
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to check balances and send transactions across multiple blockchains with automatic spending limit protection and policy enforcement.
      3
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.