Remote MCP · Endpoint

b/cited MCP server

No. b/cited answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://mcp.bcited.ai/public

The last check completed an MCP handshake.

Registry name
ai.bcited/bcited
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
171 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
AEO tools: scan any URL for AI-citation readiness, read the public leaderboard and citation panel.
Listing
From the official MCP registry (active).
Recent checks of b/cited
CheckedResultHandshake
6 hours agoHandshake completed171 ms
2 days agoHandshake completed256 ms
4 days agoHandshake completed170 ms
5 days agoHandshake completed49 ms
7 days agoHandshake completed189 ms
8 days agoHandshake completed240 ms
9 days agoHandshake completed145 ms
12 days agoHandshake completed301 ms
13 days agoHandshake completed132 ms
15 days agoHandshake completed205 ms
16 days agoHandshake completed140 ms
17 days agoHandshake completed166 ms
18 days agoHandshake completed190 ms
19 days agoHandshake completed157 ms
20 days agoHandshake completed183 ms
21 days agoHandshake completed252 ms
23 days agoHandshake completed184 ms

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

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