Veyra

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

Sollte ich dies verwenden

Qualität und Sicherheit

A
Qualität der Beschreibung
94%
Vollständigkeit des Schemas
60%
Qualität der Benennung
100%
Risiko der Vergiftung
100%
Übereinstimmung der Berechtigungen
100%
Einhaltung des Protokolls
100%

Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.

Kontextkosten

~755Tokens (Tool-Definitionen)
~462 BTypische Antwortgröße
Mittlere Auswirkung auf die Aufmerksamkeit (0.59% von 128k Kontext)

Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.

Installieren

Installation mit einem Klick

Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:

{
  "mcpServers": {
    "veyra": {
      "command": "npx",
      "args": [
        "veyra-mcp"
      ]
    }
  }
}

Ausführbare Pakete

npmveyra-mcp0.1.1stdio

Remote-Endpunkte

https://veyra.money/api/mcpstreamable-http

Was es kann

Tool-Inventar

Tools (7)

🟢 Nur lesen🟡 Schreiben🔴 Löschen⚪ Unbekannt
🟢get_capabilities

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

Eingabe-Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢get_budget

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

Eingabe-Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢list_payment_sources

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

Eingabe-Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟡create_payment(amount, asset, recipient, network, reason, ...)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "amount": {
      "type": "string",
      "description": "Decimal string, e.g. 4.50"
    },
    "asset": {
      "type": "string",
      "description": "e.g. USDC"
    },
    "recipient": {
      "type": "string",
      "description": "Destination address. Must be a valid address for the network, e.g. 0x… on base."
    },
    "network": {
      "type": "string",
      "description": "e.g. base"
    },
    "reason": {
      "type": "string"
    },
    "idempotency_key": {
      "type": "string",
      "description": "Agent-generated unique key; retries must reuse it"
    }
  },
  "required": [
    "amount",
    "asset",
    "recipient",
    "network",
    "reason",
    "idempotency_key"
  ],
  "additionalProperties": false
}
🟢get_payment(payment_id)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "payment_id": {
      "type": "string"
    }
  },
  "required": [
    "payment_id"
  ],
  "additionalProperties": false
}
🟢list_payments(limit)

List this agent's recent payments.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "number"
    }
  },
  "additionalProperties": false
}
🔴cancel_payment(payment_id)

Cancel a payment only while still cancellable.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "payment_id": {
      "type": "string"
    }
  },
  "required": [
    "payment_id"
  ],
  "additionalProperties": false
}

Community

Diesen Server bewerten

Nachweis

Aktuelle Beobachtungen

verifiziertVersion nicht aufgezeichnet7 Tools
verifiziertVersion nicht aufgezeichnet7 Tools