Remote MCP · Endpoint

KitRank use cases MCP server

No. KitRank use cases answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://kitrank.dev/api/mcp

The last check completed an MCP handshake.

Registry name
dev.kitrank/kitrank
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
180 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only catalog of 1,900+ real, sourced AI agent use cases with tools, cost and setup prompts.
Listing
From the official MCP registry (active).
Recent checks of KitRank use cases
CheckedResultHandshake
1 hour agoHandshake completed180 ms
9 days agoHandshake completed139 ms
9 days agoHandshake completed280 ms
11 days agoHandshake completed138 ms
12 days agoHandshake completed161 ms
13 days agoHandshake completed183 ms
14 days agoHandshake completed258 ms
14 days agoHandshake completed920 ms
16 days agoHandshake completed1.16 s
19 days agoHandshake completed262 ms
21 days agoHandshake completed251 ms
24 days agoHandshake completed134 ms
26 days agoHandshake completed505 ms
28 days agoHandshake completed87 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 KitRank use cases and makes no claim about it beyond what these checks measured.