Continuity
REMOTE · CONTINUITYWRITER.COM · SCANNED OCT 7
Private story bible for fiction writers, shared with AI assistants over MCP.
Available components
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. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 880 tokens (~80/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · continuitywriter.com
claude mcp add --transport http lahutchins91-continuity 'https://continuitywriter.com/mcp'
{
"mcpServers": {
"lahutchins91-continuity": {
"url": "https://continuitywriter.com/mcp"
}
}
} {
"servers": {
"lahutchins91-continuity": {
"type": "http",
"url": "https://continuitywriter.com/mcp"
}
}
} [mcp_servers.lahutchins91-continuity] url = "https://continuitywriter.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lahutchins91-continuity": {
"type": "remote",
"url": "https://continuitywriter.com/mcp",
"enabled": true
}
}
} openclaw mcp add lahutchins91-continuity --url 'https://continuitywriter.com/mcp' --transport streamable-http
mcp_servers:
lahutchins91-continuity:
url: "https://continuitywriter.com/mcp" {
"McpServers": {
"lahutchins91-continuity": {
"Transport": "http",
"Url": "https://continuitywriter.com/mcp"
}
}
} assistant mcp add lahutchins91-continuity -t streamable-http -u 'https://continuitywriter.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 7 Oct 26 +3
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- 4 Oct 26 +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.
- 2 Oct 26 +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.
- 1 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Sept 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Oct 2026 · Probed https://continuitywriter.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=continuitywriter.com | CN=YR2,O=Let's Encrypt,C=US | 23 Sept 2026 | 22 Dec 2026 | RSA 2048 | SHA256-RSA | 5b0efcae1d734d8221bc1b707d0045ee44c |
| SANs: continuitywriter.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of continuitywriter.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| continuitywriter.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://continuitywriter.com/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://continuitywriter.com/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Protected resource metadata
| Document | https://continuitywriter.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://continuitywriter.com/mcp |
| Authorisation server | https://kufinkiktgnnhusuenjq.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://continuitywriter.com/mcp | Verified | 200 | |
| http (plaintext) | http://continuitywriter.com/mcp | HTTPS enforced | 308 | https://continuitywriter.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
continuity_audit continuity audit ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | – | – |
| projectId | string | yes | – |
| proposedText | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
create_story_project create story project ~41
Create a new private story project when the user asks. Does not save canon or scenes.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
get_canon_history get canon history ~45
Read previous and new content for a saved canon entry, newest first. No changes are made.
| Name | Type | Req | Description |
|---|---|---|---|
| canonEntryId | string | yes | – |
| offset | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
get_continuity_context get continuity context ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| projectId | string | yes | – |
| request | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
list_approved_scenes list approved scenes ~49
Read approved scene summaries in story order. Page with offset to inspect older scenes or verify a scene number before saving.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | – | – |
| projectId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
list_story_checkpoints list story checkpoints ~50
Retrieve provisional story handoffs to recover progress across chats. These notes never override approved canon. Page with offset for older checkpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | – | – |
| projectId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
list_story_projects list story projects ~45
Find the user’s saved story projects before starting or resuming a story. Use the returned ID; do not guess projects. Page with offset.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
record_approved_scene record approved scene ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| continuityNotes | string | – | – |
| projectId | string | yes | – |
| replaceExisting | boolean | – | – |
| sceneNumber | integer | yes | – |
| summary | string | yes | – |
| title | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
save_story_checkpoint save story checkpoint ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| checkpointId | – | yes | – |
| nextSteps | array | – | – |
| openThreads | array | – | – |
| projectId | string | yes | – |
| storyState | string | yes | – |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
search_story_canon search story canon ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | – | – |
| projectId | string | yes | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
upsert_canon_entry upsert canon entry ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| expectedRevision | integer | – | – |
| kind | string | yes | – |
| projectId | string | yes | – |
| revisionReason | string | – | – |
| status | string | yes | – |
| tags | array | – | – |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
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.