Remote MCP · Endpoint

SkillDB Catalog MCP server

No. SkillDB Catalog answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://skilldb.dev/api/mcp/catalog

The last check completed an MCP handshake.

Registry name
io.github.latentsmurf/skilldb-catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
89 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Find AI agent skills: public previews and source links. Read-only discovery; no account required.
Listing
From the official MCP registry (active).
Recent checks of SkillDB Catalog
CheckedResultHandshake
10 hours agoHandshake completed89 ms
3 days agoHandshake completed81 ms
12 days agoHandshake completed73 ms
13 days agoHandshake completed72 ms
14 days agoHandshake completed69 ms
15 days agoHandshake completed114 ms
16 days agoHandshake completed72 ms
17 days agoHandshake completed71 ms
18 days agoHandshake completed66 ms
20 days agoHandshake completed79 ms
22 days agoHandshake completed68 ms
25 days agoHandshake completed111 ms
27 days agoHandshake completed74 ms
30 days agoHandshake completed67 ms

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

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