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.

Israel Vehicle Registry

PYPI · MCP-IL-VEHICLES

Israeli vehicle registry for AI agents: plate lookup, open recalls, model specs, new-car prices, lic

Available components

83 Trust /100

Last scanned (20 hours ago)

Scores higher than 83% of PyPI servers

Category Maps and Location

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 Security100
  • No malware found by supply-chain analysis.Pass
  • 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
  • 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to olegsher-ds-2025/mcp-il-vehicles). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 940 tokens (~67/item across 14 items; 14 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 14% of tool parameters carry a description.Partial
  • 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 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 (16)

  • Malware scan
  • 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

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 +3
    • Stability: unverified → 0.20 ▲ functional
  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 +1
    • Security disclosure: fail → pass ▲ functional
  • 15 Nov 26 64

    First indexed and scored.

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/mcp-il-vehicles@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo olegsher-ds-2025/mcp-il-vehicles
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/olegsher-ds-2025/mcp-il-vehicles/.github/workflows/publish.yml@refs/tags/v0.2.1
Rekor log index 3902556045
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:ccdcb25b57d1403626ed8ce05071f9e28a48f1074db13bcf77bb41046ccc1d49

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 22 packages
Packages resolved 22
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~893 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
disabled_parking_permit ~43

Does a licence plate hold a disabled-parking permit (תג חניה לנכה)? Returns issue date and permit type code.

NameTypeReqDescription
platestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

ev_adoption_by_year ~66

Time series of electric (BEV) and plug-in/hybrid share among active private & commercial vehicles, grouped by year first on the road — a proxy for EV adoption in new registrations over time.

NameTypeReqDescription
from_yearinteger––
to_year–––

Structured output declared, but exposes no named fields.

No examples provided.

ev_by_district ~72

Current number of electric vehicles by district (מחוז) and sub-district (נפה), with each area's share of the national EV fleet. Optional ownership filter, e.g. "פרטי", "חברה", "השכרה", "ליסינג".

NameTypeReqDescription
ownershipstring––

Structured output declared, but exposes no named fields.

No examples provided.

ev_charging_stations ~47

EV charging sites by place name, address or operator (e.g. "אילת", "Afcon").

NameTypeReqDescription
limitinteger––
querystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

find_garages ~100

Licensed garages and test stations (מוסכים ומכוני רישוי) by city (exact Hebrew name, e.g. "בת ים"), specialty keyword (e.g. "חשמל", "היברידי", "דיזל", "פחחות") and/or garage name.

NameTypeReqDescription
citystring––
limitinteger––
namestring––
specialtystring––

Structured output declared, but exposes no named fields.

No examples provided.

find_garages_near ~160

Licensed garages nearest to an address or GPS point, with distance in km.

NameTypeReqDescription
addressstring–e.g. "ההסתדרות 50, בת ים" (or give lat/lon instead).
extra_cities––neighbouring cities to include (Hebrew names as in the registry, e.g. ["חולון", "תל אביב -יפו"]).
lat–––
lon–––
max_resultsinteger––
radius_kmnumber–keep garages within this distance.
specialtystring–keyword such as "חשמל", "היברידי", "מכונאות", "פחחות", "צמיגים".

Structured output declared, but exposes no named fields.

No examples provided.

health ~17

Check that the server can reach data.gov.il.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

model_specs_for_plate ~52

Technical and safety specs (horsepower, engine, drive, airbags, ADAS, CO2, green index) for the exact model/year registered to a licence plate.

NameTypeReqDescription
platestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

new_car_prices ~74

Official importer list prices (₪) for new cars, by make/model text and optional model year. Newer models are often listed in Latin letters (e.g. "COROLLA"), older ones in Hebrew — try both.

NameTypeReqDescription
limitinteger––
querystringyes–
year–––

Structured output declared, but exposes no named fields.

No examples provided.

personal_import_check ~52

Was this vehicle brought in by personal import (יבוא אישי, new or used) rather than an official importer? Personal-import cars can have different warranty, parts and resale considerations.

NameTypeReqDescription
platestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

search_models ~57

Search makes/models (Hebrew or Latin, e.g. "טויוטה קורולה" or "COROLLA") and return specs.

NameTypeReqDescription
limitinteger––
querystringyes–
year–––

Structured output declared, but exposes no named fields.

No examples provided.

used_car_report ~60

One-call pre-purchase check for a used car: registry record, licence/test validity, open recalls, personal import, disabled-parking permit, model safety/specs and the model's new list price — with flags.

NameTypeReqDescription
platestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

vehicle_by_plate ~64

Look up an Israeli licence plate: make, model, year, fuel, colour, ownership type, last annual test, licence expiry, VIN, tyres. Searches active, inactive, two-wheeler and public-vehicle registries.

NameTypeReqDescription
platestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

vehicle_recalls ~29

Open (not yet performed) manufacturer recalls for a licence plate.

NameTypeReqDescription
platestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Israel Vehicle Registry MCP server?

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

pypi · mcp-il-vehicles

# add to Claude Code
claude mcp add olegsher-ds-2025-mcp-il-vehicles -- uvx mcp-il-vehicles
Common questions

What is the Israel Vehicle Registry MCP server?

Israel Vehicle Registry is an MCP server listed in the public MCP registry as io.github.olegsher-ds-2025/mcp-il-vehicles. Israeli vehicle registry for AI agents: plate lookup, open recalls, model specs, new-car prices, lic. This page covers its PyPI package (mcp-il-vehicles).

Is the Israel Vehicle Registry MCP server safe to use?

Israel Vehicle Registry scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 Israel Vehicle Registry MCP server expose?

Israel Vehicle Registry exposes 14 tools: vehicle_by_plate, vehicle_recalls, model_specs_for_plate, search_models, new_car_prices, and 9 more. Their descriptions and schemas cost roughly 893 tokens of context every time the server is loaded.

Is the Israel Vehicle Registry MCP server still maintained?

Israel Vehicle Registry 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 Israel Vehicle Registry MCP server under?

Israel Vehicle Registry 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 Israel Vehicle Registry MCP server?

VerifyMCP ran 16 checks on Israel Vehicle Registry, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.