Remote MCP · Endpoint

GenPM MCP server

No. GenPM answered an MCP handshake 36 minutes ago.

UpLast checked 36 minutes ago

Server URL

https://mcp.genpm.net/

The last check completed an MCP handshake.

Registry name
io.github.GenPM-net/genpm
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
589 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search, inspect and inject full source modules (code + AI rules + MCP) pinned to a Git commit.
Listing
From the official MCP registry (active).
Recent checks of GenPM
CheckedResultHandshake
36 minutes agoHandshake completed589 ms
8 days agoHandshake completed259 ms
9 days agoHandshake completed307 ms
11 days agoHandshake completed271 ms
12 days agoHandshake completed150 ms
12 days agoHandshake completed228 ms
14 days agoHandshake completed207 ms
14 days agoHandshake completed235 ms
16 days agoHandshake completed123 ms
19 days agoHandshake completed142 ms
21 days agoHandshake completed179 ms
24 days agoHandshake completed166 ms
26 days agoHandshake completed223 ms
28 days agoHandshake completed132 ms

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

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 GenPM and makes no claim about it beyond what these checks measured.