Remote MCP · Endpoint
Agent Evidence API MCP server
No. Agent Evidence API answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://agent-evidence-api.thx93.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.Thx93/agent-evidence-api
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 974 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 61.1% from 18 checks
- Described by its publisher as
- Cited web evidence and claim verification for AI agents. No API key: $0.003 USDC per call.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 974 ms |
| 1 day ago | Handshake completed | 336 ms |
| 2 days ago | Handshake completed | 417 ms |
| 3 days ago | Handshake completed | 504 ms |
| 4 days ago | Handshake completed | 388 ms |
| 5 days ago | Handshake completed | 774 ms |
| 6 days ago | Handshake completed | 807 ms |
| 9 days ago | Handshake completed | 344 ms |
| 11 days ago | Handshake completed | 523 ms |
| 14 days ago | Handshake completed | 446 ms |
| 16 days ago | Handshake completed | 469 ms |
| 18 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 22 days ago | Failed - the server returned an HTTP error | — |
| 24 days ago | Failed - the server returned an HTTP error | — |
| 26 days ago | Failed - the server returned an HTTP error | — |
| 27 days ago | Failed - the server returned an HTTP error | — |
| 29 days ago | Failed - the server returned an HTTP error | — |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 29.
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 Agent Evidence API and makes no claim about it beyond what these checks measured.