Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ODocs.co

REMOTE · API.ODOCS.CO

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

Available components

+4 this week 68 Trust /100

Last scanned (19 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Documents and Files

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3029 tokens (~302/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 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.

  • 15 Nov 26 +1
    • “create-comment” reworded the description of “author” cosmetic
    • “create-document” reworded the description of “author” cosmetic
    • “patch-document” reworded the description of “author” cosmetic
    • “reply-to-comment” reworded the description of “author” cosmetic
    • “resolve-comment” reworded the description of “author” cosmetic

    5 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 14 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 64

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://api.odocs.co/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=odocs.co CN=Amazon RSA 2048 M04,O=Amazon,C=US 24 Oct 2026 9 May 2027 RSA 2048 SHA256-RSA d99357f14bcdb000c6fc6b0ed9ce860
SANs: odocs.co, www.odocs.co, api.odocs.co, origin.api.odocs.co
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.odocs.co. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
co. DS published 7786 8 Verified
odocs.co. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains
content-security-policy default-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.odocs.co/mcp Verified 200
http (plaintext) http://api.odocs.co/mcp HTTPS enforced 301 https://api.odocs.co/mcp
MCP tools · 10 exposed · ~2,941 tokens

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 →

Tool Tokens
create-comment ~330

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.

NameTypeReqDescription
authorstring–Name shown on your edits and comments (e.g. "MyAgent"), with a robot mark as an agent. Invisible and text-direction characters are removed, line breaks and control characters become spaces, and it is…
bodystringyesComment text
idstringyesDocument ID
occurrenceinteger–0-based index of the match (the earliest match is 0); required when the quote appears more than once. It counts every match in the whole doc text, including the phrase inside longer lines; approximat…
quotestringyesExact text in the document to comment on, matched exactly against the current text, like replace-text.

No output schema declared.

No examples provided.

create-document ~254

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.

NameTypeReqDescription
authorstring–Name shown on your edits and comments (e.g. "MyAgent"), with a robot mark as an agent. Invisible and text-direction characters are removed, line breaks and control characters become spaces, and it is…
contentstring–Initial document content (default: empty)
titlestringyesDocument title

No output schema declared.

No examples provided.

get-document ~481

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.

NameTypeReqDescription
formatstring–Response format: 'text' (default) is a readable .txt-style view; 'json' is the structured object.
frontmatterboolean–(text format only) Include the metadata frontmatter block. Default true; false returns just the body.
idstringyesDocument ID (UUID from the doc URL)
includeCommentsboolean–Include the comment threads in the result (the same threads list-comments returns). Default false. In json they are a comments array. In text format each thread wraps the text at its anchor (placemen…

No output schema declared.

No examples provided.

get-instructions ~62

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get-version ~195

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.

NameTypeReqDescription
formatstring–Response format: 'text' (default) is a readable .txt-style view; 'json' is the structured object.
frontmatterboolean–(text format only) Include the metadata frontmatter block. Default true; false returns just the body.
idstringyesDocument ID
indexintegeryesVersion index, as listed by list-versions

No output schema declared.

No examples provided.

list-comments ~318

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.

NameTypeReqDescription
formatstring–Response format: 'text' (default) is a readable .txt-style view; 'json' is the structured object.
idstringyesDocument ID
includeResolvedboolean–Include resolved threads too (default true); false returns open threads only.

No output schema declared.

No examples provided.

list-versions ~91

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.

NameTypeReqDescription
idstringyesDocument ID

No output schema declared.

No examples provided.

patch-document ~701

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 jo…

NameTypeReqDescription
authorstring–Name shown on your edits and comments (e.g. "MyAgent"), with a robot mark as an agent. Invisible and text-direction characters are removed, line breaks and control characters become spaces, and it is…
expectedVersioninteger–The document version from your last read. If the document has changed since, the patch is refused with 409 and nothing is applied (conflict detection).
idstringyesDocument ID
operationsarrayyesOperations, applied in order. Text-anchored ops (insert-after / insert-before / replace-text / delete-text) name exact text that the server resolves to a position; position-based ops (insert / delete…

No output schema declared.

No examples provided.

reply-to-comment ~229

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.

NameTypeReqDescription
authorstring–Name shown on your edits and comments (e.g. "MyAgent"), with a robot mark as an agent. Invisible and text-direction characters are removed, line breaks and control characters become spaces, and it is…
bodystringyesReply text
idstringyesDocument ID
threadIdstringyesComment thread ID (a thread's id in list-comments results)

No output schema declared.

No examples provided.

resolve-comment ~280

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.

NameTypeReqDescription
authorstring–Name shown on your edits and comments (e.g. "MyAgent"), with a robot mark as an agent. Invisible and text-direction characters are removed, line breaks and control characters become spaces, and it is…
idstringyesDocument ID
notestring–Optional note recorded as a reply before the thread closes, e.g. "rewrote the intro as asked"
resolvedboolean–false re-opens the thread. Default true (resolve).
threadIdstringyesComment thread ID (a thread's id in list-comments results)

No output schema declared.

No examples provided.

Install

How do I install the ODocs.co MCP server?

ODocs.co is a hosted endpoint at https://api.odocs.co/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 · api.odocs.co

# add to Claude Code
claude mcp add --transport http co-odocs-odocs 'https://api.odocs.co/mcp'
Common questions

What is the ODocs.co MCP server?

ODocs.co is an MCP server listed in the public MCP registry as co.odocs/odocs. One link any agent can edit: shared docs for people and AI agents, live. No login. This page covers its hosted endpoint (https://api.odocs.co/mcp).

Is the ODocs.co MCP server safe to use?

ODocs.co scores 68 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 ODocs.co MCP server expose?

ODocs.co exposes 10 tools: create-document, get-document, patch-document, list-versions, get-version, and 5 more. Their descriptions and schemas cost roughly 2,941 tokens of context every time the server is loaded.

Does the ODocs.co MCP server require authentication?

No. We connected to ODocs.co without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ODocs.co MCP server still maintained?

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

What did VerifyMCP test on the ODocs.co MCP server?

VerifyMCP ran 13 checks on ODocs.co, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.