Veyra MCP server
io.github.zapxlabs/veyrazapxlabsstreamable-httpv0.1.2Scanned
Give AI agents a wallet with a spending limit. Non-custodial USDC on Base, server-enforced limits.
7 tools: 1 can delete or cancel things, 1 do something that can't be undone and 5 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Veyra MCP server can do
The Veyra MCP server is published by the GitHub account zapxlabs. It has 7 tools. It can delete or cancel things (1 tool: cancel_payment) and do things that cannot be undone, such as sending, paying or publishing (create_payment). 5 tools only read.
1 tool brings in text other people can write (get_payment); 1 tool can send data out of your system (create_payment).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 0.1.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Deletes or cancels 1Claude Code: deny
cancel_paymentCancel a payment only while still cancellable.No findings
Why it is in this group
- The name "cancel_payment" says "cancel": a word for removing or ending something.
Description, as the server wrote it Cancel a payment only while still cancellable.
Can't be undone 1Claude Code: ask
create_paymentCreate a payment intent.Can send data outNo findings
Why it is in this group
- The name "create_payment" says "create": a word for a change.
- The name "create_payment" also says "payment": a word that usually means money moves, which cannot be taken back.
- The input addresses people (input.recipient): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.recipient): what the tool writes goes there.
Description, as the server wrote it 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.
Only reads 5Show 5 read-only tools
get_budgetReturn remaining daily allowance and policy summary.No findings
Why it is in this group
- The name "get_budget" says "get": a word for reading.
Description, as the server wrote it Return remaining daily allowance and policy summary. Read-only. If blocked by limits, ask the human user — do not retry.
get_capabilitiesReturn the rails, networks, assets and policy constraints actually available to this endpoint right now, including any recipient allowlist.No findings
Why it is in this group
- The name "get_capabilities" says "get": a word for reading.
Description, as the server wrote it Return the rails, networks, assets and policy constraints actually available to this endpoint right now, including any recipient allowlist. Read-only.
get_paymentGet 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`.Reads text others writeNo findings
Why it is in this group
- The name "get_payment" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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_sourcesList masked payment sources available to this agent, including whether each can settle unattended.No findings
Why it is in this group
- The name "list_payment_sources" says "list": a word for reading.
Description, as the server wrote it List masked payment sources available to this agent, including whether each can settle unattended. Never request secrets.
list_paymentsList this agent's recent payments.No findings
Why it is in this group
- The name "list_payments" says "list": a word for reading.
Description, as the server wrote it List this agent's recent payments.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:13 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 destructive, 1 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://veyra.money/api/mcp: tools/list returned 7 tools to an anonymous client, including cancel_payment (destructive), create_payment (irreversible)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http veyra https://veyra.money/api/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http veyra https://veyra.money/api/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__veyra__get_capabilities",
"mcp__veyra__get_budget",
"mcp__veyra__list_payment_sources",
"mcp__veyra__get_payment",
"mcp__veyra__list_payments"
],
"ask": [
"mcp__veyra__create_payment"
],
"deny": [
"mcp__veyra__cancel_payment"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as veyra. Review it before you use it.
Capability tags behind 2 rules
- mcp__veyra__create_payment outbound
- mcp__veyra__get_payment untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.zapxlabs/veyra/verify?hash=11e0eb91e01028cefda1193017b477c1ac390c89a2a6cb100d56e5348d34b8c0" | jq -e '.changed == false'Pinned hash 11e0eb91e010, from Nov 20, 2026, 19:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.zapxlabs/veyra/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.zapxlabs/veyra)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:52 UTC.
Veyra MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Veyra MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Veyra MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: cancel_payment.
Can the Veyra MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: create_payment.
What tools does the Veyra MCP server have?
- 7 tools: 1 destructive, 1 irreversible, 5 read. cancel_payment, create_payment, get_capabilities, get_budget, list_payment_sources, get_payment and list_payments.
Does the Veyra MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Veyra MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_payment.
Has the Veyra MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.