# Continuity (remote · continuitywriter.com)

Private story bible for fiction writers, shared with AI assistants over MCP.

- Trust score: 79/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-07

## Components

- remote · `continuitywriter.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/lahutchins91-continuity/continuitywriter.md), [page](https://verifymcp.io/servers/lahutchins91-continuity/continuitywriter)

## Channel facts

- Endpoint: `https://continuitywriter.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-07.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 880 tokens (~80/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Continuity MCP server?

Continuity is a hosted endpoint at https://continuitywriter.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http lahutchins91-continuity 'https://continuitywriter.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "lahutchins91-continuity": {
      "url": "https://continuitywriter.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lahutchins91-continuity": {
      "type": "http",
      "url": "https://continuitywriter.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.lahutchins91-continuity]
url = "https://continuitywriter.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lahutchins91-continuity": {
      "type": "remote",
      "url": "https://continuitywriter.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lahutchins91-continuity --url 'https://continuitywriter.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lahutchins91-continuity:
    url: "https://continuitywriter.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "lahutchins91-continuity": {
      "Transport": "http",
      "Url": "https://continuitywriter.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add lahutchins91-continuity -t streamable-http -u 'https://continuitywriter.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "lahutchins91-continuity": {
      "type": "http",
      "url": "https://continuitywriter.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-07 (score 79, +3)

- [security improvement] Authorization: fail → pass
- [security] First check of Authorization: partial

### 2026-10-04 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-02 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-01 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-30 (score 74)

First indexed and scored.

## MCP tools (11)

### `list_story_projects` (~45 tokens)

list story projects

Find the user’s saved story projects before starting or resuming a story. Use the returned ID; do not guess projects. Page with offset.

Input parameters:

- `offset` (integer)

Output parameters:

- `data`

### `create_story_project` (~41 tokens)

create story project

Create a new private story project when the user asks. Does not save canon or scenes.

Input parameters:

- `description` (string)
- `name` (string, required)

Output parameters:

- `data`

### `get_continuity_context` (~87 tokens)

get continuity context

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.

Input parameters:

- `limit` (integer)
- `projectId` (string, required)
- `request` (string, required)

Output parameters:

- `data`

### `search_story_canon` (~69 tokens)

search story canon

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.

Input parameters:

- `offset` (integer)
- `projectId` (string, required)
- `query` (string)

Output parameters:

- `data`

### `upsert_canon_entry` (~126 tokens)

upsert canon entry

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.

Input parameters:

- `content` (string, required)
- `expectedRevision` (integer)
- `kind` (string, required)
- `projectId` (string, required)
- `revisionReason` (string)
- `status` (string, required)
- `tags` (array)
- `title` (string, required)

Output parameters:

- `data`

### `get_canon_history` (~45 tokens)

get canon history

Read previous and new content for a saved canon entry, newest first. No changes are made.

Input parameters:

- `canonEntryId` (string, required)
- `offset` (integer)

Output parameters:

- `data`

### `list_approved_scenes` (~49 tokens)

list approved scenes

Read approved scene summaries in story order. Page with offset to inspect older scenes or verify a scene number before saving.

Input parameters:

- `offset` (integer)
- `projectId` (string, required)

Output parameters:

- `data`

### `record_approved_scene` (~100 tokens)

record approved scene

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.

Input parameters:

- `continuityNotes` (string)
- `projectId` (string, required)
- `replaceExisting` (boolean)
- `sceneNumber` (integer, required)
- `summary` (string, required)
- `title` (string)

Output parameters:

- `data`

### `save_story_checkpoint` (~120 tokens)

save story checkpoint

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.

Input parameters:

- `checkpointId` (required)
- `nextSteps` (array)
- `openThreads` (array)
- `projectId` (string, required)
- `storyState` (string, required)
- `title` (string, required)

Output parameters:

- `data`

### `list_story_checkpoints` (~50 tokens)

list story checkpoints

Retrieve provisional story handoffs to recover progress across chats. These notes never override approved canon. Page with offset for older checkpoints.

Input parameters:

- `offset` (integer)
- `projectId` (string, required)

Output parameters:

- `data`

### `continuity_audit` (~65 tokens)

continuity audit

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.

Input parameters:

- `offset` (integer)
- `projectId` (string, required)
- `proposedText` (string, required)

Output parameters:

- `data`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lahutchins91-continuity/continuitywriter#diagnostics

## Score history

- 2026-10-07: 79
- 2026-10-05: 76
- 2026-10-04: 76
- 2026-10-03: 75
- 2026-10-02: 75
- 2026-10-01: 74
- 2026-09-30: 74

## Common questions

### What is the Continuity MCP server?

Continuity is an MCP server listed in the public MCP registry as io.github.LAHutchins91/continuity. Private story bible for fiction writers, shared with AI assistants over MCP. This page covers its hosted endpoint (https://continuitywriter.com/mcp).

### Is the Continuity MCP server safe to use?

Continuity scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Continuity MCP server expose?

Continuity exposes 11 tools: list_story_projects, create_story_project, get_continuity_context, search_story_canon, upsert_canon_entry, and 6 more. Their descriptions and schemas cost roughly 797 tokens of context every time the server is loaded.

### Does the Continuity MCP server require authentication?

Yes. Continuity asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Continuity MCP server still maintained?

Continuity is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://continuitywriter.com/mcp
- Repository: https://github.com/LAHutchins91/continuity-mcp
- Website: https://continuitywriter.com/
- Changelog RSS feed: https://verifymcp.io/servers/lahutchins91-continuity/continuitywriter.xml
- Changelog JSON feed: https://verifymcp.io/servers/lahutchins91-continuity/continuitywriter.json
- HTML version of this page: https://verifymcp.io/servers/lahutchins91-continuity/continuitywriter