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.

pitwall-mcp

PYPI · PITWALL-MCP

Solo lectura sobre BMW CarData: mantenimiento, neumaticos y bateria de 12V. No afiliado a BMW AG.

Available components

−15 this week 67 Trust /100

Last scanned (12 hours ago)

Scores higher than 60% of PyPI servers

Category IoT and Hardware

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 2 of 40 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1030 tokens (~85/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 21 Nov 26 −16
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → 0.97 functional
  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 13 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
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 · Analysed pypi/pitwall-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 40 packages
Packages resolved 40
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~807 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
diagnose_software_update ~76

Informe acotado sobre por que no llega una Remote Software Upgrade. De las tres condiciones que documenta BMW, CarData solo permite observar una (la bateria de 12V); sobre las otras dos declara 'no observable por CarData'. Trabaja sobre la SERIE del historico local, no sobre una foto puntual.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_api_quota ~54

Cuantas peticiones REST se han gastado hoy, cuantas quedan, cuando se estima que se reinicia la ventana, y el estado de la cache local. Todo se deriva de SQLite: NO gasta cuota.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_fault_memory ~82

Codigos de la memoria de averias del coche, agrupados por centralita, y que codigos han aparecido o desaparecido desde la lectura anterior. Cada codigo solo trae centralita y codigo: sin estado, fecha ni descripcion, y NO se traduce porque el catalogo no dice que significa. Comparte la cache del contenedor (12 h).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_fuel_status ~96

Deposito en % y litros (+/-6 L segun el catalogo), autonomia, repostajes detectados en el historico local y consumo real desde el ultimo, con su margen de error. Incluye el consumo homologado OBFCM, marcado como lo que es: una cifra de por vida congelada desde la ultima visita al taller, no el consumo actual. Comparte la cache del contenedor (12 h).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_maintenance_summary ~53

Bloque de texto listo para pegar en un prompt: kilometraje, partidas CBS con km y fecha restantes, presiones de las cuatro ruedas en bar contra su objetivo, y la fecha del dato mas antiguo utilizado.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_telematic_data ~53

Lee el contenedor de mantenimiento completo: kilometraje, CBS, bateria de 12V, presiones y estado de sueno. Fuente: GET /telematicData. Cache de 12 h.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_tyre_diagnosis ~80

Desgaste, defectos, dimensiones, fechas de montaje y fabricacion, temporada, runflat y dibujo. NO devuelve presiones: esas vienen del contenedor telematico. Verificado en este vehiculo: BMW responde con la estructura vacia, y los ceros que trae NO son medidas. Cache de 7 dias.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_vehicle_basic_data ~48

Modelo, serie, motor, fecha de construccion, lista de equipamiento y puStep. Fuente: GET /customers/vehicles/{vin}/basicData. Cache de 30 dias.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_vehicle_status ~51

Kilometraje y avisos de mantenimiento (CBS). El desglose CBS por partida esta pendiente de verificar contra una respuesta real: la estructura de El desglose por partida esta verificado contra una respuesta real.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

list_vehicles ~46

VINs mapeados a la cuenta, con mappedSince y mappingType (PRIMARY o SECONDARY). Fuente: GET /customers/vehicles/mappings. Cache de 30 dias.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

report_product_update_step ~77

Expone puStep, el paso de actualizacion de PRODUCTO. NO es la version de software del vehiculo: ese descriptor no existe en el catalogo de BMW. Verificado en este vehiculo: /basicData NO devuelve puStep, asi que la herramienta explica esa ausencia en vez de sustituirla por otra cosa.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

search_descriptors ~91

Busca en el catalogo telematico local de BMW CarData (294 descriptores). Acepta consultas en espanol o en ingles. NO gasta cuota de la API: el catalogo es un fichero local. Es la unica fuente de verdad sobre que descriptores existen.

NameTypeReqDescription
include_electricboolean––
limitinteger––
querystringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the pitwall-mcp server?

pitwall-mcp runs locally as a PyPI package, launched with uvx pitwall-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · pitwall-mcp

# add to Claude Code
claude mcp add sergioprats-pitwall-mcp -- uvx pitwall-mcp
Common questions

What is the pitwall-mcp server?

pitwall-mcp is listed in the public MCP registry as io.github.sergioprats/pitwall-mcp. Solo lectura sobre BMW CarData: mantenimiento, neumaticos y bateria de 12V. No afiliado a BMW AG. This page covers its PyPI package (pitwall-mcp).

Is the pitwall-mcp server safe to use?

pitwall-mcp scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 pitwall-mcp server expose?

pitwall-mcp exposes 12 tools: search_descriptors, get_api_quota, list_vehicles, get_vehicle_basic_data, report_product_update_step, and 7 more. Their descriptions and schemas cost roughly 807 tokens of context every time the server is loaded.

Is the pitwall-mcp server still maintained?

pitwall-mcp 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 licence is the pitwall-mcp server under?

pitwall-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the pitwall-mcp server?

VerifyMCP ran 15 checks on pitwall-mcp, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about pitwall-mcp: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.