Remote MCP · Endpoint

io.github.cyanheads/bluesky-mcp-server MCP server

No. io.github.cyanheads/bluesky-mcp-server answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://bluesky.caseyjhand.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.cyanheads/bluesky-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
247 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Search Bluesky posts and feeds; read profiles, threads, and trends. STDIO or Streamable HTTP.
Listing
From the official MCP registry (active).
Recent checks of io.github.cyanheads/bluesky-mcp-server
CheckedResultHandshake
1 hour agoHandshake completed247 ms
1 day agoHandshake completed269 ms
2 days agoHandshake completed288 ms
3 days agoHandshake completed284 ms
4 days agoHandshake completed433 ms
5 days agoHandshake completed142 ms
6 days agoHandshake completed285 ms
9 days agoHandshake completed378 ms
11 days agoHandshake completed129 ms
14 days agoHandshake completed837 ms
16 days agoHandshake completed315 ms
18 days agoHandshake completed122 ms
20 days agoHandshake completed200 ms
22 days agoHandshake completed103 ms
24 days agoHandshake completed81 ms
26 days agoHandshake completed124 ms
27 days agoHandshake completed100 ms
28 days agoHandshake completed610 ms

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

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 io.github.cyanheads/bluesky-mcp-server and makes no claim about it beyond what these checks measured.