Skip to content

Continuity by Ouroboros Apps MCP server

io.github.LAHutchins91/continuityLAHutchins91streamable-httpv0.5.2Scanned

Story continuity, novel memory, and series bible for fiction writers, shared with AI assistants

11 tools: 2 can delete or cancel things, 2 change things and 7 only read.

Tools: 2 delete, 0 irreversible, 2 write, 7 read.
  • Reads private data · 2
  • Reads text others write · 3
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Continuity by Ouroboros Apps MCP server can do

The Continuity by Ouroboros Apps MCP server is published by the GitHub account LAHutchins91. It has 11 tools. It can delete or cancel things (2 tools: upsert_canon_entry and record_approved_scene) and create or change data (2 tools: create_story_project and save_story_checkpoint). 7 tools only read.

2 tools read private data (get_continuity_context and list_story_checkpoints); 3 tools bring in text other people can write (get_continuity_context, search_story_canon and list_story_checkpoints).

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 0.5.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Deletes or cancels 2Claude Code: deny
  • record_approved_sceneStore a concise summary of a scene the user has approved.No findings

    Why it is in this group

    • The description's first verb is "store": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Store a concise summary of a scene the user has approved. Never record an unapproved draft. An occupied scene number is preserved unless replaceExisting is true and the user requested replacement. Identical retries return the saved scene.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • upsert_canon_entrySave a fact or revise canon only after the user approves it.No findings

    Why it is in this group

    • The name "upsert_canon_entry" says "upsert": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Save a fact or revise canon only after the user approves it. Preserve the existing title/kind. LOCKED requires approval as established fact; brainstorming is not approval. Existing entries require expectedRevision from retrieval; conflicting edits fail without overwriting. Identical retries leave revision history unchanged.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 2Claude Code: ask
  • create_story_projectCreate a new private story project when the user asks.No findings

    Why it is in this group

    • The name "create_story_project" says "create": a word for a change.
    Description, as the server wrote it
    Create a new private story project when the user asks. Does not save canon or scenes.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • save_story_checkpointPreserve a concise story-session handoff when the user asks to save progress or has authorized ongoing checkpoints for this story.1 finding

    Why it is in this group

    • The name "save_story_checkpoint" says "save": a word for a change.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...d story state, never a full transcript, credentials, or unrelated personal details. Reuse c..."

      What this check looks for
    Description, as the server wrote it
    Preserve a concise story-session handoff when the user asks to save progress or has authorized ongoing checkpoints for this story. Stores provisional notes, not canon or an approved scene. Separate established progress from unresolved ideas. Send only focused story state, never a full transcript, credentials, or unrelated personal details. Reuse checkpointId on retries.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 7Show 7 read-only tools
  • continuity_auditRetrieve locked canon for the assistant to compare against a short proposed scene.No findings

    Why it is in this group

    • The description's first verb is "retrieve": a word for reading.
    Description, as the server wrote it
    Retrieve locked canon for the assistant to compare against a short proposed scene. This tool supplies evidence; the assistant must identify contradictions. Does not save or approve the scene.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_canon_historyRead previous and new content for a saved canon entry, newest first.No findings

    Why it is in this group

    • The name "get_canon_history" says "get": a word for reading.
    Description, as the server wrote it
    Read previous and new content for a saved canon entry, newest first. No changes are made.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_continuity_contextRetrieve relevant canon, recent approved scenes, and the latest provisional checkpoint before continuing a saved story or recovering it in a new chat.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_continuity_context" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "retrieve" and "chat": it reads messages.
    • untrusted-inputThe description's first sentence says "retrieve" and "chat": it reads messages, which other people can write.
    Description, as the server wrote it
    Retrieve relevant canon, recent approved scenes, and the latest provisional checkpoint before continuing a saved story or recovering it in a new chat. request is a brief scene/topic query, never a chat transcript. Results are a selection; use search_story_canon for specific missing facts.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_approved_scenesRead approved scene summaries in story order.No findings

    Why it is in this group

    • The name "list_approved_scenes" says "list": a word for reading.
    Description, as the server wrote it
    Read approved scene summaries in story order. Page with offset to inspect older scenes or verify a scene number before saving.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_story_checkpointsRetrieve provisional story handoffs to recover progress across chats.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_story_checkpoints" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "retrieve" and "chat": it reads messages.
    • untrusted-inputThe description's first sentence says "retrieve" and "chat": it reads messages, which other people can write.
    Description, as the server wrote it
    Retrieve provisional story handoffs to recover progress across chats. These notes never override approved canon. Page with offset for older checkpoints.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_story_projectsFind the user’s saved story projects before starting or resuming a story.No findings

    Why it is in this group

    • The name "list_story_projects" says "list": a word for reading.
    Description, as the server wrote it
    Find the user’s saved story projects before starting or resuming a story. Use the returned ID; do not guess projects. Page with offset.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_story_canonSearch saved canon by literal title/content text, or browse every entry with an empty query and offset.Reads text others writeNo findings

    Why it is in this group

    • The name "search_story_canon" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Search saved canon by literal title/content text, or browse every entry with an empty query and offset. Use to verify details before revising an entry or when context retrieval omits something.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:58 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://continuitywriter.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://kufinkiktgnnhusuenjq.supabase.co/auth/v1
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (2 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://continuitywriter.com/mcp: tools/list returned 11 tools to an anonymous client, including upsert_canon_entry (destructive), record_approved_scene (destructive), create_story_project (write), save_story_checkpoint (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.5.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http continuity https://continuitywriter.com/mcp
claude mcp add --transport http continuity https://continuitywriter.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__continuity__list_story_projects",
      "mcp__continuity__get_continuity_context",
      "mcp__continuity__search_story_canon",
      "mcp__continuity__get_canon_history",
      "mcp__continuity__list_approved_scenes",
      "mcp__continuity__list_story_checkpoints",
      "mcp__continuity__continuity_audit"
    ],
    "ask": [
      "mcp__continuity__create_story_project",
      "mcp__continuity__save_story_checkpoint"
    ],
    "deny": [
      "mcp__continuity__upsert_canon_entry",
      "mcp__continuity__record_approved_scene"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as continuity. Review it before you use it.

Capability tags behind 3 rules
  • mcp__continuity__get_continuity_context private-data, untrusted-input
  • mcp__continuity__search_story_canon untrusted-input
  • mcp__continuity__list_story_checkpoints private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.LAHutchins91/continuity/verify?hash=66b4c97d8eb0afb7facc88e704134f1f487571ae1f163dcb2cb71728870c4018" | jq -e '.changed == false'

Pinned hash 66b4c97d8eb0, from Nov 16, 2026, 00:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.LAHutchins91/continuity/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.LAHutchins91/continuity
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.LAHutchins91/continuity.svg)](https://radar.anlyon.com/servers/io.github.LAHutchins91/continuity)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:17 UTC.

Continuity by Ouroboros Apps MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Continuity by Ouroboros Apps MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Continuity by Ouroboros Apps MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: upsert_canon_entry and record_approved_scene.

Can the Continuity by Ouroboros Apps MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Continuity by Ouroboros Apps MCP server have?

11 tools: 2 destructive, 2 write, 7 read. upsert_canon_entry, record_approved_scene, create_story_project, save_story_checkpoint, list_story_projects, get_continuity_context, search_story_canon, get_canon_history and 3 more.

Does the Continuity by Ouroboros Apps MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Continuity by Ouroboros Apps MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Continuity by Ouroboros Apps MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.