Skip to content

ODocs.co MCP server

co.odocs/odocsodocs.costreamable-httpv1.0.1Scanned

One link any agent can edit: shared docs for people and AI agents, live. No login.

10 tools: 1 can delete or cancel things, 1 do something that can't be undone, 3 change things and 5 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. 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 ODocs.co MCP server can do

The ODocs.co MCP server is published by odocs.co, a domain the MCP Registry verified. It has 10 tools. It can delete or cancel things (1 tool: patch-document), do things that cannot be undone, such as sending, paying or publishing (reply-to-comment) and create or change data (3 tools: create-document, create-comment and resolve-comment). 5 tools only read.

6 tools read private data (get-document, list-versions, get-version and 3 more); 6 tools bring in text other people can write (create-document, patch-document, list-comments and 3 more); 2 tools can send data out of your system (create-comment and reply-to-comment). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

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

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 1.0.1.

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.

10 tools

Deletes or cancels 1Claude Code: deny
  • patch-documentApplies one or more edit operations, in order, to an existing ODocs.co document; people who have it open see each edit in real time.Reads text others write1 finding

    Why it is in this group

    • The name "patch-document" says "patch": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,278 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...thing applied); edits within a line and rewrites of whole lines are not affected."

      What this check looks for
    Description, as the server wrote it
    Applies one or more edit operations, in order, to an existing ODocs.co document; people who have it open see each edit in real time. Returns { id, version, ok }, plus a warning when the author name was changed. Two kinds of operation: text-anchored (insert-after / insert-before / replace-text / delete-text), where the server finds the given exact text and resolves it to a position, so no character offsets are needed; and position-based (insert / delete / replace) at an exact character offset. expectedVersion enables conflict detection: if the document changed since that version, the patch is refused with 409 and nothing is applied. Operations are not atomic: they apply one at a time to the live document and are not rolled back. When one fails, the operations before it stay applied (and visible), and the 400 body reports appliedOps: N, the number applied; sending the whole batch again applies those a second time. On an anchor failure the body can also carry nearestMatchOffset and nearestMatchSnippet; they appear only when the anchor matches the document except for whitespace (usually a different newline count), so their absence means the text is not in the document. Anchor matching is exact. LINE BREAKS: each "\n" is a paragraph break, except inside a code block (an insert strictly inside one, or a replace within one, stays in it; at its very start / end a "\n" is a paragraph break). A delete or replace across one JOINS the paragraphs (the first keeps its formatting, except that a range starting at a line start keeps the later line's paragraph); a replace with as many lines as it spans rewrites each line in place, and deleting a whole line with its "\n" joins nothing; identical whole lines at the start / end of find and replace are left out ("2\naf" → "2\nA\nB\naf" only inserts "A\nB\n"). After a join the document can differ from what a position computed before it assumed: list items after a plain paragraph can't join it (one "\n" stays), and a code block's lines joined into a paragraph become hard breaks the plain text doesn't show. While someone has the document open, a patch that would join paragraphs is refused as a whole (409 join_blocked_live_editors, nothing applied); edits within a line and rewrites of whole lines are not affected.

    Annotations the server declares

    • title: Edit Document
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
Can't be undone 1Claude Code: ask
  • reply-to-commentAdds a reply to an existing comment thread on an ODocs.co document, e.g.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "reply-to-comment" says "reply": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "reply-to-comment" says "reply": it sends or publishes something to other people.
    Description, as the server wrote it
    Adds a reply to an existing comment thread on an ODocs.co document, e.g. a note that the feedback was addressed. It does not open, resolve or re-open a thread. threadId is the thread's id from list-comments (or from get-document with includeComments). Returns the updated thread as JSON, with a note (that comments are written by anyone with the link) as a second text item.

    Annotations the server declares

    • title: Reply to Comment
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
Changes things 3Claude Code: ask
  • create-commentOpens a new comment thread on specific text in an ODocs.co document, without changing the document text.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "create-comment" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "create-comment" says "create" and "comment": it writes something other people read.
    Description, as the server wrote it
    Opens a new comment thread on specific text in an ODocs.co document, without changing the document text. Suited to review: flagging a problem, asking a question, or suggesting a change for a person to decide on. The comment is anchored to `quote` (exact text from the document, matched like replace-text; occurrence selects one match when the quote appears more than once) and is shown highlighted in the editor. Returns the new thread, including its id, as JSON, with a note (that comments are written by anyone with the link) as a second text item.

    Annotations the server declares

    • title: Create Comment
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • create-documentCreates a new ODocs.co document from a title and optional initial content, and returns its id and shareable URL.Reads text others writeNo findings

    Why it is in this group

    • The name "create-document" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Creates a new ODocs.co document from a title and optional initial content, and returns its id and shareable URL. Anyone who has the URL can read and edit the document; there is no per-person access control. Documents are temporary: a document is deleted after 7 days in which nobody, person or agent, opens or edits it. A signed-in user can save a document in the cloud from the editor, up to their account's limit; a saved document is kept until it is made temporary again. The editor offers a Markdown download. This tool only creates new documents; it does not change an existing one.

    Annotations the server declares

    • title: Create Document
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • resolve-commentMarks a comment thread on an ODocs.co document resolved, or re-opens it with resolved:false.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "resolve-comment" says "resolve": a word for reading.
    • The description's first verb is "mark": a word for a change.

    What it can reach

    • private-dataThe description's first sentence says "thread": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "resolve-comment" says "resolve" and "comment": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "mark" and "comment": it reads comments, which other people can write.
    Description, as the server wrote it
    Marks a comment thread on an ODocs.co document resolved, or re-opens it with resolved:false. Resolved threads are not counted in openCommentCount. The optional note is recorded as a reply before the thread closes, so people can see what was done. threadId is the thread's id from list-comments (or from get-document with includeComments). Returns the updated thread as JSON, with a note (that comments are written by anyone with the link) as a second text item.

    Annotations the server declares

    • title: Resolve Comment
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
Only reads 5Show 5 read-only tools
  • get-documentReads an ODocs.co document by ID.Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "get-document" says "get" and "document": it reads documents.
    • private-dataThe description's first sentence says "read" and "doc": it reads documents.
    Description, as the server wrote it
    Reads an ODocs.co document by ID. The default result is a readable plaintext (.txt-style) view: a metadata frontmatter (id, title, version, persistent, commentCount, openCommentCount, note) followed by the body. format:"json" returns { id, title, content, version, persistent, commentCount, openCommentCount } as an object; frontmatter:false returns just the body. version is the value patch-document accepts as expectedVersion for conflict detection. openCommentCount is the number of unresolved comment threads; includeComments:true adds the threads to the result. persistent is true for a document saved in the cloud, false for a temporary one. The note (that the text is written by anyone with the link) is the frontmatter's note field in the text view; json and frontmatter:false results carry it as a second text item.

    Annotations the server declares

    • title: Get Document
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get-instructionsReturns the ODocs.co integration guide as plain text: how patch positions and text anchors are matched, conflict detection with expectedVersion, document lifetime (temporary by def…Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "return" and "doc": it reads documents.
    Description, as the server wrote it
    Returns the ODocs.co integration guide as plain text: how patch positions and text anchors are matched, conflict detection with expectedVersion, document lifetime (temporary by default), error codes and rate limits. Relevant when working with an ODocs.co document link without other documentation.

    Annotations the server declares

    • title: Get ODocs Agent Guide
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get-versionReturns the content of one saved version of an ODocs.co document, by its index in list-versions.Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "return" and "doc": it reads documents.
    Description, as the server wrote it
    Returns the content of one saved version of an ODocs.co document, by its index in list-versions. The default result is a plaintext view (frontmatter: timestamp, title, note; then the content); format:"json" returns { timestamp, title, content }; frontmatter:false returns just the content. The note (that the text is written by anyone with the link) is the frontmatter's note field in the text view; json and frontmatter:false results carry it as a second text item.

    Annotations the server declares

    • title: Get Document Version
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list-commentsReturns the comment threads people or agents left on an ODocs.co document.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "return" and "thread": it reads messages.
    • untrusted-inputThe name "list-comments" says "list" and "comment": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "return" and "comment": it reads comments, which other people can write.
    Description, as the server wrote it
    Returns the comment threads people or agents left on an ODocs.co document. Each thread has an id, the quoted text it refers to, whether it is resolved, and its replies. The default result is a readable plaintext <comment> list after a frontmatter (id, commentCount, openCommentCount, note); format:"json" returns the structured array, which also carries contextBefore / contextAfter around the quote, approximateLineNumber, anchored (true when that line is where the comment is attached, false when it is only where the quote text first appears), anchorState ("attached" or "detached": the text was changed or removed; anchored and orphaned mirror it), currentText (when attached, the text the comment sits on now, which can differ from the original quote) and occurrence (with the quote as find/anchor in patch-document it matches the commented copy; null if unknown). The text tags carry the same with placement="anchor" (plus occurrence) or "text", and state="detached" for a detached thread. The note (that comments are written by anyone with the link) is the frontmatter's note field in the text view; a json result carries it as a second text item.

    Annotations the server declares

    • title: List Comments
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list-versionsLists an ODocs.co document's saved versions (version history) as an array of { index, timestamp, contributors } (contributors: who edited in that version, each { label, kind }: the…Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "list" and "doc": it reads documents.
    Description, as the server wrote it
    Lists an ODocs.co document's saved versions (version history) as an array of { index, timestamp, contributors } (contributors: who edited in that version, each { label, kind }: the name shown and human or agent), or an empty array when no version has been saved yet. The content of a version is returned by get-version for its index.

    Annotations the server declares

    • title: List Document Versions
    • readOnlyHint: true
    • destructiveHint: false
    • 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.

72 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.

Reads private data6
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__odocs__create-comment",
      "mcp__odocs__reply-to-comment"
    ]
  }
}

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 21, 2026, 19:20 UTC, unchanged since Nov 14, 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
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

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

    Matched text

    https://api.odocs.co/mcp: tools/list returned 10 tools to an anonymous client, including patch-document (destructive), reply-to-comment (irreversible), create-document (write), create-comment (write), resolve-comment (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 2,278 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...thing applied); edits within a line and rewrites of whole lines are not affected."

    What this check looks for

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 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http odocs https://api.odocs.co/mcp
claude mcp add --transport http odocs https://api.odocs.co/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__odocs__get-document",
      "mcp__odocs__list-versions",
      "mcp__odocs__get-version",
      "mcp__odocs__get-instructions",
      "mcp__odocs__list-comments"
    ],
    "ask": [
      "mcp__odocs__create-document",
      "mcp__odocs__create-comment",
      "mcp__odocs__reply-to-comment",
      "mcp__odocs__resolve-comment"
    ],
    "deny": [
      "mcp__odocs__patch-document"
    ]
  }
}

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 odocs. Review it before you use it.

