Remote MCP · Endpoint

AI Developer Toolkit documentation MCP server

No. AI Developer Toolkit documentation answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://developertoolkit.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.mjaskolski/developer-toolkit-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
588 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Search and read guides on Claude Code, Codex and Cursor, in English and Polish.
Listing
From the official MCP registry (active).
Recent checks of AI Developer Toolkit documentation
CheckedResultHandshake
1 hour agoHandshake completed588 ms
1 day agoHandshake completed633 ms
2 days agoHandshake completed82 ms
3 days agoHandshake completed949 ms
4 days agoHandshake completed1.24 s
5 days agoHandshake completed550 ms
6 days agoHandshake completed1.50 s
9 days agoHandshake completed472 ms
11 days agoHandshake completed591 ms
14 days agoHandshake completed694 ms
16 days agoHandshake completed614 ms
18 days agoHandshake completed620 ms
20 days agoHandshake completed634 ms
22 days agoHandshake completed586 ms
24 days agoHandshake completed703 ms
26 days agoHandshake completed417 ms
27 days agoHandshake completed1.05 s
29 days agoHandshake completed836 ms

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

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