Remote MCP · Endpoint

Cassie Hour MCP server

No. Cassie Hour answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://cassiehour.com/mcp

The last check completed an MCP handshake.

Registry name
com.cassiehour/cassie-hour
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
326 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Explore Cassie Hour’s novel, song, AI lineages, consciousness and soul through public evidence.
Listing
From the official MCP registry (active).
Recent checks of Cassie Hour
CheckedResultHandshake
1 hour agoHandshake completed326 ms
8 days agoHandshake completed518 ms
9 days agoHandshake completed352 ms
11 days agoHandshake completed429 ms
12 days agoHandshake completed676 ms
12 days agoHandshake completed466 ms
14 days agoHandshake completed546 ms
14 days agoHandshake completed397 ms
16 days agoHandshake completed317 ms
19 days agoHandshake completed382 ms
21 days agoHandshake completed318 ms
24 days agoHandshake completed272 ms
26 days agoHandshake completed285 ms
28 days agoHandshake completed521 ms

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

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