Remote MCP · Endpoint

Evident Agent Service Discovery MCP server

No. Evident Agent Service Discovery answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://evidentagents.com/mcp

The last check completed an MCP handshake.

Registry name
com.evidentagents/reviews
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
668 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Discover MCP services, match task constraints, get connection setup and self-reported use feedback.
Listing
From the official MCP registry (active).
Recent checks of Evident Agent Service Discovery
CheckedResultHandshake
10 hours agoHandshake completed668 ms
2 days agoHandshake completed501 ms
4 days agoHandshake completed497 ms
6 days agoHandshake completed480 ms
8 days agoHandshake completed600 ms
10 days agoHandshake completed581 ms
12 days agoHandshake completed812 ms
13 days agoHandshake completed606 ms
14 days agoHandshake completed566 ms
17 days agoHandshake completed566 ms
18 days agoHandshake completed485 ms
20 days agoHandshake completed420 ms
21 days agoHandshake completed339 ms
23 days agoHandshake completed262 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 Evident Agent Service Discovery and makes no claim about it beyond what these checks measured.