Remote MCP · Endpoint

ModelsLab Agent Control Plane MCP server

No. ModelsLab Agent Control Plane answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://modelslab.com/mcp/agents

The last check completed an MCP handshake.

Registry name
io.github.ModelsLab/modelslab-agents
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
80 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Account, billing, team, API key and model discovery tools for agents that use ModelsLab.
Listing
From the official MCP registry (active).
Recent checks of ModelsLab Agent Control Plane
CheckedResultHandshake
37 minutes agoHandshake completed80 ms
3 days agoHandshake completed624 ms
13 days agoHandshake completed124 ms
13 days agoHandshake completed98 ms
15 days agoHandshake completed62 ms
16 days agoHandshake completed59 ms
17 days agoHandshake completed114 ms
18 days agoHandshake completed71 ms
18 days agoHandshake completed69 ms
20 days agoHandshake completed111 ms
22 days agoHandshake completed92 ms
25 days agoHandshake completed91 ms
27 days agoHandshake completed91 ms
30 days agoHandshake completed82 ms

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

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