Veyra MCP Server

by zapxlabs Your server? Claim it

not responding

Veyra is listed as active in the registry but did not answer our last check. 46 installs a week from npm. It exposes 7 tools. Last commit 19 Sep 2026.

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

Installs per day peak 176 · avg 15 · -73% w/w

a month agotoday

Uptime history 52 days of history · worst day 0%

52 days agonow

1.1%

Uptime 24h

1 of 91 checks

Tools

read from the server

239 ms

Response time

average over 24h

Installs / week

npm and PyPI

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 19 September 2026. No other catalogue keeps this.

19 Sep 2 tool descriptions were rewritten create_payment, get_payment

Veyra does not always answer

Over the last week it answered 15.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://veyra.money/api/mcp

~/.codex/config.toml

[mcp_servers.veyra]
url = "https://veyra.money/api/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

payment

create_payment

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_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`. 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_payment_sources

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

budget

get_budget

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

cancel

cancel_payment

Cancel a payment only while still cancellable.

capabilities

get_capabilities

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

payments

list_payments

List this agent's recent payments.

Endpoints

URL	Transport	State	Latency	Checked
https://veyra.money/api/mcp	streamable-http	answering	54 ms	14 min ago

Alternatives to Veyra

same job, measured the same way

stipend.sh

by graphiker-australia

Non-custodial USDC wallet on Base with spending limits enforced in code, not in a prompt.

64 installs/wk local only

Xenarch MCP

by xenarch-ai

Xenarch — x402 MCP server for AI agent payments. Non-custodial, USDC on Base L2.

110 installs/wk local only

Purser

by ahmad-codex

Wallet for AI agents with on-chain spending limits and owner approval over the limit

local only

CAI MCP

by cailab-hk

CAI MCP server — gives AI agents a custodial wallet, @cai.com email, and vault.

local only

PetaSats

by bsvanon

Buy BSV with USDC on Base through a local non-custodial MCP server.

2 714 installs/wk local only

Cloaked Agent

by cloakedagent

Trustless spending accounts for AI agents on Solana with on-chain enforced limits.

38 installs/wk local only

WritersLogic AI Agents (x402)

by writerslogic

Pay-per-call AI agents over x402. Settled in USDC on Base with a per-call spending cap.

448 installs/wk local only

SpendTheBits Gift Cards

by jkambo1986-collab

Let an AI agent buy gift cards with USDC over x402, within limits the wallet owner sets.

52 installs/wk answering

Veyra — questions

Answers built from our own checks of this server.

What can Veyra do?

It exposes 7 tools, read directly from the server on our last check. Among them: cancel_payment, create_payment, get_budget, get_capabilities, get_payment, list_payments and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Veyra working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 1 of 91 checks got a reply (1.1%), average response time 239 ms. The bar chart above shows every period we have measured.

The registry lists Veyra as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Veyra?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Veyra need an API key?

No. Veyra completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Veyra?

It answers our handshake in 239 ms on average, which is faster than 56% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Veyra?

The npm package veyra-mcp was installed 46 times in the last week. Week over week that is -73%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Veyra open source?

The code is open source: it is published under the MIT licence, written in TypeScript, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at veyra.money, which runs on its operator's own terms.