Remote MCP · Endpoint

AI PM Lab MCP server

No. AI PM Lab answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://aipmlab.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.aipmlab/ai-pm-lab
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
97 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Learn how AI products work: lessons, model cost comparisons, real experiments, PM guides.
Listing
From the official MCP registry (active).
Recent checks of AI PM Lab
CheckedResultHandshake
2 hours agoHandshake completed97 ms
1 day agoHandshake completed520 ms
3 days agoHandshake completed120 ms
3 days agoHandshake completed80 ms
4 days agoHandshake completed69 ms
5 days agoHandshake completed114 ms
7 days agoHandshake completed1.25 s
10 days agoHandshake completed92 ms
12 days agoHandshake completed113 ms
15 days agoHandshake completed182 ms
17 days agoHandshake completed661 ms
19 days agoHandshake completed75 ms
21 days agoHandshake completed92 ms
23 days agoHandshake completed366 ms
25 days agoHandshake completed632 ms

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

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