Veyra のリモート MCP サーバーとは何ですか?
Veyra のリモート MCP サーバーは、https://veyra.money/api/mcp にホストされた Model Context Protocol エンドポイントです。AI アシスタントはローカルに何もインストール・実行することなく接続できます。
@Veyra
基本情報
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/mcpclaude mcp add veyra --transport http https://veyra.money/api/mcpReturn 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.
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.
https://veyra.money/api/mcp (Streamable HTTP)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" } } }
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 allowlistget_budget — Return remaining daily allowance and policy summarylist_payment_sources — List masked payment sources available to this agent, including whether each can settle unattendedcreate_payment — Create a payment intentget_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_urllist_payments — List this agent's recent paymentscancel_payment — Cancel a payment only while still cancellableinitialize request when checked on 2026-11-13.Sources: Website, Submission.
Veyra のリモート MCP サーバーは、https://veyra.money/api/mcp にホストされた Model Context Protocol エンドポイントです。AI アシスタントはローカルに何もインストール・実行することなく接続できます。
エンドポイント https://veyra.money/api/mcp を Claude Code、Cursor、VS Code など任意の MCP 対応クライアントに追加してください。このページのセットアップ手順で各クライアントを一度に設定できます。
いいえ。Veyra の MCP サーバーは認証不要です——エンドポイント URL で直接接続できます。
Veyra は streamable-http エンドポイントを公開しており、これはリモート MCP サーバーで広く使われ、主要な MCP クライアントがサポートするトランスポートです。
Remote MCP for AI image, video, music, speech and custom voice generation. Discover models and input schemas for free; authorize your APIXO account to generate media and check results.
AOI is a commercial environmental-intelligence gateway that gives AI agents programmatic access to 38 real-world intelligence capabilities — climate risk, satellite monitoring, methane detection, water & soil, vegetation
Checks one specific street address in the City of Gold Coast or Brisbane City, Queensland, Australia (any suburb, e.g. Surfers Paradise, Southport, Robina, Coomera, Kangaroo Point, New Farm, Chapel Hill) using official o
Search and read current AWS documentation, check regional availability and load AWS agent skills, with no AWS account needed.
Convert web pages to clean Markdown and retrieval-ready chunks with browser rendering support.
コメント