RegEvidenceHub Waste
REMOTE · WASTE.REGEVIDENCEHUB.COM
RegEvidenceHub Waste: England waste registration, DWT readiness and permit-change preflight.
Available components
Last scanned (13 hours ago)
Scores higher than 7% of remote servers
Reachable. Last reached 21 Nov 2026.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Nov 26 −59
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 8 Nov 26 0
- Stability: 0.97 → pass security
- 7 Nov 26 +1
- Endpoint reachability: unreachable → reachable ▲ functional
- 6 Nov 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://waste.regevidencehub.com/ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=waste.regevidencehub.com | CN=YE1,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5444435f17a134e64c0c1768bd8a527749f |
| SANs: waste.regevidencehub.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of waste.regevidencehub.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| regevidencehub.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://waste.regevidencehub.com/ai/mcp | HTTP error | 404 | |
| http (plaintext) | http://waste.regevidencehub.com/ai/mcp | HTTPS enforced | 301 | https://waste.regevidencehub.com/ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_waste_rules ~49
LEGACY COMPATIBILITY alias for waste_rule_catalog. Use waste_rule_catalog for new integrations. Returns the same payment-free supported-role/activity catalogue so older installed connectors do not fail with Unknown tool.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
waste_carrier_broker_dealer_preflight ~128
FREE CARRIER/BROKER/DEALER REGISTRATION LIFECYCLE tool for England. Select when the unresolved question is a new registration, renewal, detail/activity change, legal-type change, or lower-to-upper change for a carrier, broker or dealer. Supply role and lifecycle action, plus own-waste/tier facts when relevant. Returns a bounded route, fee route, findings and official evidence. It is read-only and never submits or renews a registration. Do NOT use for site permit changes or DWT reporting readiness.
| Name | Type | Req | Description |
|---|---|---|---|
| scenario | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
waste_digital_tracking_readiness ~124
FREE DIGITAL WASTE TRACKING RECEIVING-SITE READINESS tool for England phase 1. Select only when the question is whether a waste receiving site is in the permitted/licensed receiving-site scope and ready for receipt reporting around the 1 October 2026 mandatory start. Supply receiving authorisation, whether controlled waste is received, reporting-method readiness, and optionally an as-of date. Returns phase-1 scope/readiness, findings and evidence; it never submits DWT records. Do NOT use for carrier registration or permit-change comparison.
| Name | Type | Req | Description |
|---|---|---|---|
| scenario | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
waste_permit_change_preflight ~119
FREE PERMIT-CHANGE IMPACT PREFLIGHT for an EXISTING England waste operation when both current and proposed operating facts are available. Compare modelled fields such as location, activities, waste types, quantity, storage, treatment or operating hours. Returns changed fields, findings, official evidence and review actions; it is read-only and does not vary a permit or decide that a variation/new permit is legally required. Do NOT use for a brand-new operation route, carrier registration, or DWT receipt-reporting readiness.
| Name | Type | Req | Description |
|---|---|---|---|
| scenario | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
waste_rule_catalog ~65
FREE RULE CATALOG tool. Use before a case-specific preflight when an agent needs the exact supported role IDs, activity IDs, and bounded route names accepted by this service. Do NOT use it to decide a user's case; use waste_rule_preflight after collecting the relevant facts.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
waste_rule_info ~46
LEGACY COMPATIBILITY alias for waste_service_info. Use waste_service_info for new integrations. Returns the same payment-free service metadata so older installed connectors do not fail with Unknown tool.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
waste_rule_preflight ~119
FREE GENERAL ENTRY TOOL for a CURRENT England waste operation when the regulatory route is still uncertain. Provide nation, role, one or more modelled activities, and any known site/waste/authorisation facts. Returns a deterministic route, missing facts, findings, evidence and next actions; it is read-only and does not submit anything. Do NOT use when the question is specifically carrier/broker/dealer registration, DWT receiving-site readiness, or a current-vs-proposed permit change; use the corresponding narrow tool instead.
| Name | Type | Req | Description |
|---|---|---|---|
| scenario | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
waste_service_info ~86
FREE SERVICE/DISCOVERY metadata tool. Use for questions about this connector's England scope, available tools, payment-free public-AI surface, fail-closed behavior, and safety boundaries. Do NOT use for evidence freshness; use waste_source_status. Do NOT use for a case-specific regulatory route; use waste_rule_preflight or the narrower registration, DWT, or permit-change tool.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
waste_source_status ~77
FREE EVIDENCE-HEALTH tool. Use only to check whether the reviewed official GOV.UK / Environment Agency evidence is fresh, unchanged, available and decision-usable. It returns source-health status and never makes a waste-route or permit conclusion. Do NOT use for operational routing; use waste_rule_preflight or a narrower workflow tool.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the RegEvidenceHub Waste MCP server?
RegEvidenceHub Waste is a hosted endpoint at https://waste.regevidencehub.com/ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · waste.regevidencehub.com
claude mcp add --transport http changhuliu-uk-waste-rule-mcp 'https://waste.regevidencehub.com/ai/mcp'
What is the RegEvidenceHub Waste MCP server?
RegEvidenceHub Waste is an MCP server listed in the public MCP registry as io.github.ChanghuLiu/uk-waste-rule-mcp. RegEvidenceHub Waste: England waste registration, DWT readiness and permit-change preflight. This page covers its hosted endpoint (https://waste.regevidencehub.com/ai/mcp).
Is the RegEvidenceHub Waste MCP server safe to use?
RegEvidenceHub Waste scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RegEvidenceHub Waste MCP server expose?
RegEvidenceHub Waste exposes 9 tools: waste_service_info, waste_rule_catalog, waste_rule_info, list_waste_rules, waste_source_status, and 4 more. Their descriptions and schemas cost roughly 813 tokens of context every time the server is loaded.
Does the RegEvidenceHub Waste MCP server require authentication?
Its publisher declares no required credentials for RegEvidenceHub Waste. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the RegEvidenceHub Waste MCP server still maintained?
RegEvidenceHub Waste is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the RegEvidenceHub Waste MCP server?
VerifyMCP ran 5 checks on RegEvidenceHub Waste, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about RegEvidenceHub Waste: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.