accueil / serveurs / Dev & Code / io.github.ChanghuLiu/uk-taxi-phv-regulatory-decision-layer
io.github.ChanghuLiu/uk-taxi-phv-regulatory-decision-layer
serveur MCP (Model Context Protocol) · UK Taxi PHV Regulatory Decision Layer 1.0.3
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.ChanghuLiu/uk-taxi-phv-regulatory-decision-layer est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.ChanghuLiu/uk-taxi-phv-regulatory-decision-layer » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 5 outils
- compare_licensing_requirements≈ 776 tokens
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.
Paramètres, retour & exemple (1)
Paramètrespayload· object · requis
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 authority-specific rule inputs are not narrowed.
Exemple d'appel{"name": "compare_licensing_requirements", "arguments": {"payload": {}}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - licensing_source_status≈ 416 tokens
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.
Paramètres, retour & exemple (1)
Paramètresauthority· ? · optionnel
Exact supported licensing-authority name returned by list_supported_authorities. Omit this parameter for a global source-health and review-readiness check.
Exemple d'appel{"name": "licensing_source_status", "arguments": {"authority": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - list_supported_authorities≈ 210 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "list_supported_authorities", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - taxi_licence_preflight≈ 686 tokens
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.
Paramètres, retour & exemple (1)
Paramètrespayload· object · requis
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 evaluated only when the evidence-backed rule bundle declares them.
Exemple d'appel{"name": "taxi_licence_preflight", "arguments": {"payload": {}}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - taxi_phv_info≈ 260 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "taxi_phv_info", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».