Remote MCP · Endpoint

skill MCP server

No. skill answered an MCP handshake 42 minutes ago.

Up · key neededLast checked 42 minutes ago

Server URL

https://doc2mcp.site/api/mcp/60778812-f202-41a2-964a-1cdea1a87f6a/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
io.github.doc2mcp/skill
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
718 ms
Tools exposed
Behind credentials
Uptime, last 30 days
4 checks from 4 checks
Described by its publisher as
MCP server for skill documentation, generated by doc2mcp.
Repository
https://github.com/doc2mcp/doc2mcp-registry
Listing
From the official MCP registry (active).
Recent checks of skill
CheckedResultHandshake
42 minutes agoHandshake completed718 ms
3 hours agoHandshake completed267 ms
1 day agoHandshake completed274 ms
2 days agoHandshake completed267 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with skill and makes no claim about it beyond what these checks measured.