MCP.so
Sign In
V

Veyra MCP Server

@Veyra

Basic information

Transport

streamable-http

Authentication

None

Last updated

Category

Other

Author

Veyra

About Veyra MCP Server

Veyra is a financial permission layer for AI agents. Connect a wallet you already own (MetaMask, Base / Coinbase passkey or WalletConnect), set what an agent may spend, and paste one MCP endpoint into Claude Code, Cursor, Codex or any MCP client that can send a bearer header. Per-payment and daily caps, an auto-approve band, an ask-for-approval band and an optional recipient allowlist are enforced on Veyra's server, so the agent cannot raise its own limits. Payments are USDC on Base only, and Veyra never holds funds or keys. A simulated source moves no money, so you can test the approved, held and blocked paths first.

Connection details

https://veyra.money/api/mcp

Setup

claude mcp add veyra --transport http https://veyra.money/api/mcp

Veyra MCP Server tools

7

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

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

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

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.

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.

List this agent's recent payments.

Cancel a payment only while still cancellable.

Overview

What it is

Veyra is a financial permission layer for AI agents. Connect a wallet you already own (MetaMask, Base / Coinbase passkey or WalletConnect), set what an agent may spend, and paste one MCP endpoint into Claude Code, Cursor, Codex or any MCP client that can send a bearer header. Per-payment and daily caps, an auto-approve band, an ask-for-approval band and an optional recipient allowlist are enforced on Veyra's server, so the agent cannot raise its own limits. Payments are USDC on Base only, and Veyra never holds funds or keys. A simulated source moves no money, so you can test the approved, held and blocked paths first.

From the publisher's website: Connect wallets once, set agent spend limits, and ship one MCP endpoint. Policy stays on our servers — agents never get your keys.

Connect

  • Endpoint: https://veyra.money/api/mcp (Streamable HTTP)
  • Authentication: no authentication

Claude Code:

claude mcp add veyra --transport http https://veyra.money/api/mcp

Other clients (mcpServers config):

{ "mcpServers": { "veyra": { "type": "http", "url": "https://veyra.money/api/mcp" } } }

Tools

Read from the server's tools/list on 2026-11-13:

  • get_capabilities — Return the rails, networks, assets and policy constraints actually available to this endpoint right now, including any recipient allowlist
  • get_budget — Return remaining daily allowance and policy summary
  • list_payment_sources — List masked payment sources available to this agent, including whether each can settle unattended
  • create_payment — Create a payment intent
  • get_payment — 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
  • list_payments — List this agent's recent payments
  • cancel_payment — Cancel a payment only while still cancellable

Notes

  • Description above is the publisher's own summary from their submission; check the website for plans, pricing and limits.
  • The endpoint answered a standard MCP initialize request when checked on 2026-11-13.

Sources: Website, Submission.

Frequently asked questions

1

What is the Veyra remote MCP server?

The Veyra remote MCP server is a hosted Model Context Protocol endpoint at https://veyra.money/api/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the Veyra MCP server?

Add the endpoint https://veyra.money/api/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the Veyra MCP server require authentication?

No. Veyra's MCP server does not require authentication — you can connect directly with the endpoint URL.

4

Which transport does the Veyra MCP server use?

Veyra exposes a streamable-http endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments