RegEvidenceHub Taxi
REMOTE · TAXI.REGEVIDENCEHUB.COM · SCANNED SEP 25
RegEvidenceHub Taxi: England taxi/PHV licensing preflight and council comparison.
Available components
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 708 tokens (~141/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the RegEvidenceHub Taxi MCP server?
RegEvidenceHub Taxi is a hosted endpoint at https://taxi.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 · taxi.regevidencehub.com
claude mcp add --transport http changhuliu-uk-taxi-phv-regulatory-decision-layer 'https://taxi.regevidencehub.com/ai/mcp'
{
"mcpServers": {
"changhuliu-uk-taxi-phv-regulatory-decision-layer": {
"url": "https://taxi.regevidencehub.com/ai/mcp"
}
}
} {
"servers": {
"changhuliu-uk-taxi-phv-regulatory-decision-layer": {
"type": "http",
"url": "https://taxi.regevidencehub.com/ai/mcp"
}
}
} [mcp_servers.changhuliu-uk-taxi-phv-regulatory-decision-layer] url = "https://taxi.regevidencehub.com/ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"changhuliu-uk-taxi-phv-regulatory-decision-layer": {
"type": "remote",
"url": "https://taxi.regevidencehub.com/ai/mcp",
"enabled": true
}
}
} openclaw mcp add changhuliu-uk-taxi-phv-regulatory-decision-layer --url 'https://taxi.regevidencehub.com/ai/mcp' --transport streamable-http
mcp_servers:
changhuliu-uk-taxi-phv-regulatory-decision-layer:
url: "https://taxi.regevidencehub.com/ai/mcp" {
"McpServers": {
"changhuliu-uk-taxi-phv-regulatory-decision-layer": {
"Transport": "http",
"Url": "https://taxi.regevidencehub.com/ai/mcp"
}
}
} assistant mcp add changhuliu-uk-taxi-phv-regulatory-decision-layer -t streamable-http -u 'https://taxi.regevidencehub.com/ai/mcp'
{
"mcpServers": {
"changhuliu-uk-taxi-phv-regulatory-decision-layer": {
"type": "http",
"url": "https://taxi.regevidencehub.com/ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 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
- 24 Sept 26 +1
- Tool “compare_licensing_requirements” rewrote its description, which is the text the model reads security
- Tool “licensing_source_status” rewrote its description, which is the text the model reads security
- Tool “list_supported_authorities” rewrote its description, which is the text the model reads security
- Tool “taxi_licence_preflight” rewrote its description, which is the text the model reads security
- Tool “taxi_phv_info” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 67% → 100% ▲ functional
- Schema quality: good → excellent functional
- “licensing_source_status” reworded the description of “authority” cosmetic
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 0
- Server version: 1.0.1 → 1.0.3 functional
- 21 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 20 Sept 26 70
First indexed and scored.
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 25 Sept 2026 · Probed https://taxi.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=taxi.regevidencehub.com | CN=YR1,O=Let's Encrypt,C=US | 20 Sept 2026 | 19 Dec 2026 | RSA 2048 | SHA256-RSA | 5feaf165f970a2f988b4b4c3ba819b51ffa |
| SANs: taxi.regevidencehub.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of taxi.regevidencehub.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| regevidencehub.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://taxi.regevidencehub.com/ai/mcp | Verified | 200 | |
| http (plaintext) | http://taxi.regevidencehub.com/ai/mcp | HTTPS enforced | 301 | https://taxi.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 →
compare_licensing_requirements ~138
Free deterministic comparison for TWO OR MORE supported councils/licensing authorities on this public AI surface. Use when the user wants requirements, blockers or trade-offs compared for the same applicant or fleet, or is choosing where to license. Call list_supported_authorities first if authority names or coverage are uncertain. Do not use for a single-authority readiness check; use taxi_licence_preflight instead.
| Name | Type | Req | Description |
|---|---|---|---|
| payload | object | yes | Cross-authority comparison request. Call list_supported_authorities first, then supply one or more exact authority names plus the applicant facts to compare. Additional applicant facts are allowed so… |
Structured output declared, but exposes no named fields.
No examples provided.
licensing_source_status ~137
Free official-source health and freshness tool. Use when the user asks whether licensing evidence is current, stale, changed, conflicted, inaccessible, under review, or safe to rely on. Pass a supported authority name to narrow the check; omit authority for the global view. It returns source/review readiness signals, not an applicant or vehicle licensing decision. For one-authority readiness use taxi_licence_preflight; for cross-authority comparison use compare_licensing_requirements.
| Name | Type | Req | Description |
|---|---|---|---|
| authority | – | – | Exact supported licensing-authority name returned by list_supported_authorities. Omit this parameter for a global source-health and review-readiness check. |
Structured output declared, but exposes no named fields.
No examples provided.
list_supported_authorities ~84
Free coverage-discovery tool. Use when the user asks which councils or licensing authorities are supported, whether a named authority is covered, or when the authority name should be normalized before another call. It returns supported authority names and does not assess eligibility. After selecting one authority use taxi_licence_preflight; for two or more authorities use compare_licensing_requirements.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
taxi_licence_preflight ~144
Free deterministic decision preflight for ONE supported council/licensing authority on this public AI surface. Use when the user wants applicant, driver, vehicle or fleet readiness, applicable requirements or blockers, missing facts, and next actions before submission or onboarding. Call list_supported_authorities first if coverage or the exact authority name is uncertain. Do not use for multiple-authority comparison; use compare_licensing_requirements instead.
| Name | Type | Req | Description |
|---|---|---|---|
| payload | object | yes | One-authority applicant/fleet preflight facts. Start by calling list_supported_authorities and use the returned authority name exactly. Additional authority-specific facts are allowed and are evaluat… |
Structured output declared, but exposes no named fields.
No examples provided.
taxi_phv_info ~97
Free orientation tool for the public AI surface. Use this first when the user asks what RegEvidenceHub Taxi does, which tools are available, or what the evidence-safety boundary is. It returns service/tool metadata and makes no licensing decision. If the user wants one-authority readiness, use taxi_licence_preflight; for multiple authorities, use compare_licensing_requirements; for coverage discovery, use list_supported_authorities.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
What is the RegEvidenceHub Taxi MCP server?
RegEvidenceHub Taxi is an MCP server listed in the public MCP registry as io.github.ChanghuLiu/uk-taxi-phv-regulatory-decision-layer. RegEvidenceHub Taxi: England taxi/PHV licensing preflight and council comparison. This page covers its hosted endpoint (https://taxi.regevidencehub.com/ai/mcp).
Is the RegEvidenceHub Taxi MCP server safe to use?
RegEvidenceHub Taxi scores 74 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 Taxi MCP server expose?
RegEvidenceHub Taxi exposes 5 tools: taxi_phv_info, list_supported_authorities, licensing_source_status, taxi_licence_preflight, compare_licensing_requirements. Their descriptions and schemas cost roughly 600 tokens of context every time the server is loaded.
Does the RegEvidenceHub Taxi MCP server require authentication?
No. We connected to RegEvidenceHub Taxi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RegEvidenceHub Taxi MCP server still maintained?
RegEvidenceHub Taxi is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.