MCP.so
ログイン
V

Veyra MCP Server

@Veyra

基本情報

トランスポート

streamable-http

認証方式

不要

最終更新

カテゴリ

その他

作者

Veyra

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.

接続情報

https://veyra.money/api/mcp

セットアップ

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

Veyra MCP Server のツール

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.

概要

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.

よくある質問

1

Veyra のリモート MCP サーバーとは何ですか?

Veyra のリモート MCP サーバーは、https://veyra.money/api/mcp にホストされた Model Context Protocol エンドポイントです。AI アシスタントはローカルに何もインストール・実行することなく接続できます。

2

Veyra の MCP サーバーにはどう接続しますか?

エンドポイント https://veyra.money/api/mcp を Claude Code、Cursor、VS Code など任意の MCP 対応クライアントに追加してください。このページのセットアップ手順で各クライアントを一度に設定できます。

3

Veyra の MCP サーバーは認証が必要ですか?

いいえ。Veyra の MCP サーバーは認証不要です——エンドポイント URL で直接接続できます。

4

Veyra の MCP サーバーはどのトランスポートを使用しますか?

Veyra は streamable-http エンドポイントを公開しており、これはリモート MCP サーバーで広く使われ、主要な MCP クライアントがサポートするトランスポートです。

コメント