Remote MCP · Endpoint

Veyra MCP server

No. Veyra answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://veyra.money/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.zapxlabs/veyra
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
126 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Give AI agents a wallet with a spending limit. Non-custodial USDC on Base, server-enforced limits.
Listing
From the official MCP registry (active).
Recent checks of Veyra
CheckedResultHandshake
1 day agoHandshake completed126 ms
3 days agoHandshake completed83 ms
5 days agoHandshake completed73 ms
7 days agoHandshake completed90 ms
9 days agoHandshake completed102 ms
10 days agoHandshake completed101 ms
11 days agoHandshake completed220 ms
13 days agoHandshake completed125 ms
15 days agoHandshake completed697 ms
17 days agoHandshake completed349 ms
18 days agoHandshake completed64 ms
19 days agoHandshake completed92 ms
20 days agoHandshake completed98 ms
22 days agoHandshake completed164 ms
22 days agoHandshake completed130 ms
23 days agoHandshake completed106 ms
24 days agoHandshake completed109 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Veyra and makes no claim about it beyond what these checks measured.