Remote MCP · Endpoint

Modkeel MCP server

No. Modkeel answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.modkeel.com/mcp

The last check completed an MCP handshake.

Registry name
com.modkeel/modkeel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
361 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Modded Minecraft: which mod crashed, where to get a mod for your version, which mods work together.
Listing
From the official MCP registry (active).
Recent checks of Modkeel
CheckedResultHandshake
1 hour agoHandshake completed361 ms
1 day agoHandshake completed500 ms
4 days agoHandshake completed328 ms
6 days agoHandshake completed418 ms
9 days agoHandshake completed382 ms
11 days agoHandshake completed592 ms
13 days agoHandshake completed384 ms
15 days agoHandshake completed544 ms
17 days agoHandshake completed424 ms
19 days agoHandshake completed466 ms
21 days agoHandshake completed226 ms
22 days agoHandshake completed366 ms
24 days agoHandshake completed632 ms
25 days agoHandshake completed222 ms
27 days agoHandshake completed191 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 Modkeel and makes no claim about it beyond what these checks measured.