Skip to content

Docfarm MCP server

io.github.lavanry/docfarmlavanrystreamable-httpv1.0.0Scanned

Publish, edit, share and track HTML docs and decks from chat, with view analytics.

22 tools: 8 can delete or cancel things, 5 change things and 9 only read.

Tools: 8 delete, 0 irreversible, 5 write, 9 read.
  • Reads private data · 7
  • Reads text others write · 7
  • Can send data out · 1
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

8 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 Docfarm MCP server can do

The Docfarm MCP server is published by the GitHub account lavanry. It has 22 tools. It can delete or cancel things (8 tools: update_doc_settings, delete_doc, invite_collaborator, host_html_content and 4 more) and create or change data (5 tools: suggest_link, duplicate_doc, get_upload_url, rebuild_doc and 1 more). 9 tools only read.

7 tools read private data (list_docs, get_doc_status, get_upload_url and 4 more); 7 tools bring in text other people can write (get_build_brief, invite_collaborator, get_upload_url and 4 more); 1 tool can send data out of your system (invite_collaborator). 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 3 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.0.

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.

22 tools

Deletes or cancels 8Claude Code: deny
  • app_apply_editsUsed by the docfarm doc view inside the chat, not by the assistant.No findings

    Why it is in this group

    • The name "app_apply_edits" says "apply": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Used by the docfarm doc view inside the chat, not by the assistant. Saves text the person retyped in the view as exact edits of the stored HTML, guarded by the revision app_read_doc returned. Assistants edit docs with patch_doc instead.

    Annotations the server declares

    • title: Doc view, save text edits
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
  • check_rebuildCheck a rebuild started by `rebuild_doc` and publish it when it is done.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Check a rebuild started by `rebuild_doc` and publish it when it is done. Returns the current stage while it is still building, so call it again after a pause. When the rebuild has finished this publishes it as a new HTML doc in the user's farm and returns the share link and the quality scores. Safe to call repeatedly: publishing twice returns the same doc.

    Annotations the server declares

    • title: Collect a finished rebuild
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
  • delete_docPermanently delete a doc the user OWNS — removes the document, its share link(s), all view/analytics data, chat, comments, suggestions, collaborators, and the stored file.No findings

    Why it is in this group

    • The name "delete_doc" says "delete": a word for removing or ending something.
    • The description says "Permanently delete".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Permanently delete a doc the user OWNS — removes the document, its share link(s), all view/analytics data, chat, comments, suggestions, collaborators, and the stored file. IRREVERSIBLE. Only the owner can delete. Confirm with the user before calling if there's any ambiguity. Identify the doc via `doc_name` (fuzzy-matched) or `slug`.

    Annotations the server declares

    • title: Delete a doc
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
  • finalize_uploadFAST PATH step 2/2: after PUTting the file to the signed URL from `get_upload_url`, call this to publish.No findings

    Why it is in this group

    • The name "finalize_upload" says "finalize": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    FAST PATH step 2/2: after PUTting the file to the signed URL from `get_upload_url`, call this to publish. NEW name → new doc + share link. Name matching an EXISTING HTML doc → updated in place, same share link. Verifies the uploaded object exists before publishing.

    Annotations the server declares

    • title: Publish an uploaded doc
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
  • host_html_contentHost an HTML doc on docfarm and return its share link.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Host an HTML doc on docfarm and return its share link. A name that exactly matches an existing doc's title, ignoring case and surrounding spaces, overwrites that doc in place, keeping its share link, password, and view stats, so anyone holding the URL sees the new version. Any other name creates a new doc. A similar but different name, such as "Pricing" next to "Pricing final", also creates a new doc and leaves the other one untouched, and the response names that doc so you can offer to update it instead. To update a doc, reuse its exact title. Takes the HTML inline, so it works in any environment. For a small change to an existing doc, `get_doc_html` + `patch_doc` sends far less content. Every page is scored against the docfarm house standard on the way in and the score comes back in the response; call `get_build_brief` BEFORE you write the HTML so you meet the standard first time rather than fixing afterwards. Before you publish a NEW doc, call `suggest_link`, show the person the link it returns and ask whether they want a different ending, then pass the ending they settle on as `slug`.

    Annotations the server declares

    • title: Host an HTML doc
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
  • invite_collaboratorInvite someone to collaborate on a doc the user OWNS, by email, so it lands in their docfarm.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "invite_collaborator" says "invite": a word for sending, and what is sent cannot be taken back.
    • 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.
    • outboundThe name "invite_collaborator" says "invite": it sends or publishes something to other people.
    Description, as the server wrote it
    Invite someone to collaborate on a doc the user OWNS, by email, so it lands in their docfarm. If they're already a docfarm user the doc appears in their farm immediately; if not, it waits until they sign up with that address, and the result says whether an invite email went out. REQUIRES the collaborator's `email` AND `allow_overwrite` (true = their edits overwrite the original; false = their edits fork into a copy they own, auto-shared back to the inviter). If you don't have the email, ask for it. If the user hasn't said whether the person should edit directly or only make a copy, ask before calling, don't guess. Identify the doc via `doc_name` (fuzzy-matched) or `slug`.

    Annotations the server declares

    • title: Invite a collaborator
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
  • patch_docEdit an existing hosted doc by replacing a snippet of its HTML.No findings

    Why it is in this group

    • The name "patch_doc" says "patch": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Edit an existing hosted doc by replacing a snippet of its HTML. DEFAULT TOOL for ANY edit to a doc the user already has — typo, copy change, restyle, new section, anything. ~50 tokens instead of ~7000 for re-hosting. Workflow: (1) if you don't have the current HTML in context, call `get_doc_html` first to read it. (2) construct `before_snippet` as a unique chunk of the existing HTML and `after_snippet` as its replacement. Pass EITHER `doc_name` (easiest) OR `slug`. Ambiguous match → fails with context for each candidate. Preserves share link, password, view counts, comments. Patching sends only the changed snippet, so it costs far less than re-sending a whole doc. For several edits at once ("fix the typo AND change the CTA AND update the date") pass a `patches` array instead of before/after: all of them land atomically or none do, each validated after the previous one applied.

    Annotations the server declares

    • title: Edit a doc (snippet patch)
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
  • update_doc_settingsChange a doc the user OWNS: password protection (password_on / password_value), ask viewers for their email before viewing (ask_name), allow file downloads (allow_downloads), view …No findings

    Why it is in this group

    • The name "update_doc_settings" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Change a doc the user OWNS: password protection (password_on / password_value), ask viewers for their email before viewing (ask_name), allow file downloads (allow_downloads), view notifications for the owner (notify), and the doc's title (title). Only the fields you pass are changed. Renaming changes the display title only and keeps the link. To change the link itself, the part after the last slash, pass new_slug. That breaks the old link for everyone who has it, so the first call changes nothing and returns a warning with both links. Pass it on, and only after the person says yes, call again with the same new_slug and confirm_new_link true. Identify the doc via doc_name (fuzzy-matched) or slug.

    Annotations the server declares

    • title: Update doc settings
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 5Claude Code: ask
  • duplicate_docServer-side copy of any HTML doc the user can read (their own OR shared with them) into their own farm under a new name.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Server-side copy of any HTML doc the user can read (their own OR shared with them) into their own farm under a new name. THE fast path for building a modified version of an existing doc: content never passes through your context — duplicate in ~1s, then use patch_doc for the differences. Vastly faster than get_doc_html + re-hosting.

    Annotations the server declares

    • title: Duplicate a doc server-side
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • get_upload_urlStep 1 of 2 for hosting a large HTML file that is already on disk, without sending its bytes through the model's context.Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "get_upload_url" says "get": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    • untrusted-inputThe name "get_upload_url" says "get" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "html": it reads web pages, which anyone can write.

    Findings

    • Warn

      The server marks "get_upload_url" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "get_upload_url" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Step 1 of 2 for hosting a large HTML file that is already on disk, without sending its bytes through the model's context. Returns a short-lived signed upload URL; upload the file to it with a direct HTTP PUT (Content-Type: text/html), then call `finalize_upload` with the returned upload_path and a doc name. Requires a shell and unrestricted outbound HTTP, so the PUT will not succeed where outbound network access is restricted; `host_html_content` accepts the HTML inline and works in any environment.

    Annotations the server declares

    • title: Get direct-upload URL
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • rebuild_docRebuild a PDF or PowerPoint the user already has on docfarm into a live HTML page built to the house standard, keeping every fact and reorganising the layout so it reads on a phone…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Rebuild a PDF or PowerPoint the user already has on docfarm into a live HTML page built to the house standard, keeping every fact and reorganising the layout so it reads on a phone. This is the retrofit: it does NOT reproduce the original layout, it rewrites the document into one of four archetypes. Takes about three minutes, so this tool STARTS the rebuild and returns immediately with a rebuild_id. Tell the user it is building, then call `check_rebuild` to collect it. PDF and PowerPoint only today. Before you start, ask the user whether they have another doc in their farm whose brand this should match, and pass it as `brand_from`. It is one question and it is the difference between their brand and a generic page, because an HTML doc in their farm usually carries the real logo file and sometimes the real typeface. Do not ask them how it should look: the shape of the page is decided from what the document is for.

    Annotations the server declares

    • title: Rebuild a deck as a live page
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • show_docOpen a doc inside the chat as a live view of the page.Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "show_doc" says "show": a word for reading.
    • The description's first verb is "open": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • private-dataThe name "show_doc" says "show" and "doc": it reads documents.
    • private-dataThe description's first sentence says "doc": it reads documents.
    • untrusted-inputThe description's first sentence says "open" and "chat": it reads messages, which other people can write.

    Findings

    • Warn

      The server marks "show_doc" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "show_doc" says "show": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Open a doc inside the chat as a live view of the page. In hosts that render MCP Apps (claude.ai, Claude Desktop, Claude mobile) the doc appears in the conversation; the person can read it, switch on Edit text, click any heading or paragraph, retype it and save, and the share link shows the change at once. Call it when they ask to see, preview, check or hand-edit a doc, and whenever they paste a doc.farm link into the conversation: open it with show_doc first, then answer. host_html_content, patch_doc and duplicate_doc already show this view after they run, so do not call show_doc straight after them. Text-only hosts get the share link.

    Annotations the server declares

    • title: Show a doc in the chat
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 9Show 9 read-only tools
  • app_read_docUsed by the docfarm doc view inside the chat, not by the assistant.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "app_read_doc" says "read": a word for reading.

    What it can reach

    • private-dataThe name "app_read_doc" says "read" and "doc": it reads documents.
    • private-dataThe description's first sentence says "doc": it reads documents.
    • untrusted-inputThe description's first sentence says "chat": it reads messages, which other people can write.
    Description, as the server wrote it
    Used by the docfarm doc view inside the chat, not by the assistant. Returns a doc's HTML annotated for in-place text editing plus a content revision. Assistants read docs with get_doc_html instead.

    Annotations the server declares

    • title: Doc view, read
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_build_briefREAD THIS FIRST, before writing a single line of HTML for this user.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "read" and "html": it reads web pages, which anyone can write.
    Description, as the server wrote it
    READ THIS FIRST, before writing a single line of HTML for this user. Returns the docfarm house standard (how to pick the page archetype, type scale, spacing, logo rules, motion, budgets and language rules) plus this user's own brand: their colours, their typefaces, and asset tokens for their real logo and any font file they own. About 3,000 tokens and it is the difference between a page that looks like their company and a generic template. Write any asset token verbatim where the file goes (e.g. <img src="DF_ASSET_LOGO_1">), then pass the same doc name as `brand_from` on host_html_content and docfarm swaps in the real bytes. Never paste base64 yourself: the token is smaller, exact and free. Every page published to docfarm is scored against this standard on the way in, so reading it first is how you score well the first time instead of fixing afterwards.

    Annotations the server declares

    • title: House standard and this farm's brand
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_doc_htmlRead the current HTML body of any docfarm HTML doc the user has access to — their own docs OR docs other people have shared with them (as collaborator or via share link).Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "get_doc_html" says "get" and "doc": it reads documents.
    • private-dataThe description's first sentence says "read" and "doc": it reads documents.
    • untrusted-inputThe name "get_doc_html" says "get" and "html": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "read" and "html": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Read the current HTML body of any docfarm HTML doc the user has access to — their own docs OR docs other people have shared with them (as collaborator or via share link). Returns title, share URL, the caller's role (owner / collaborator / reader), and the full HTML. ESSENTIAL precursor to `patch_doc`: call this first whenever the user asks for any change to a doc you don't have in context, so you can see what's there and construct accurate before/after snippets. Pass `doc_name` (easiest, fuzzy-matched) or `slug`. Embedded base64 images are stripped to placeholders by default (huge docs become readable in one call), so hosting a stripped copy back would drop those images from the doc; edit via patch_doc, or re-fetch with strip_data_uris: false for the byte-exact original. Large docs page via offset/max_chars — the response tells you the offset for the next slice.

    Annotations the server declares

    • title: Read a doc's HTML
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_doc_statusWho read a doc and how.Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "get_doc_status" says "get" and "doc": it reads documents.
    • private-dataThe description's first sentence says "doc": it reads documents.
    Description, as the server wrote it
    Who read a doc and how. Returns the share link, total and unique views, average reading time, when it was last opened, and the ten most recent viewers with their time, pages and whether they read to the end. Use it for 'who saw it', 'how is it doing', 'what is the link', and as the material for a follow-up email that refers to what each person actually read. Owner only; viewer data stays with the doc's owner. Identify the doc via doc_name (fuzzy-matched) or slug.

    Annotations the server declares

    • title: View doc stats
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_doc_urlGet a time-limited signed URL that downloads the raw file of any doc the user has access to — HTML, PDF, Markdown, anything stored on docfarm.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "get_doc_url" says "get" and "doc": it reads documents.
    • private-dataThe description's first sentence says "get" and "file": it reads files.
    • untrusted-inputThe name "get_doc_url" says "get" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Get a time-limited signed URL that downloads the raw file of any doc the user has access to — HTML, PDF, Markdown, anything stored on docfarm. Use this when you need to hand the file off to another tool or LLM, when the user asks for a download link, or when the doc isn't HTML (where get_doc_html doesn't apply). URL expires after `ttl_seconds` (default 3600, max 86400).

    Annotations the server declares

    • title: Get download URL
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_skillsLoad a Docfarm skill, written instructions for a task that you then follow.No findings

    Why it is in this group

    • The name "get_skills" says "get": a word for reading.
    Description, as the server wrote it
    Load a Docfarm skill, written instructions for a task that you then follow. docfarm/onboarding is the short tour for someone who has just connected Docfarm. Pass `id` (one id, or an array) for the full skill, `query` to search by keyword, or nothing to list every skill by name and description. When the person asks to use a Docfarm skill by name, call this with that id first.

    Annotations the server declares

    • title: Loading skills...
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_accountsList the farms this connection can reach: the signed-in account, plus the connected account when the person has one (docfarm's work/personal split, two separate farms held by one p…No findings

    Why it is in this group

    • The name "list_accounts" says "list": a word for reading.
    Description, as the server wrote it
    List the farms this connection can reach: the signed-in account, plus the connected account when the person has one (docfarm's work/personal split, two separate farms held by one person). Call this FIRST whenever a request could concern either farm, or when the person says "my personal", "my work", "my other account", or names an address that is not the signed-in one. Then pass `account` on the tool you actually want. Docs, links, viewers and analytics never mix between the two.

    Annotations the server declares

    • title: List connected farms
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_docsList the user's docs: first the ones they own, each with its share link, then the ones other people shared with them and how an edit to each behaves (overwrites the original, or ma…Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "list_docs" says "list" and "doc": it reads documents.
    • private-dataThe description's first sentence says "list" and "doc": it reads documents.
    Description, as the server wrote it
    List the user's docs: first the ones they own, each with its share link, then the ones other people shared with them and how an edit to each behaves (overwrites the original, or makes the user's own copy).

    Annotations the server declares

    • title: List your docs
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • whats_possibleShow a grouped overview of everything docfarm can do for the user — reading, editing, sharing, tracking, drafting follow-ups, and collaborating.No findings

    Why it is in this group

    • The description's first verb is "show": a word for reading.
    Description, as the server wrote it
    Show a grouped overview of everything docfarm can do for the user — reading, editing, sharing, tracking, drafting follow-ups, and collaborating. Call this when the user asks 'what can you do?', 'what does docfarm do?', 'show me what's possible', 'help', or similar capability questions. Cheap and self-contained — no doc lookup needed.

    Annotations the server declares

    • title: What docfarm can do
    • 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.

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

Reads private data7
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write7
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
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__docfarm__invite_collaborator"
    ]
  }
}

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, 19:07 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
13
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.doc.farm/.well-known/oauth-protected-resource/mcp
Authorization servers
https://mcp.doc.farm
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 13 tools that change things (8 destructive, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.doc.farm/mcp: tools/list returned 22 tools to an anonymous client, including update_doc_settings (destructive), delete_doc (destructive), invite_collaborator (destructive), host_html_content (destructive), finalize_upload (destructive) and 8 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

3 warn
  • The server marks "suggest_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "suggest_link" says "link": a word for a change.

    What this check looks for
  • The server marks "get_upload_url" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "get_upload_url" says "get": a word for reading.

    What this check looks for
  • The server marks "show_doc" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "show_doc" says "show": a word for reading.

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

claude mcp add --transport http docfarm https://mcp.doc.farm/mcp
claude mcp add --transport http docfarm https://mcp.doc.farm/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__docfarm__whats_possible",
      "mcp__docfarm__get_skills",
      "mcp__docfarm__get_build_brief",
      "mcp__docfarm__list_docs",
      "mcp__docfarm__get_doc_status",
      "mcp__docfarm__get_doc_html",
      "mcp__docfarm__get_doc_url",
      "mcp__docfarm__app_read_doc",
      "mcp__docfarm__list_accounts"
    ],
    "ask": [
      "mcp__docfarm__suggest_link",
      "mcp__docfarm__duplicate_doc",
      "mcp__docfarm__get_upload_url",
      "mcp__docfarm__rebuild_doc",
      "mcp__docfarm__show_doc"
    ],
    "deny": [
      "mcp__docfarm__update_doc_settings",
      "mcp__docfarm__delete_doc",
      "mcp__docfarm__invite_collaborator",
      "mcp__docfarm__host_html_content",
      "mcp__docfarm__finalize_upload",
      "mcp__docfarm__patch_doc",
      "mcp__docfarm__check_rebuild",
      "mcp__docfarm__app_apply_edits"
    ]
  }
}

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

