Remote MCP · Endpoint

vek-data MCP server

No. vek-data answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://vek-data.agent-vek.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.Ratiborro/vek-data
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
802 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Base/Ethereum blocks and balances, crypto news RSS, CoinGecko prices.
Repository
https://github.com/Ratiborro/vek-data
Listing
From the official MCP registry (active).
Recent checks of vek-data
CheckedResultHandshake
34 minutes agoHandshake completed802 ms
8 days agoHandshake completed82 ms
9 days agoHandshake completed66 ms
11 days agoHandshake completed58 ms
12 days agoHandshake completed94 ms
12 days agoHandshake completed66 ms
14 days agoHandshake completed77 ms
14 days agoHandshake completed62 ms
16 days agoHandshake completed676 ms
19 days agoHandshake completed46 ms
21 days agoHandshake completed52 ms
24 days agoHandshake completed68 ms
26 days agoHandshake completed52 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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