Remote MCP · Endpoint

Continuity by Ouroboros Apps MCP server

No. Continuity by Ouroboros Apps answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://continuitywriter.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.LAHutchins91/continuity
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
73 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Story continuity, novel memory, and series bible for fiction writers, shared with AI assistants
Listing
From the official MCP registry (active).
Recent checks of Continuity by Ouroboros Apps
CheckedResultHandshake
2 hours agoHandshake completed73 ms
2 days agoHandshake completed69 ms
4 days agoHandshake completed103 ms
6 days agoHandshake completed90 ms
9 days agoHandshake completed104 ms
11 days agoHandshake completed64 ms
13 days agoHandshake completed70 ms
14 days agoHandshake completed100 ms
16 days agoHandshake completed86 ms
17 days agoHandshake completed99 ms
18 days agoHandshake completed59 ms
21 days agoHandshake completed80 ms
22 days agoHandshake completed59 ms
24 days agoHandshake completed69 ms

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

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 Continuity by Ouroboros Apps and makes no claim about it beyond what these checks measured.