Remote MCP · Endpoint

Web Evidence MCP server

No. Web Evidence answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.aisoup.net/web-evidence/mcp

The last check completed an MCP handshake.

Registry name
io.github.impanyu/web-evidence
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
101 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Paid claim verification with cited web evidence, source provenance, snapshots, and hashes.
Listing
From the official MCP registry (active).
Recent checks of Web Evidence
CheckedResultHandshake
1 hour agoHandshake completed101 ms
4 days agoHandshake completed98 ms
7 days agoHandshake completed212 ms
16 days agoHandshake completed112 ms
16 days agoHandshake completed115 ms
18 days agoHandshake completed94 ms
19 days agoHandshake completed91 ms
20 days agoHandshake completed102 ms
21 days agoHandshake completed103 ms
22 days agoHandshake completed95 ms
23 days agoHandshake completed95 ms
26 days agoHandshake completed96 ms
29 days agoHandshake completed99 ms

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

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