# Veyra (remote · veyra.money)

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

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `veyra.money`: 74/100 (this document), [markdown](https://verifymcp.io/servers/zapxlabs-veyra/api-mcp.md), [page](https://verifymcp.io/servers/zapxlabs-veyra/api-mcp)
- npm · `veyra-mcp`: 39/100, [markdown](https://verifymcp.io/servers/zapxlabs-veyra/veyra-mcp.md), [page](https://verifymcp.io/servers/zapxlabs-veyra/veyra-mcp)

## Channel facts

- Endpoint: `https://veyra.money/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 577 tokens (~82/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 85/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 56% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Veyra MCP server?

Veyra is a hosted endpoint at https://veyra.money/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http zapxlabs-veyra 'https://veyra.money/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "zapxlabs-veyra": {
      "url": "https://veyra.money/api/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.zapxlabs-veyra]
url = "https://veyra.money/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zapxlabs-veyra": {
      "type": "remote",
      "url": "https://veyra.money/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add zapxlabs-veyra --url 'https://veyra.money/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  zapxlabs-veyra:
    url: "https://veyra.money/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "zapxlabs-veyra": {
      "Transport": "http",
      "Url": "https://veyra.money/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add zapxlabs-veyra -t streamable-http -u 'https://veyra.money/api/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 74, 0)

- [security] Tool “create_payment” rewrote its description, which is the text the model reads
- [security] Tool “get_payment” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 56 → 82
- [functional improvement] Stability: unverified → 0.03

### 2026-09-19 (score 74)

First indexed and scored.

## MCP tools (7)

### `get_capabilities` (~36 tokens)

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

### `get_budget` (~33 tokens)

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

### `list_payment_sources` (~29 tokens)

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

### `create_payment` (~349 tokens)

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.

Input parameters:

- `amount` (string, required): Decimal string, e.g. 4.50
- `asset` (string, required): e.g. USDC
- `idempotency_key` (string, required): Agent-generated unique key; retries must reuse it
- `network` (string, required): e.g. base
- `reason` (string, required)
- `recipient` (string, required): Destination address. Must be a valid address for the network, e.g. 0x… on base.

### `get_payment` (~82 tokens)

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.

Input parameters:

- `payment_id` (string, required)

### `list_payments` (~23 tokens)

List this agent's recent payments.

Input parameters:

- `limit` (number)

### `cancel_payment` (~25 tokens)

Cancel a payment only while still cancellable.

Input parameters:

- `payment_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/zapxlabs-veyra/api-mcp#diagnostics

## Score history

- 2026-09-20: 74
- 2026-09-19: 74

## Common questions

### What is the Veyra MCP server?

Veyra is an MCP server listed in the public MCP registry as io.github.zapxlabs/veyra. Give AI agents a wallet with a spending limit. Non-custodial USDC on Base, server-enforced limits. This page covers its hosted endpoint (https://veyra.money/api/mcp).

### Is the Veyra MCP server safe to use?

Veyra scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Veyra MCP server expose?

Veyra exposes 7 tools: get_capabilities, get_budget, list_payment_sources, create_payment, get_payment, and 2 more. Their descriptions and schemas cost roughly 577 tokens of context every time the server is loaded.

### Does the Veyra MCP server require authentication?

Yes. Veyra asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Veyra MCP server still maintained?

Veyra is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://veyra.money/api/mcp
- Authorisation metadata: https://veyra.money/.well-known/oauth-protected-resource/api/mcp
- Repository: https://github.com/zapxlabs/veyra-mcp
- Website: https://veyra.money/
- Changelog RSS feed: https://verifymcp.io/servers/zapxlabs-veyra/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/zapxlabs-veyra/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/zapxlabs-veyra/api-mcp