RegEvidenceHub Taxi

Evidence-linked England taxi and private-hire licensing preflight for AI agents.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Taxi Phv Info: Free orientation and service-metadata tool. Use this first when the user is asking what RegEvidenceHub Taxi does, what tools are available, which calls are free or x402-paid, how paymen
  • List Supported Authorities: Free coverage-discovery tool. Use when the user asks which councils/licensing authorities are supported, whether a named authority is covered, or when the authority name is
  • Licensing Source Status: Free official-source health and evidence-freshness tool. Use when the user asks whether licensing evidence is current, fresh, stale, changed, conflicted, inaccessible, under r

What data it sees

Do you need an account

No: the server works without sign-in

Evidence-linked England taxi and private-hire licensing preflight for AI agents. Check applicant, vehicle and fleet requirements, blockers and missing facts, compare councils, and verify official-source freshness.

How to connect

How to connect RegEvidenceHub Taxi to Claude

The server address to paste into Claude settings:

https://uk-taxi-phv-regulatory-decision-layer--liuchanghu2018.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect RegEvidenceHub Taxi to ChatGPT

The server address to paste into ChatGPT settings:

https://uk-taxi-phv-regulatory-decision-layer--liuchanghu2018.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect RegEvidenceHub Taxi to Cursor

The server address to paste into Cursor settings:

https://uk-taxi-phv-regulatory-decision-layer--liuchanghu2018.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (5)

Raw names from tools/list. Only developers need these.

taxi_phv_infoFree orientation and service-metadata tool. Use this first when the user is asking what RegEvidenceHub Taxi does, what tools are available, which calls are free or x402-paid, how payment works, or what safety/evidence limits apply. It returns service, pricing, capability and buyer-flow metadata; it does not make a licensing decision. If the user already names a council and wants applicant/vehicle readiness, use taxi_licence_preflight. If the user wants to compare councils, use compare_licensing_requirements. If the user is unsure which councils are covered, use list_supported_authorities.
list_supported_authoritiesFree coverage-discovery tool. Use when the user asks which councils/licensing authorities are supported, whether a named authority is covered, or when the authority name is uncertain and should be normalized before another tool call. It returns the supported authority names to reuse exactly in downstream calls. It does not assess eligibility or compare requirements. After selecting one authority, use taxi_licence_preflight; for two or more authorities, use compare_licensing_requirements.
licensing_source_statusFree official-source health and evidence-freshness tool. Use when the user asks whether licensing evidence is current, fresh, stale, changed, conflicted, inaccessible, under review, or safe to rely on for one authority or across the service. The optional authority parameter narrows the check; omit it for the global source-health view. It returns source/review readiness signals, not an applicant or vehicle licensing decision. For one-authority eligibility/readiness use taxi_licence_preflight; for cross-authority trade-offs use compare_licensing_requirements.
taxi_licence_preflightx402 paid decision tool for ONE supported council/licensing authority ($0.02 USDC/call). Use when the user wants an applicant, driver, vehicle or fleet readiness/eligibility preflight, applicable requirements or blockers, missing facts, and next actions before submission or onboarding. Call list_supported_authorities first when the authority name or coverage is uncertain, and use licensing_source_status first when evidence freshness is the question. Do not use this tool to compare multiple authorities; use compare_licensing_requirements instead.
compare_licensing_requirementsx402 paid comparison tool for TWO OR MORE supported councils/licensing authorities ($0.05 USDC/call). Use when the user wants cross-council requirements, blockers or trade-offs compared for the same applicant/fleet, or is choosing where to license. Call list_supported_authorities first if authority names or coverage are uncertain, and supply the same applicant facts consistently across authorities. Do not use this for a single-authority readiness/eligibility check; use taxi_licence_preflight instead.