Home / MCP registry index / io.github.gabrielkasmi/deeppvmapper
DeepPVMapper
io.github.gabrielkasmi/deeppvmapper in the official MCP registry.
Endpoint https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp. Source: github.com/gabrielkasmi/deeppvmapper.
The registry describes it as: Open registry of 1.14M+ rooftop-solar detections across France, queryable by natural language.
We read its 17 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_data_quality_reference get_department_capacity_stats get_department_yearly_stats search_detections aggregate_detection_capacity get_detections_in_bbox get_community_activity get_community_activity_in_area count_detections get_source_breakdown get_detection_details get_department_profile get_field_coverage get_field_distribution get_field_reference get_source_reference get_started
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-gabrielkasmi-deeppvmapper)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.