Remote MCP · Endpoint

Euvra MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://euvra.dev/mcp

The last check failed: the server returned an HTTP error.

Registry name
dev.euvra/euvra
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
3 tools
Uptime, last 30 days
85.7% from 14 checks
Described by its publisher as
Discover, compare, route, and execute machine-accessible capabilities for AI agents.
Listing
From the official MCP registry (active).
Recent checks of Euvra
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoHandshake completed3.50 s
4 days agoHandshake completed482 ms
6 days agoHandshake completed256 ms
8 days agoHandshake completed301 ms
10 days agoFailed - the server returned an HTTP error—
12 days agoHandshake completed331 ms
14 days agoHandshake completed877 ms
16 days agoHandshake completed91 ms
17 days agoHandshake completed232 ms
18 days agoHandshake completed1.44 s
21 days agoHandshake completed305 ms
22 days agoHandshake completed187 ms
24 days agoHandshake completed1.05 s

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

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