Remote MCP · Endpoint

citepath MCP server

No. citepath answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://citepath.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.citepath/citepath
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
707 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Citepath public MCP server for LLM readiness audits and public scan results.
Website
https://citepath.ai/
Repository
https://github.com/homezloco/citepath
Listing
From the official MCP registry (active).
Recent checks of citepath
CheckedResultHandshake
1 hour agoHandshake completed707 ms
1 day agoHandshake completed514 ms
4 days agoHandshake completed222 ms
7 days agoHandshake completed465 ms
9 days agoHandshake completed185 ms
11 days agoHandshake completed182 ms
13 days agoHandshake completed171 ms
15 days agoHandshake completed192 ms
17 days agoHandshake completed218 ms
19 days agoHandshake completed462 ms
21 days agoHandshake completed208 ms
22 days agoHandshake completed169 ms
23 days agoHandshake completed547 ms

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

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