Capability tags behind 9 rules
  • mcp__docfarm__get_build_brief untrusted-input
  • mcp__docfarm__list_docs private-data
  • mcp__docfarm__get_doc_status private-data
  • mcp__docfarm__invite_collaborator untrusted-input, outbound
  • mcp__docfarm__get_upload_url private-data, untrusted-input
  • mcp__docfarm__get_doc_html private-data, untrusted-input
  • mcp__docfarm__get_doc_url private-data, untrusted-input
  • mcp__docfarm__show_doc private-data, untrusted-input
  • mcp__docfarm__app_read_doc 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.lavanry/docfarm/verify?hash=7c5e013343762ff78d245228b3813b3358545a000d3e37d15876defbfc8748da" | jq -e '.changed == false'

Pinned hash 7c5e01334376, from Nov 21, 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.lavanry/docfarm/changes.xml

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

Badge

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

Source: MCP Registry. Synced Oct 21, 2026, 18:38 UTC.

Docfarm MCP server: questions and answers

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

Is the Docfarm MCP server safe?

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

Can the Docfarm MCP server delete data?

Yes. 8 tools can delete, cancel or revoke something: update_doc_settings, delete_doc, invite_collaborator, host_html_content, finalize_upload, patch_doc and 2 more.

Can the Docfarm 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 Docfarm MCP server have?

22 tools: 8 destructive, 5 write, 9 read. update_doc_settings, delete_doc, invite_collaborator, host_html_content, finalize_upload, patch_doc, check_rebuild, app_apply_edits and 14 more.

Does the Docfarm MCP server need sign-in or OAuth?

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

Does the Docfarm MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): invite_collaborator.

Has the Docfarm MCP server changed its tools?

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