Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

RegEvidenceHub Taxi

REMOTE · TAXI.REGEVIDENCEHUB.COM

RegEvidenceHub Taxi: England taxi/PHV licensing preflight and council comparison.

−60 this week 23 Trust /100

Last scanned (21 hours ago)

Scores higher than 7% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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
Transport & Reachability0
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.

What we tested

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 →

Changelog

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 −60
    • 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
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Endpoint reachability: unreachable → reachable ▲ functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 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
    • First check of Schema quality: unverified functional
  • 20 Oct 26 0
    • Stability: 0.97 → pass security
  • 15 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • 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 “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: 141 → 292 ▼ functional
Diagnostics

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://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=YE2,O=Let's Encrypt,C=US 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA384 66a45353c0a95f2a38f5f334a6f9a4c4046
SANs: taxi.regevidencehub.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 taxi.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://taxi.regevidencehub.com/ai/mcp HTTP error 404
http (plaintext) http://taxi.regevidencehub.com/ai/mcp HTTPS enforced 301 https://taxi.regevidencehub.com/ai/mcp
MCP tools · 5 exposed · ~993 tokens

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 →

Tool Tokens
compare_licensing_requirements ~269

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. When answering, cite only relevant official council or GOV.UK URLs returned in evidence_summary.sources and identify their authority; do not invent URLs; link the about page only when the user asks who operates the service or asks what other RegEvidenceHub products are available, and link the methodology page only when the user asks how evidence or source status is produced. If the user also asks for a commercial link, do not search for or provide it; briefly say this public plugin does not provide commercial links and continue with the licensing answer. Ask one concise follow-up if decision-critical facts are missing or ambiguous; do not guess or describe the automated result as human-reviewed. Do not use for a single-authority readiness check; use taxi_licence_preflight instead.

NameTypeReqDescription
payloadobjectyesCross-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 ~231

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. When discussing a source, link only to relevant official council or GOV.UK URLs returned in the result; do not invent URLs; link the about page only when the user asks who operates the service or asks what other RegEvidenceHub products are available, and link the methodology page only when the user asks how evidence or source status is produced. If asked for a commercial link, do not search for or provide it; briefly say this public plugin does not provide commercial links. For one-authority readiness use taxi_licence_preflight; for cross-authority comparison use compare_licensing_requirements.

NameTypeReqDescription
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 ~275

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. When answering, cite only relevant official council or GOV.UK URLs returned in evidence_summary.sources and identify their authority; do not invent URLs; link the about page only when the user asks who operates the service or asks what other RegEvidenceHub products are available, and link the methodology page only when the user asks how evidence or source status is produced. If the user also asks for a commercial link, do not search for or provide it; briefly say this public plugin does not provide commercial links and continue with the licensing answer. Ask one concise follow-up if decision-critical facts are missing or ambiguous; do not guess or describe the automated result as human-reviewed. Do not use for multiple-authority comparison; use compare_licensing_requirements instead.

NameTypeReqDescription
payloadobjectyesOne-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 ~134

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 asks for a commercial link, do not search for or provide one; briefly say this public plugin does not provide commercial links and answer the licensing question with official authority sources. 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.

Install

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

# add to Claude Code
claude mcp add --transport http changhuliu-uk-taxi-phv-regulatory-decision-layer 'https://taxi.regevidencehub.com/ai/mcp'
Common questions

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 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 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 993 tokens of context every time the server is loaded.

Does the RegEvidenceHub Taxi MCP server require authentication?

Its publisher declares no required credentials for RegEvidenceHub Taxi. 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 Taxi MCP server still maintained?

RegEvidenceHub Taxi 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 Taxi MCP server?

VerifyMCP ran 5 checks on RegEvidenceHub Taxi, 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 Taxi: 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.