Capability tags behind 10 rules
  • mcp__odocs__create-document untrusted-input
  • mcp__odocs__get-document private-data
  • mcp__odocs__patch-document untrusted-input
  • mcp__odocs__list-versions private-data
  • mcp__odocs__get-version private-data
  • mcp__odocs__get-instructions private-data
  • mcp__odocs__list-comments private-data, untrusted-input
  • mcp__odocs__create-comment untrusted-input, outbound
  • mcp__odocs__reply-to-comment untrusted-input, outbound
  • mcp__odocs__resolve-comment 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/co.odocs/odocs/verify?hash=f6df958c00d0b9b4c42a689ae9c8fde8b7596b909f7529e9e04b746cf32b14b1" | jq -e '.changed == false'

Pinned hash f6df958c00d0, from Nov 13, 2026, 13:18 UTC.

Watch

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

https://radar.anlyon.com/servers/co.odocs/odocs/changes.xml

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

Badge

Anlyon Radar badge for co.odocs/odocs
[![Anlyon Radar](https://radar.anlyon.com/badge/co.odocs/odocs.svg)](https://radar.anlyon.com/servers/co.odocs/odocs)

Source: MCP Registry. Synced Nov 13, 2026, 14:17 UTC.

ODocs.co MCP server: questions and answers

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

Is the ODocs.co MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 5 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 ODocs.co MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: patch-document.

Can the ODocs.co MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: reply-to-comment.

What tools does the ODocs.co MCP server have?

10 tools: 1 destructive, 1 irreversible, 3 write, 5 read. patch-document, reply-to-comment, create-document, create-comment, resolve-comment, get-document, list-versions, get-version and 2 more.

Does the ODocs.co MCP server need sign-in or OAuth?

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

Does the ODocs.co MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create-comment and reply-to-comment.

Has the ODocs.co MCP server changed its tools?

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