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.

DeepPVMapper

REMOTE · ZELHLIYLRLKTNASIRCWP.SUPABASE.CO

Open registry of 1.14M+ rooftop-solar detections across France, queryable by natural language.

0 this week 76 Trust /100

Last scanned (16 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 5627 tokens (~331/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • 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 hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 17 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Oct 26 +1
    • Stability: 0.97 → pass security
  • 19 Oct 26 0
    • Tool “aggregate_detection_capacity” rewrote its description, which is the text the model reads security
    • Tool “get_department_capacity_stats” rewrote its description, which is the text the model reads security
    • Tool “get_department_yearly_stats” rewrote its description, which is the text the model reads security
    • Tool “get_detections_in_bbox” rewrote its description, which is the text the model reads security
    • Tool “search_detections” rewrote its description, which is the text the model reads security
    • Schema quality: 244 → 331 ▼ functional
    • Tool coverage: 75% → 92% ▲ functional
    • Server version: 0.1.0 → 0.2.0 functional
    • New tool “count_detections” functional
    • New tool “get_department_profile” functional
    • New tool “get_detection_details” functional
    • New tool “get_field_coverage” functional
    • New tool “get_field_distribution” functional
    • New tool “get_field_reference” functional
    • New tool “get_source_breakdown” functional
    • New tool “get_source_reference” functional
    • New tool “get_started” functional
    • “aggregate_detection_capacity” added an optional parameter “false_positive_status” cosmetic
    • “aggregate_detection_capacity” added an optional parameter “has_frpv_proba” cosmetic
    • “aggregate_detection_capacity” added an optional parameter “has_rnb_id” cosmetic
    • “aggregate_detection_capacity” added an optional parameter “max_azimuth” cosmetic
    • “aggregate_detection_capacity” added an optional parameter “max_first_seen” cosmetic
    • “aggregate_detection_capacity” added an optional parameter “max_last_seen” cosmetic
    • “aggregate_detection_capacity” added an optional parameter “max_surface” cosmetic
    • “aggregate_detection_capacity” added an optional parameter “max_tilt” cosmetic
    • “aggregate_detection_capacity” added an optional parameter “max_vintages” cosmetic
    • “aggregate_detection_capacity” added an optional parameter “min_azimuth” cosmetic
    • “aggregate_detection_capacity” added an optional parameter “min_first_seen” cosmetic
    • “aggregate_detection_capacity” added an optional parameter “min_frpv_proba” cosmetic
    • “aggregate_detection_capacity” added an optional parameter “min_last_seen” cosmetic
    • “aggregate_detection_capacity” added an optional parameter “min_surface” cosmetic
    • “aggregate_detection_capacity” added an optional parameter “min_tilt” cosmetic
    • “aggregate_detection_capacity” added an optional parameter “sources_include” cosmetic
    • “search_detections” added an optional parameter “false_positive_status” cosmetic
    • “search_detections” added an optional parameter “has_frpv_proba” cosmetic
    • “search_detections” added an optional parameter “has_rnb_id” cosmetic
    • “search_detections” added an optional parameter “max_azimuth” cosmetic
    • “search_detections” added an optional parameter “max_first_seen” cosmetic
    • “search_detections” added an optional parameter “max_last_seen” cosmetic
    • “search_detections” added an optional parameter “max_surface” cosmetic
    • “search_detections” added an optional parameter “max_tilt” cosmetic
    • “search_detections” added an optional parameter “max_vintages” cosmetic
    • “search_detections” added an optional parameter “min_azimuth” cosmetic
    • “search_detections” added an optional parameter “min_first_seen” cosmetic
    • “search_detections” added an optional parameter “min_frpv_proba” cosmetic
    • “search_detections” added an optional parameter “min_last_seen” cosmetic
    • “search_detections” added an optional parameter “min_surface” cosmetic
    • “search_detections” added an optional parameter “min_tilt” cosmetic
    • “search_detections” added an optional parameter “sources_include” cosmetic
    • “aggregate_detection_capacity” reworded the description of “cross_validated” cosmetic
    • “aggregate_detection_capacity” reworded the description of “quality_filter” cosmetic
    • “search_detections” reworded the description of “cross_validated” cosmetic
    • “search_detections” reworded the description of “quality_filter” cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 · Probed https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=supabase.co CN=WE1,O=Google Trust Services,C=US 24 Oct 2026 22 Jan 2027 ECDSA 256 ECDSA-SHA256 d2b50611cd88e9c50e4e2231f4d3f059
SANs: supabase.co, *.supabase.co
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of zelhliylrlktnasircwp.supabase.co. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
co. DS published 7786 8 Verified
supabase.co. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp Verified 200
http (plaintext) http://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp HTTPS enforced 301 https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp
MCP tools · 17 exposed · ~5,627 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
aggregate_detection_capacity ~1,052

Compute the total estimated installed capacity (kWp) and count of detections matching a set of filters — département, commune, capacity range, and cross-validation across sources (cross_validated) or imagery vintages (min_vintages) — plus a quality_summary for the summed sample. Unlike get_department_capacity_stats, which is a fixed pre-computed département-wide aggregate with no other filters, this tool sums a live filtered subset, up to max_rows detections. Example: "installed capacity in Gironde confirmed by at least two sources" -> dpt="33", cross_validated=true. Data quality note: this is a detection dataset, not an exhaustive inventory (estimated recall ~0.6). A missing detection does not mean no PV installation exists there. kwp, surface, tilt and azimuth are model estimates, not surveyed values. In this server, quality_filter=true keeps only detections identified by 2 or more sources (see source_encoding in get_data_quality_reference). Call get_data_quality_reference for the full picture before assessing fitness for a specific use case.

NameTypeReqDescription
cross_validatedboolean–Alias of quality_filter, kept for backward compatibility.
dptstring–French département code, e.g. "33".
false_positive_statusstring–flagged = false_positive is true; not_flagged = false_positive is false; unrecorded = false_positive is null (no status recorded — NOT a confirmed true positive).
has_frpv_probaboolean–true = only detections that have an FRPV comparison (frpv_proba not null); false = only those without one. A null frpv_proba means "no comparison available", not probability 0.
has_rnb_idboolean–true = only detections matched to an RNB building identifier (rnb_id not null); false = only detections without one.
inseestring–INSEE commune code.
max_azimuthnumber–Maximum estimated azimuth, degrees clockwise from true north (180 = south).
max_first_seeninteger–Upper bound on first_seen imagery year.
max_kwpnumber–Maximum estimated installed capacity, in kWp.
max_last_seeninteger–Upper bound on last_seen imagery year.
max_rowsintegeryesCap on the number of matching detection rows fetched to compute the capacity sum. If the true match count exceeds this, total_kwp is a partial lower bound and `truncated` is true — increase max_rows…
max_surfacenumber–Maximum estimated PV array area, in m².
max_tiltnumber–Maximum estimated tilt from horizontal, in degrees.
max_vintagesinteger–Maximum number of imagery vintages (e.g. 1 = seen in a single year only).
min_azimuthnumber–Minimum estimated azimuth, degrees clockwise from true north (180 = south).
min_first_seeninteger–Earliest imagery year of first detection, lower bound (e.g. 2018). Not an installation date.
min_frpv_probanumber–Minimum frpv_proba. The data contract recommends 0.1 as a precision/recall trade-off. Note: detections with a null frpv_proba (no FRPV comparison available) are excluded when this is set; null does n…
min_kwpnumber–Minimum estimated installed capacity, in kWp.
min_last_seeninteger–Lower bound on last_seen imagery year.
min_surfacenumber–Minimum estimated PV array area, in m².
min_tiltnumber–Minimum estimated tilt from horizontal, in degrees.
min_vintagesinteger–Minimum number of distinct imagery vintages (years) the installation was independently detected in. Use 2+ as a persistence/confidence signal, since a one-off detection in a single vintage is more li…
quality_filterbooleanyesIf true, only include detections identified by 2 OR MORE sources(the `sources` field lists at least two codes, e.g. "0,1" = DeepPVMapper pipeline + FRPV reference, "0,2" = pipeline + OpenStreetMap).…
sources_includearray–Only include detections present in ALL of these sources. Accepts names or codes, case-insensitive: dpvm/deeppvmapper/kasmi (0), frpv/thebault (1), osm/openstreetmap (2), manual/annotation (3), recall…

No output schema declared.

No examples provided.

count_detections ~1,011

Count detections matching a set of filters, exactly, without downloading rows (fast, no row cap). Use this for "how many ..." questions, e.g. "how many installations have an RNB id?" -> has_rnb_id=true; "how many are identified by 2+ sources?" -> quality_filter=true; "how many come from OpenStreetMap?" -> sources_include=[2]. Returns the matching count, the unfiltered registry total and the percentage. Counts are DETECTED systems, not an inventory. Data quality note: this is a detection dataset, not an exhaustive inventory (estimated recall ~0.6). A missing detection does not mean no PV installation exists there. kwp, surface, tilt and azimuth are model estimates, not surveyed values. In this server, quality_filter=true keeps only detections identified by 2 or more sources (see source_encoding in get_data_quality_reference). Call get_data_quality_reference for the full picture before assessing fitness for a specific use case.

NameTypeReqDescription
breakdown_rnb_idbooleanyesIf true, also return how many of the matching detections do / do not have an rnb_id (ignores has_rnb_id for this breakdown).
cross_validatedboolean–Alias of quality_filter, kept for backward compatibility.
dptstring–French département code, e.g. "33".
false_positive_statusstring–flagged = false_positive is true; not_flagged = false_positive is false; unrecorded = false_positive is null (no status recorded — NOT a confirmed true positive).
has_frpv_probaboolean–true = only detections that have an FRPV comparison (frpv_proba not null); false = only those without one. A null frpv_proba means "no comparison available", not probability 0.
has_rnb_idboolean–true = only detections matched to an RNB building identifier (rnb_id not null); false = only detections without one.
inseestring–INSEE commune code.
max_azimuthnumber–Maximum estimated azimuth, degrees clockwise from true north (180 = south).
max_first_seeninteger–Upper bound on first_seen imagery year.
max_kwpnumber–Maximum estimated installed capacity, in kWp.
max_last_seeninteger–Upper bound on last_seen imagery year.
max_surfacenumber–Maximum estimated PV array area, in m².
max_tiltnumber–Maximum estimated tilt from horizontal, in degrees.
max_vintagesinteger–Maximum number of imagery vintages (e.g. 1 = seen in a single year only).
min_azimuthnumber–Minimum estimated azimuth, degrees clockwise from true north (180 = south).
min_first_seeninteger–Earliest imagery year of first detection, lower bound (e.g. 2018). Not an installation date.
min_frpv_probanumber–Minimum frpv_proba. The data contract recommends 0.1 as a precision/recall trade-off. Note: detections with a null frpv_proba (no FRPV comparison available) are excluded when this is set; null does n…
min_kwpnumber–Minimum estimated installed capacity, in kWp.
min_last_seeninteger–Lower bound on last_seen imagery year.
min_surfacenumber–Minimum estimated PV array area, in m².
min_tiltnumber–Minimum estimated tilt from horizontal, in degrees.
min_vintagesinteger–Minimum number of distinct imagery vintages (years) the installation was independently detected in. Use 2+ as a persistence/confidence signal, since a one-off detection in a single vintage is more li…
quality_filterbooleanyesIf true, only include detections identified by 2 OR MORE sources(the `sources` field lists at least two codes, e.g. "0,1" = DeepPVMapper pipeline + FRPV reference, "0,2" = pipeline + OpenStreetMap).…
sources_includearray–Only include detections present in ALL of these sources. Accepts names or codes, case-insensitive: dpvm/deeppvmapper/kasmi (0), frpv/thebault (1), osm/openstreetmap (2), manual/annotation (3), recall…

No output schema declared.

No examples provided.

get_community_activity ~108

Get a snapshot of ongoing community contribution activity on the map: how many corrections are currently pending moderation, their breakdown by action type (add / modify / delete), and the most recent submissions (timestamp, action, target). Submitted free-text comments are intentionally excluded from this tool. This reflects unmoderated, unverified user activity, not the registry itself — do not present it as confirmed detection data.

NameTypeReqDescription
recent_limitintegeryesHow many of the most recent pending contributions to list.

No output schema declared.

No examples provided.

get_community_activity_in_area ~323

Find pending, unmoderated community contributions relevant to a specific area, to answer "has anyone flagged anything here that is not in the registry yet?" Two independent filters: dpt finds pending edits/deletions (action=modify/delete) targeting existing detections in that département; a full bounding box (min_lon/min_lat/max_lon/max_lat) finds pending new additions (action=add) whose proposed footprint centroid falls inside it. Combine with get_department_capacity_stats / search_detections / get_detections_in_bbox for the confirmed registry picture, and present this separately and clearly as unverified, pending community input — not confirmed detection data. Free-text comments are never included.

NameTypeReqDescription
dptstring–Filter pending edits/deletions of EXISTING detections (action=modify or delete) to this département. Does not apply to proposed new additions (action=add), which have no département recorded on the p…
max_latnumber––
max_lonnumber––
min_latnumber––
min_lonnumber––
recent_limitintegeryesMaximum number of matching items to return per category.
scan_limitintegeryesHow many recent proposed additions (action=add) to scan for a bbox match. Only relevant when all four bbox parameters are given — there is no server-side spatial index on pending items, so matching i…

No output schema declared.

No examples provided.

get_data_quality_reference ~124

Return the DeepPVMapper/OpenPVMapper registry's documented data-quality characteristics: estimated detection recall, which fields are model-derived estimates vs. structural/observed fields, the source-encoding table, the recommended confidence threshold, confidence signals, and licensing/liability terms. Call this before advising how much to trust a result for a specific use case (e.g. exploratory research vs. a commercial or regulatory decision) — pair it with the quality_summary attached to search_detections / aggregate_detection_capacity results, which reflects the specific query rather than the registry as a whole.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_department_capacity_stats ~231

Get installed rooftop-PV capacity (total kWp) and system counts for one or all French départements, from the DeepPVMapper/OpenPVMapper registry. This is a fixed, pre-computed department-wide aggregate with no other filters — use aggregate_detection_capacity instead if you need a filtered subset (e.g. only cross-validated detections). Data quality note: this is a detection dataset, not an exhaustive inventory (estimated recall ~0.6). A missing detection does not mean no PV installation exists there. kwp, surface, tilt and azimuth are model estimates, not surveyed values. In this server, quality_filter=true keeps only detections identified by 2 or more sources (see source_encoding in get_data_quality_reference). Call get_data_quality_reference for the full picture before assessing fitness for a specific use case.

NameTypeReqDescription
dptstring–French département code, e.g. "33" for Gironde. Omit for all départements.
top_ninteger–If set and dpt is omitted, return only the top N départements by installed capacity.

No output schema declared.

No examples provided.

get_department_profile ~180

One-call profile of a département: installed capacity and national rank, yearly trend (by first-seen imagery year), source mix, share identified by 2+ sources, and share matched to an RNB building id. Cross-references the pre-computed department statistics with live counts. Data quality note: this is a detection dataset, not an exhaustive inventory (estimated recall ~0.6). A missing detection does not mean no PV installation exists there. kwp, surface, tilt and azimuth are model estimates, not surveyed values. In this server, quality_filter=true keeps only detections identified by 2 or more sources (see source_encoding in get_data_quality_reference). Call get_data_quality_reference for the full picture before assessing fitness for a specific use case.

NameTypeReqDescription
dptstringyesFrench département code, e.g. "33".

No output schema declared.

No examples provided.

get_department_yearly_stats ~159

Get yearly system counts and capacity by département, based on first-seen imagery year. Useful for tracking apparent PV deployment growth over time. Data quality note: this is a detection dataset, not an exhaustive inventory (estimated recall ~0.6). A missing detection does not mean no PV installation exists there. kwp, surface, tilt and azimuth are model estimates, not surveyed values. In this server, quality_filter=true keeps only detections identified by 2 or more sources (see source_encoding in get_data_quality_reference). Call get_data_quality_reference for the full picture before assessing fitness for a specific use case.

NameTypeReqDescription
dptstring–French département code, e.g. "33". Omit for all départements.

No output schema declared.

No examples provided.

get_detection_details ~180

Get the full record of one detection by id: technical characteristics (surface, kwp, tilt, azimuth — model estimates), imagery years, sources decoded into plain labels, frpv_proba, false-positive flag, rnb_id and location codes, plus simple confidence signals. Data quality note: this is a detection dataset, not an exhaustive inventory (estimated recall ~0.6). A missing detection does not mean no PV installation exists there. kwp, surface, tilt and azimuth are model estimates, not surveyed values. In this server, quality_filter=true keeps only detections identified by 2 or more sources (see source_encoding in get_data_quality_reference). Call get_data_quality_reference for the full picture before assessing fitness for a specific use case.

NameTypeReqDescription
idintegeryesRegistry identifier of the detection (the `id` field).

No output schema declared.

No examples provided.

get_detections_in_bbox ~215

Get rooftop-PV detections within a geographic bounding box (WGS84 lon/lat), including footprint geometry. Intended for map-style spatial queries over a small area. Data quality note: this is a detection dataset, not an exhaustive inventory (estimated recall ~0.6). A missing detection does not mean no PV installation exists there. kwp, surface, tilt and azimuth are model estimates, not surveyed values. In this server, quality_filter=true keeps only detections identified by 2 or more sources (see source_encoding in get_data_quality_reference). Call get_data_quality_reference for the full picture before assessing fitness for a specific use case.

NameTypeReqDescription
max_countintegeryesMaximum number of detections to return (max 500 here; the underlying API defaults to 2000, capped lower to keep responses manageable for an LLM).
max_latnumberyes–
max_lonnumberyes–
min_latnumberyes–
min_lonnumberyes–

No output schema declared.

No examples provided.

get_field_coverage ~226

Completeness report: for each optional field of the registry (rnb_id, frpv_proba, false_positive, false_positive_source), how many detections have it filled in and what percentage. Answers "how many installations have an RNB id / an FRPV comparison / a false-positive flag?" in one call, for France or one département. For a single filtered count use count_detections instead. Null means "not available/recorded", never "0" or "confirmed ok". Data quality note: this is a detection dataset, not an exhaustive inventory (estimated recall ~0.6). A missing detection does not mean no PV installation exists there. kwp, surface, tilt and azimuth are model estimates, not surveyed values. In this server, quality_filter=true keeps only detections identified by 2 or more sources (see source_encoding in get_data_quality_reference). Call get_data_quality_reference for the full picture before assessing fitness for a specific use case.

NameTypeReqDescription
dptstring–French département code. Omit for all of France.

No output schema declared.

No examples provided.

get_field_distribution ~326

Histogram of a numeric field (kwp, surface, tilt, azimuth, n_vintages, first_seen, last_seen) with exact counts per bin, for France or one département. Answers "how are installations distributed by size / tilt / orientation / year?". kwp, surface, tilt and azimuth are model estimates. first_seen/last_seen are imagery years, not installation dates. Data quality note: this is a detection dataset, not an exhaustive inventory (estimated recall ~0.6). A missing detection does not mean no PV installation exists there. kwp, surface, tilt and azimuth are model estimates, not surveyed values. In this server, quality_filter=true keeps only detections identified by 2 or more sources (see source_encoding in get_data_quality_reference). Call get_data_quality_reference for the full picture before assessing fitness for a specific use case.

NameTypeReqDescription
bin_edgesarray–Custom ascending bin edges; each bin is [edge_i, edge_i+1) and the last is closed. Ignored for first_seen / last_seen, which are counted per year (use min_year / max_year).
dptstring–French département code. Omit for all of France.
fieldstringyesNumeric field to describe.
max_yearinteger–For first_seen / last_seen: last year to count.
min_yearinteger–For first_seen / last_seen: first year to count.
quality_filterbooleanyesIf true, restrict to detections identified by 2+ sources.

No output schema declared.

No examples provided.

get_field_reference ~63

Field-by-field documentation of a detection record: type, unit, nullability, whether it is observed or a model estimate, how to read it, and which tool filters or reports it. Call this when the user asks what a field means or how reliable it is.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_source_breakdown ~225

Break down detections by source code (0=DPVM pipeline, 1=FRPV reference, 2=OSM, 3=manual correction, 4=recall sample), for one département or all of France, with human-readable labels. A detection can carry several sources, so per-source counts overlap and do not add up to the total. Also returns how many detections are identified by 2+ sources (the meaning of quality_filter). Data quality note: this is a detection dataset, not an exhaustive inventory (estimated recall ~0.6). A missing detection does not mean no PV installation exists there. kwp, surface, tilt and azimuth are model estimates, not surveyed values. In this server, quality_filter=true keeps only detections identified by 2 or more sources (see source_encoding in get_data_quality_reference). Call get_data_quality_reference for the full picture before assessing fitness for a specific use case.

NameTypeReqDescription
dptstring–French département code, e.g. "33". Omit for all of France.

No output schema declared.

No examples provided.

get_source_reference ~185

Explain the data sources behind the registry's `sources` field: for each source, its code, short key, name, accepted aliases, and where the data comes from (with references: code, thesis, papers). Use it for questions like "what is FRPV?", "where does the OSM data come from?", "what is a manual correction?". The `sources` field answers "where do we have this installation?": each listed code is a dataset or process that contains it. Example: "0,1" = present in both DeepPVMapper (DPVM) and FRPV; "0,2" = present in DeepPVMapper and OpenStreetMap.

NameTypeReqDescription
sourcestring–A source name, alias or code (e.g. "frpv", "OpenStreetMap", "kasmi", "3"). Omit to list all.

No output schema declared.

No examples provided.

get_started ~71

START HERE. Call this first when the user is new, asks what this server can do, or asks a vague question about DeepPVMapper. Returns a plain-language introduction, example questions, which tool answers which kind of question, a glossary and the main caveats. Reply to the user in their own language.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_detections ~948

Search individual rooftop-PV detections by département, commune (INSEE code), estimated capacity range, and/or cross-validation confidence (min_vintages, cross_validated). Returns a bounded list of detection records plus a quality_summary for the returned sample (use get_detections_in_bbox instead for map/spatial queries with geometry). Data quality note: this is a detection dataset, not an exhaustive inventory (estimated recall ~0.6). A missing detection does not mean no PV installation exists there. kwp, surface, tilt and azimuth are model estimates, not surveyed values. In this server, quality_filter=true keeps only detections identified by 2 or more sources (see source_encoding in get_data_quality_reference). Call get_data_quality_reference for the full picture before assessing fitness for a specific use case.

NameTypeReqDescription
cross_validatedboolean–Alias of quality_filter, kept for backward compatibility.
dptstring–French département code, e.g. "33".
false_positive_statusstring–flagged = false_positive is true; not_flagged = false_positive is false; unrecorded = false_positive is null (no status recorded — NOT a confirmed true positive).
has_frpv_probaboolean–true = only detections that have an FRPV comparison (frpv_proba not null); false = only those without one. A null frpv_proba means "no comparison available", not probability 0.
has_rnb_idboolean–true = only detections matched to an RNB building identifier (rnb_id not null); false = only detections without one.
inseestring–INSEE commune code.
limitintegeryesMaximum number of records to return (max 200).
max_azimuthnumber–Maximum estimated azimuth, degrees clockwise from true north (180 = south).
max_first_seeninteger–Upper bound on first_seen imagery year.
max_kwpnumber–Maximum estimated installed capacity, in kWp.
max_last_seeninteger–Upper bound on last_seen imagery year.
max_surfacenumber–Maximum estimated PV array area, in m².
max_tiltnumber–Maximum estimated tilt from horizontal, in degrees.
max_vintagesinteger–Maximum number of imagery vintages (e.g. 1 = seen in a single year only).
min_azimuthnumber–Minimum estimated azimuth, degrees clockwise from true north (180 = south).
min_first_seeninteger–Earliest imagery year of first detection, lower bound (e.g. 2018). Not an installation date.
min_frpv_probanumber–Minimum frpv_proba. The data contract recommends 0.1 as a precision/recall trade-off. Note: detections with a null frpv_proba (no FRPV comparison available) are excluded when this is set; null does n…
min_kwpnumber–Minimum estimated installed capacity, in kWp.
min_last_seeninteger–Lower bound on last_seen imagery year.
min_surfacenumber–Minimum estimated PV array area, in m².
min_tiltnumber–Minimum estimated tilt from horizontal, in degrees.
min_vintagesinteger–Minimum number of distinct imagery vintages (years) the installation was independently detected in. Use 2+ as a persistence/confidence signal, since a one-off detection in a single vintage is more li…
quality_filterbooleanyesIf true, only include detections identified by 2 OR MORE sources(the `sources` field lists at least two codes, e.g. "0,1" = DeepPVMapper pipeline + FRPV reference, "0,2" = pipeline + OpenStreetMap).…
sources_includearray–Only include detections present in ALL of these sources. Accepts names or codes, case-insensitive: dpvm/deeppvmapper/kasmi (0), frpv/thebault (1), osm/openstreetmap (2), manual/annotation (3), recall…

No output schema declared.

No examples provided.

Install

How do I install the DeepPVMapper MCP server?

DeepPVMapper is a hosted endpoint at https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · zelhliylrlktnasircwp.supabase.co

# add to Claude Code
claude mcp add --transport http gabrielkasmi-deeppvmapper 'https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp'
Common questions

What is the DeepPVMapper MCP server?

DeepPVMapper is an MCP server listed in the public MCP registry as io.github.gabrielkasmi/deeppvmapper. Open registry of 1.14M+ rooftop-solar detections across France, queryable by natural language. This page covers its hosted endpoint (https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp).

Is the DeepPVMapper MCP server safe to use?

DeepPVMapper scores 76 out of 100 on VerifyMCP. 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 DeepPVMapper MCP server expose?

DeepPVMapper exposes 17 tools: get_data_quality_reference, get_department_capacity_stats, get_department_yearly_stats, search_detections, aggregate_detection_capacity, and 12 more. Their descriptions and schemas cost roughly 5,627 tokens of context every time the server is loaded.

Does the DeepPVMapper MCP server require authentication?

No. We connected to DeepPVMapper without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the DeepPVMapper MCP server still maintained?

DeepPVMapper 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 did VerifyMCP test on the DeepPVMapper MCP server?

VerifyMCP ran 12 checks on DeepPVMapper, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about DeepPVMapper: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.