Remote MCP · Endpoint

DevDocs10 MCP server

No. DevDocs10 answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://devdocs10.com/mcp

The last check completed an MCP handshake.

Registry name
com.devdocs10/docs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
90 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search and read tested Swift, JavaScript, CSS and HTML docs from DevDocs10.
Listing
From the official MCP registry (active).
Recent checks of DevDocs10
CheckedResultHandshake
34 minutes agoHandshake completed90 ms
9 days agoHandshake completed212 ms
10 days agoHandshake completed153 ms
11 days agoHandshake completed91 ms
12 days agoHandshake completed89 ms
14 days agoHandshake completed144 ms
14 days agoHandshake completed82 ms
15 days agoHandshake completed93 ms
17 days agoHandshake completed353 ms
19 days agoHandshake completed159 ms
21 days agoHandshake completed319 ms
24 days agoHandshake completed177 ms
26 days agoHandshake completed184 ms
28 days agoHandshake completed100 ms

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

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