Remote MCP · Endpoint

VEYA MCP server

No. VEYA answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://mcp.veyanet.tech/mcp

The last check completed an MCP handshake.

Registry name
io.github.veyanet/veya
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
238 ms
Tools exposed
55 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Check, limit, record and prove AI agent actions with 2-of-3 validators and onchain proofs.
Listing
From the official MCP registry (active).
Recent checks of VEYA
CheckedResultHandshake
5 hours agoHandshake completed238 ms
3 days agoHandshake completed148 ms
12 days agoHandshake completed122 ms
12 days agoHandshake completed101 ms
14 days agoHandshake completed97 ms
15 days agoHandshake completed109 ms
16 days agoHandshake completed106 ms
17 days agoHandshake completed97 ms
18 days agoHandshake completed153 ms
19 days agoHandshake completed194 ms
22 days agoHandshake completed95 ms
25 days agoHandshake completed105 ms
27 days agoHandshake completed119 ms

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

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 VEYA and makes no claim about it beyond what these checks measured.