Technical documentation

sherlock-mcp

Sherlock is een MCP-server voor installatiewerk en locatiegebonden analyses in Nederland.

De server ontsluit tools voor adresverrijking, subsidies, meldcodes, voertuigtoegang,
emissiezones, netcongestie, laadinfrastructuur en warmtenetten, zodat clients deze checks
via één uniforme interface kunnen aanroepen.

Deze documentatiepagina toont het MCP-oppervlak van Sherlock als een referentie in OpenAPI-stijl. Tool-, resource- en promptitems zijn conceptuele weergaven van onderdelen die via het geauthenticeerde `/mcp`-transport worden aangeroepen.

Tools 12
Resources 3
Prompts 1
Routes 7

Authentication

Use the API key as a bearer token when connecting to the authenticated MCP transport.

Authorization: Bearer <YOUR_API_KEY>

Metadata

Generated 2026-11-19T12:56:34.137245+00:00
OpenAPI 3.1.0
Surface MCP + public HTTP routes

MCP tools

Callable operations

tool

address_lookup

Enrich a Dutch address using three sources: BAG (canonical address + identifiers + RD coordinates), Stella Spark Nexus WFS (normalized ranked nexus items), and EP-online (energy label export, when configured). Input: AddressLookupInput JSON with either `postal_code` (e.g. '1012AB') OR `street_name` + `city` (e.g.

tool

get_vehicle_info

Retrieve RDW vehicle information for a Dutch license plate. Input: GetVehicleInfoInput with a `license_plate`. Output: GetVehicleInfoOutput with normalized vehicle details and provenance metadata.

tool

check_vehicle_zone_access

Determine whether a vehicle is likely allowed inside a Dutch emission zone. Input: CheckVehicleZoneAccessInput with a `license_plate` plus either coordinates or an address. Output: CheckVehicleZoneAccessOutput with a yes/no/unknown decision, matched zones, and provenance metadata.

tool

find_charge_points

Find nearby EV charge points around a location. Input: FindChargePointsInput with either WGS84 coordinates or a Dutch address, plus radius and result limit. Output: FindChargePointsOutput with resolved lookup coordinates, operational charge points, and provenance metadata.

tool

lookup_emission_zone

Look up Dutch emission zones for a location. Input: LookupEmissionZoneInput with either coordinates or an address. Output: LookupEmissionZoneOutput with matched zones, the resolved lookup point, and provenance metadata.

tool

lookup_district_heating

Look up district-heating coverage for a Dutch location. Input: LookupDistrictHeatingInput with either coordinates or an address. Output: LookupDistrictHeatingOutput with nearby WarmteAtlas district-heating areas and provenance metadata.

tool

lookup_grid_congestion

Look up electricity grid-congestion status for a Dutch postcode. Input: LookupGridCongestionInput with a postcode at postcode-6 granularity. Output: LookupGridCongestionOutput with afname/opwek color codes, translated labels, regional metadata, and freshness metadata.

tool

health_check

Report MCP service health and dataset freshness metadata. Input: HealthCheckInput JSON with `include_resources` flag to request per-resource details. Output: HealthCheckOutput containing overall status and optional per-resource freshness records.

tool

search_rvo_subsidies

Semantic search across the Dutch RVO subsidies catalogue combining embeddings and keyword ranking. Input: SubsidySearchInput JSON with `query` text plus optional `statuses`, `limit`, and `debug`. Output: SubsidySearchOutput with minimal result stubs and refresh timestamp.

tool

get_rvo_subsidy

Fetch full details for a single RVO subsidy by ID. Input: SubsidyDetailInput JSON with `id` from search results. Output: SubsidyDetailOutput containing cleaned text fields (no HTML) and full_text.

tool

search_rvo_meldcodes

Search RVO installation registries (insulation, heat pumps, solar boilers, HR glass) for matching meldcodes or products. Input: MeldcodeSearchInput JSON with `installation_type`, list of `queries`, optional `limit`, and `debug`. Output: MeldcodeSearchOutput with deduplicated items plus per-query ID lists and refresh timestamp.

tool

get_meldcode_detail

Fetch full details for a single meldcode record by ID. Input: MeldcodeDetailInput JSON with `installation_type` and `id` from search results. Output: MeldcodeDetailOutput containing cleaned text fields (no HTML) and full_text.

HTTP surface

Public and transport routes

These are the browser-facing and transport endpoints that sit next to the MCP component catalog.

Health /health
GET

Operational health route for uptime checks, Cloud Run probes, and quick environment inspection.

Technical docs /docs
GET

Sherlock's branded technical documentation page. It combines route guidance and an OpenAPI-style view of the MCP surface.

MCP transport /mcp
POST

Authenticated MCP HTTP transport endpoint. Clients use this JSON-RPC surface to invoke tools, read resources, and retrieve prompts.

Public demo /
GET

Public Dutch-language Sherlock demo landing page with the homepage hero, gated live chat, and streamed tool trace.

Demo alias /demo
GET

Alias route that serves the same Sherlock one-page as `/`.

Demo chat unlock /api/chat/unlock
POST

Unlocks the public Sherlock demo chat by setting a signed demo cookie.

Demo chat stream /api/chat/stream
POST

Streams a single Dutch-language demo chat turn as NDJSON, including tool trace events and assistant deltas.

OpenAPI view

Conceptual MCP reference

Swagger UI is used here as a searchable component reference. The listed tool, resource, and prompt operations document the Sherlock MCP surface rather than standalone REST endpoints.