Remote MCP · Endpoint

Cite Files MCP server

No. Cite Files answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://citefiles.com/mcp

The last check completed an MCP handshake.

Registry name
com.citefiles/citefiles
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
581 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Check whether AI assistants can reach, read and cite a public website. No account for 4 of 5 tools.
Website
https://citefiles.com/integrations
Listing
From the official MCP registry (active).
Recent checks of Cite Files
CheckedResultHandshake
1 hour agoHandshake completed581 ms
2 days agoHandshake completed500 ms
5 days agoHandshake completed523 ms
7 days agoHandshake completed612 ms
9 days agoHandshake completed502 ms
11 days agoHandshake completed611 ms
13 days agoHandshake completed195 ms
15 days agoHandshake completed477 ms
17 days agoHandshake completed196 ms
19 days agoHandshake completed480 ms
20 days agoHandshake completed740 ms
21 days agoHandshake completed524 ms
23 days agoHandshake completed503 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 Cite Files and makes no claim about it beyond what these checks measured.