Remote MCP · Endpoint

Citewren MCP server

No. Citewren answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://citewren.cybermaxtools.com/mcp?via=mcp-registry

The last check completed an MCP handshake.

Registry name
dev.workers.cybermax-tools.cybermax/citewren
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
56 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
AI search readiness MCP: score a site for ChatGPT/Claude/Perplexity crawlers. 3 free/day.
Listing
From the official MCP registry (active).
Recent checks of Citewren
CheckedResultHandshake
3 hours agoHandshake completed56 ms
13 hours agoHandshake completed86 ms
2 days agoHandshake completed239 ms
4 days agoHandshake completed75 ms
7 days agoHandshake completed59 ms
9 days agoHandshake completed115 ms
11 days agoHandshake completed144 ms
14 days agoHandshake completed40 ms
15 days agoHandshake completed238 ms
18 days agoHandshake completed84 ms
20 days agoHandshake completed91 ms
21 days agoHandshake completed64 ms
23 days agoHandshake completed112 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.

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