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 · SCANNED SEP 26

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

62 Trust /100
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 Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1952 tokens (~244/item across 8 items; 8 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 Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 75% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
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'
// .cursor/mcp.json
{
  "mcpServers": {
    "gabrielkasmi-deeppvmapper": {
      "url": "https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "gabrielkasmi-deeppvmapper": {
      "type": "http",
      "url": "https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.gabrielkasmi-deeppvmapper]
url = "https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gabrielkasmi-deeppvmapper": {
      "type": "remote",
      "url": "https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add gabrielkasmi-deeppvmapper --url 'https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  gabrielkasmi-deeppvmapper:
    url: "https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "gabrielkasmi-deeppvmapper": {
      "Transport": "http",
      "Url": "https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp"
    }
  }
}
# add to Vellum
assistant mcp add gabrielkasmi-deeppvmapper -t streamable-http -u 'https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp'
// mcp.json
{
  "mcpServers": {
    "gabrielkasmi-deeppvmapper": {
      "type": "http",
      "url": "https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 26 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 25 Sept 26 62

    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 26 Sept 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 26 Aug 2026 24 Nov 2026 ECDSA 256 ECDSA-SHA256 7c35296a896c0a6f13f8495266045d45
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. present 7786 8 Verified
supabase.co. absent 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 · 8 exposed · ~1,952 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 ~490

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. Call get_data_quality_reference for the full picture before assessing fitness for a specific use case.

NameTypeReqDescription
cross_validatedboolean–If true, only include detections confirmed by at least two independent sources (e.g. the automated DeepPVMapper pipeline plus OpenStreetMap or the FRPV reference dataset), not just a single pipeline.…
dptstring–French département code, e.g. "33".
inseestring–INSEE commune code.
max_kwpnumber–Maximum estimated installed capacity, in kWp.
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…
min_kwpnumber–Minimum estimated installed capacity, in kWp.
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 (default), only include detections with frpv_proba >= 0.1, the threshold recommended in the data contract for a good precision/recall trade-off.

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 ~203

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. 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_yearly_stats ~131

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. 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_detections_in_bbox ~187

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. 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.

search_detections ~386

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. Call get_data_quality_reference for the full picture before assessing fitness for a specific use case.

NameTypeReqDescription
cross_validatedboolean–If true, only include detections confirmed by at least two independent sources (e.g. the automated DeepPVMapper pipeline plus OpenStreetMap or the FRPV reference dataset), not just a single pipeline.…
dptstring–French département code, e.g. "33".
inseestring–INSEE commune code.
limitintegeryesMaximum number of records to return (max 200).
max_kwpnumber–Maximum estimated installed capacity, in kWp.
min_kwpnumber–Minimum estimated installed capacity, in kWp.
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 (default), only include detections with frpv_proba >= 0.1, the threshold recommended in the data contract for a good precision/recall trade-off.

No output schema declared.

No examples provided.

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 62 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 8 tools: get_data_quality_reference, get_department_capacity_stats, get_department_yearly_stats, search_detections, aggregate_detection_capacity, and 3 more. Their descriptions and schemas cost roughly 1,952 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 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.