Remote MCP · Endpoint

RegEvidenceHub Waste MCP server

No. RegEvidenceHub Waste answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://waste.regevidencehub.com/ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.ChanghuLiu/uk-waste-rule-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
139 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
RegEvidenceHub Waste: England waste registration, DWT readiness and permit-change preflight.
Listing
From the official MCP registry (active).
Recent checks of RegEvidenceHub Waste
CheckedResultHandshake
1 hour agoHandshake completed139 ms
9 days agoHandshake completed119 ms
10 days agoHandshake completed125 ms
11 days agoHandshake completed151 ms
12 days agoHandshake completed125 ms
14 days agoHandshake completed128 ms
14 days agoHandshake completed117 ms
15 days agoHandshake completed128 ms
17 days agoHandshake completed137 ms
19 days agoHandshake completed117 ms
21 days agoHandshake completed117 ms
24 days agoHandshake completed176 ms
26 days agoHandshake completed135 ms
28 days agoHandshake completed116 ms

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

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