Remote MCP · Endpoint

DeepPVMapper MCP server

No. DeepPVMapper answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://zelhliylrlktnasircwp.supabase.co/functions/v1/mcp/mcp

The last check completed an MCP handshake.

Registry name
io.github.gabrielkasmi/deeppvmapper
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
343 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Open registry of 1.14M+ rooftop-solar detections across France, queryable by natural language.
Listing
From the official MCP registry (active).
Recent checks of DeepPVMapper
CheckedResultHandshake
5 hours agoHandshake completed343 ms
9 days agoHandshake completed364 ms
10 days agoHandshake completed397 ms
11 days agoHandshake completed520 ms
12 days agoHandshake completed266 ms
14 days agoHandshake completed302 ms
14 days agoHandshake completed366 ms
15 days agoHandshake completed219 ms
17 days agoHandshake completed383 ms
19 days agoHandshake completed327 ms
22 days agoHandshake completed272 ms
24 days agoHandshake completed320 ms
26 days agoHandshake completed336 ms
28 days agoHandshake completed414 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 28.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with DeepPVMapper and makes no claim about it beyond what these checks measured.