Atlas entry

www.bimbaguru.co.il

5 capabilities over MCP. First atlas observation.

Observed · passive: no tools called, no credentials sent · sha256:8700de…f44b

Surfaces

5 protocols checked

ARDNot foundNo document retrieved
A2ANot found0 skills
MCPValid2026-07-28 · 5 tools · 0 resources · 0 prompts
OpenAPINot detected0 operations
WebMCPNot detected0 declarative form tools · experimental
Exact states and meaning
  • ARD
    absent

    Exact state: not found · No document retrieved

    The supported discovery location returned no matching document.

    Not found does not prove the service exposes no such interface elsewhere.

    Not observed / not fetched

  • A2A
    absent

    Exact state: not found · 0 skills

    The supported discovery location returned no matching document.

    Not found does not prove the service exposes no such interface elsewhere.

    Not observed / not fetched

  • MCP
    observed

    Exact state: valid · Revision 2026-07-28 · 5 tools · 0 resources · 0 prompts

    A usable protocol document was retrieved and validated.

    Directly observed

  • OpenAPI
    absent

    Exact state: not detected · 0 operations

    No endpoint was established from the evidence and scope that InterfaceDelta inspected.

    Not detected does not prove that no endpoint exists.

    Not observed / not fetched

  • WebMCP
    absent

    Exact state: not detected · 0 declarative form tools · experimental

    No named declarative WebMCP form tools were observed in the origin root HTML.

    Script-registered tools and other pages are not observed, so this does not mean the site has no WebMCP tools.

    Not observed / not fetched

Capabilities

5 · inventory complete

Summary of the AI readings · beta

The service lists 5 capabilities, and 3 have AI readings.

lookup_vehicle, get_tools_directory and get_vehicle_history are read as read-only.

Rows named: lookup_vehicle · get_tools_directory · get_vehicle_history

Written by code from the AI readings on this page: it groups them and says nothing they do not.

The atlas shows each capability by its plain identifier, inputs and declared sign-in. Publisher descriptions, paths, links and source evidence are not published here.

MCP tools 5

  • get_parts_link

    inputs plate, vin

  • get_savings_link

    inputs brand (required), model

  • get_tools_directory

    AI Reads only 0.80

  • get_vehicle_history

    inputs plate (required)

    AI Reads only 0.85

  • lookup_vehicle

    inputs plate, vin

    AI Reads only 0.93

Not observed in this Passport: A2A skills, MCP resources, MCP prompts, OpenAPI operations.

Declared and observed

No tools declare hints.

A disagreement is not a finding about the service: either side can be wrong. How we compare declarations and readings.

Atlas history

1 observation

  • 5 capabilities · MCP 2026-07-28 · MCP endpoint validFirst observation
    Fingerprint and versions
    Fingerprint
    8700decf576e573a58ae9ba6a391327c90699808d711e207faf1da8eabf0f44b
    Passport schema
    0.5.0, passport-semantic-v4
    Consistency
    MCP_PROMPTS_ADVERTISEMENT_LIST: match · MCP_RESOURCES_ADVERTISEMENT_LIST: match · MCP_TOOLS_ADVERTISEMENT_LIST: match · OPENAPI_MCP_EXPLICIT_MAPPING: not applicable

Each class compares an observation with the previous atlas observation. Runs of unchanged observations are grouped. Struck values are what the previous observation recorded; inserted values are what this one recorded.

About this entry

  • il.co.bimbaguru/bimba-guru
    Listed

    Official MCP Registry · first listed 3 Nov 2026 · last listed 3 Nov 2026

Passive observations of a public interface listed in the Official MCP Registry. An observation does not verify security, ownership or compliance, and InterfaceDelta assigns no scores or rankings. Methodology · Report an inaccuracy · Ask for removal

Identity and snapshot
Target key
sha256:a0ef493a785b921023d61e9213f6dcdd532f663ab9cf86ba84fee0c790ed434e
Locator SHA-256
88a73513df28ae462ba40353c337d0cc815c0c6b89cd00a4bdb144b3ea78f11b
Snapshot generated
4 Nov 2026, 00:59 UTC

The entry is one exact observed target, not a real-world service identity, and implies no ownership. Endpoint paths are not published; the locator hash lets an operator confirm their own URL.