Remote MCP · Endpoint

Citewren MCP server

No. Citewren answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://citewren.cybermax-tools.workers.dev/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
992 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 15 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
1 hour agoHandshake completed992 ms
1 day agoHandshake completed131 ms
2 days agoHandshake completed99 ms
2 days agoHandshake completed128 ms
4 days agoHandshake completed138 ms
7 days agoHandshake completed138 ms
9 days agoHandshake completed92 ms
12 days agoHandshake completed121 ms
14 days agoHandshake completed325 ms
16 days agoHandshake completed110 ms
18 days agoHandshake completed189 ms
20 days agoHandshake completed117 ms
22 days agoHandshake completed89 ms
24 days agoHandshake completed86 ms
25 days agoHandshake completed99 ms

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

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.