MCP servers › io.github.lavanry › docfarm

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.lavanry/docfarm

Publish, edit, share and track HTML docs and decks from chat, with view analytics. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Topic: productivity-and-docs · AI-classifiedversion 1.0.0streamable HTTP22 tools

Summary

io.github.lavanry/docfarm is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 22 tools, 3 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Tools: 22
Described as changing data: 10 of 22 toolsAI-classified
Mainly works on: files and code on the machine it runs on; accounts and data in outside web servicesAI-classified
Topic: productivity-and-docsAI-classified
Last tested: 2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 9 tools whose name or declaration suggests they change data (update_doc_settings, delete_doc, invite_collaborator, host_html_content, get_upload_url and 4 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

10 tools are described as changing something (update_doc_settings, delete_doc, invite_collaborator, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-23
Mode: read-only (no tool calls)
Latest version: 1.0.0, published 2026-10-11 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-11 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-23
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.0 (published 2026-10-11).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

22tools

3resources

0prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; accounts and data in outside web services.

10 of 22 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

whats_possiblereads or searches
“Show a grouped overview of everything docfarm can do for the user — reading, editing, sharing, tracking, drafting follow-ups, and collaborating.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
get_skillson 5 other serversreads or searches
“Load a Docfarm skill, written instructions for a task that you then follow.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
- idstring or array“One skill id such as "docfarm/onboarding", or several.”
- querystring“What the task is about, in plain words.”
get_build_briefreads or searches
“READ THIS FIRST, before writing a single line of HTML for this user.”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs
- doc_namestring“Optional.”
- accountstring“Email address of the farm to act on.”
list_docson 31 other serversreads or searches
“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 …”
Publisher declares: read-only yes · destructive no · open-world no
1 input
- accountstring“Email address of the farm to act on.”
get_doc_statusreads or searches
“Who read a doc and how.”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs
- doc_namestring“Name of the doc (fuzzy-matched).”
- slugstring“The doc's slug or share URL.”
- accountstring“Email address of the farm to act on.”
update_doc_settingscreates or changes datadescribed as changing data
“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 t…”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
11 inputs
- doc_namestring“Name of the doc (fuzzy-matched).”
- slugstring“The doc's slug or share URL.”
- titlestring“A new title for the doc (max 500 chars).”
- new_slugstring“A new ending for the share link, the part after the last slash.”
- confirm_new_linkboolean“Set true only after the person has seen the warning about the old link and said yes.”
- password_onboolean“Require a password to view.”
- password_valuestring“The password.”
- ask_nameboolean“Ask each viewer for their email before showing the doc.”
- allow_downloadsboolean“Let viewers download the original file.”
- notifyboolean“Notify the owner on views.”
- accountstring“Email address of the farm to act on.”
delete_docon 2 other serversdeletesdescribed as changing data
“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.”
Publisher declares: read-only no · destructive yes · open-world no
3 inputs
- doc_namestring“Name of the doc to delete.”
- slugstring“Share-link slug or full URL.”
- accountstring“Email address of the farm to act on.”
invite_collaboratordescribed as changing data
“Invite someone to collaborate on a doc the user OWNS, by email, so it lands in their docfarm.”
Publisher declares: read-only no · destructive yes · open-world yes
5 inputs, 2 required
- doc_namestring“Name of the doc to share.”
- slugstring“Share-link slug or full URL.”
- emailstringrequired“Email address of the person to invite.”
- allow_overwritebooleanrequired“true = collaborator's edits overwrite the original; false = edits fork into a copy they own (auto-shared back to the inviter).”
- accountstring“Email address of the farm to act on.”
suggest_linkreads or searches
“The share link a NEW doc would get, before you publish it.”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs, 1 required
- namestringrequired“The page name you will publish under.”
- slugstring“Optional.”
- accountstring“Email address of the farm to act on.”
host_html_contentcreates or changes datadescribed as changing data
“Host an HTML doc on docfarm and return its share link.”
Publisher declares: read-only no · destructive yes · open-world no
6 inputs, 2 required
- htmlstringrequired“Full HTML body”
- namestringrequired“Page name.”
- slugstring“Optional.”
- replaceboolean“Omit normally.”
- brand_fromstring“Optional.”
- accountstring“Email address of the farm to act on.”
duplicate_doccreates or changes datadescribed as changing data
“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.”
Publisher declares: read-only no · destructive no · open-world no
4 inputs, 1 required
- doc_namestring“Source doc name (fuzzy-matched).”
- slugstring“Source share-link slug or full URL.”
- new_namestringrequired“Name for the copy in the user's farm.”
- accountstring“Email address of the farm to act on.”
get_upload_urlon 9 other serversreads or searches
“Step 1 of 2 for hosting a large HTML file that is already on disk, without sending its bytes through the model's context.”
Publisher declares: read-only no · destructive no · open-world no
1 input
- accountstring“Email address of the farm to act on.”

Show 10 more tools

finalize_uploadon 4 other serverscreates or changes datadescribed as changing data
“FAST PATH step 2/2: after PUTting the file to the signed URL from `get_upload_url`, call this to publish.”
Publisher declares: read-only no · destructive yes · open-world no
4 inputs, 2 required
- namestringrequired“Doc name — same rules as host_html_content (existing name = in-place update).”
- upload_pathstringrequired“The upload_path value returned by get_upload_url.”
- slugstring“Optional.”
- accountstring“Email address of the farm to act on.”
get_doc_htmlreads or searches
“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).”
Publisher declares: read-only yes · destructive no · open-world no
6 inputs
- doc_namestring“Doc name.”
- slugstring“Share-link slug or full URL.”
- offsetnumber“Character offset to start reading from (default 0).”
- max_charsnumber“Max characters to return per call (default 200000, max 500000).”
- strip_data_urisboolean“Default true: base64 data URIs ≥1KB are replaced with short placeholders so content isn't crowded out by embedded images.”
- accountstring“Email address of the farm to act on.”
get_doc_urlreads or searches
“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.”
Publisher declares: read-only yes · destructive no · open-world no
5 inputs
- doc_namestring
- slugstring
- ttl_secondsnumber“Lifetime of the signed URL in seconds.”
- download_filenamestring“If set, the URL forces a file download with this filename (Content-Disposition: attachment).”
- accountstring“Email address of the farm to act on.”
patch_doccreates or changes datadescribed as changing data
“Edit an existing hosted doc by replacing a snippet of its HTML.”
Publisher declares: read-only no · destructive yes · open-world no
7 inputs
- doc_namestring“Name of the doc to edit (same name you passed to host_html_content).”
- slugstring“Share-link slug or full URL.”
- before_snippetstring“Exact text to find (must be unique unless occurrence_index given).”
- after_snippetstring“Replacement text.”
- occurrence_indexnumber“0-based index of which match to replace when before_snippet isn't unique”
- patchesarray“Several edits applied atomically.”
- accountstring“Email address of the farm to act on.”
rebuild_doccreates or changes datadescribed as changing data
“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.”
Publisher declares: read-only no · destructive no · open-world no
4 inputs
- doc_namestring“Name of the PDF or PowerPoint doc to rebuild (fuzzy-matched).”
- slugstring“Share-link slug or full URL.”
- brand_fromstring“Optional.”
- accountstring“Email address of the farm to act on.”
check_rebuildcreates or changes datadescribed as changing data
“Check a rebuild started by `rebuild_doc` and publish it when it is done.”
Publisher declares: read-only no · destructive yes · open-world no
3 inputs, 1 required
- rebuild_idstringrequired“The rebuild_id returned by rebuild_doc.”
- namestring“Name for the rebuilt doc.”
- accountstring“Email address of the farm to act on.”
show_doccontrols a browser or desktop
“Open a doc inside the chat as a live view of the page.”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs
- doc_namestring“Name of the doc (fuzzy-matched).”
- slugstring“The doc's slug or share URL.”
- accountstring“Email address of the farm to act on.”
app_read_docreads or searches
“Used by the docfarm doc view inside the chat, not by the assistant.”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs, 1 required
- slugstringrequired“The doc's slug.”
- accountstring“Email address of the farm to act on.”
app_apply_editscreates or changes datadescribed as changing data
“Used by the docfarm doc view inside the chat, not by the assistant.”
Publisher declares: read-only no · destructive yes · open-world no
4 inputs, 3 required
- slugstringrequired“The doc's slug.”
- revstringrequired“The rev app_read_doc returned for the bytes being edited.”
- editsarrayrequired
- accountstring“Email address of the farm to act on.”
list_accountson 42 other serversreads or searches
“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).”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 22 tools
Says what it returns: 71% of 21 tools
States limits, defaults or errors: 9% of 22 tools
Says when to use it: 47% of 19 tools
Items covered per tool: 2.3 of 4 on average

Counted from the listing

Parameters with a description: 96% of 79
Tools with a description: 100% of 22
Typical description length: 544 characters

The tool set

Counted from the listing

Tools: 22
Size of the list: about 7,495 tokens for an agent to load (characters ÷ 4)
Naming: 22 of 22 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 22 of 22 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://mcp.doc.farm/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "docfarm": {
      "url": "https://mcp.doc.farm/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "docfarm": {
      "type": "http",
      "url": "https://mcp.doc.farm/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"docfarm","type":"http","url":"https://mcp.doc.farm/mcp"}'

Claude Code

claude mcp add --transport http docfarm https://mcp.doc.farm/mcp

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.doc.farm/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint mcp.doc.farm/mcp	Session opened	matches	our test · 2026-10-23
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.lavanry/docfarm

Answered from the data above

Is io.github.lavanry/docfarm safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 10 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.lavanry/docfarm need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.lavanry/docfarm been security tested?

Partly. 4 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can io.github.lavanry/docfarm do?

It lists 22 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete and control a browser or desktop. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.lavanry/docfarm change or delete data?

10 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.MrGo2/icloud-mcpiCloud MCPalso has tools that controls a browser or desktop, creates or changes data, deletes, reads or searchescompare with this one
io.github.JonathanRReed/apple-tools-mcpApple Tools (Unified)also has tools that controls a browser or desktop, creates or changes data, deletes, reads or searchescompare with this one
io.github.Shuffzord/roadravenRoadRavenalso has tools that controls a browser or desktop, creates or changes data, deletes, reads or searchescompare with this one
com.granoflow/mcp-serverGranoflowalso has tools that controls a browser or desktop, creates or changes data, deletes, reads or searchescompare with this one
io.github.amineutron/mcp-trackingTask tracking (sessions, ETA, dashboard)also has tools that controls a browser or desktop, creates or changes data, deletes, reads or searchescompare with this one
io.github.nuncaeslupus/doc-controldoc-controlalso has tools that controls a browser or desktop, creates or changes data, deletes, reads or searchescompare with this one

Active servers whose topic is also “productivity-and-docs” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 3

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
768 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 22 tools, 3 resources, 0 prompts.
4,238 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

productivity-and-docs

AI-classified · 2026-10-23

Pricing modelAI-classified

no value

No value: the AI answer was held back because the quoted text did not clearly support it.

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-23

MCP capability

resources, tools

our test · 2026-10-23

Transport

streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.lavanry/docfarm: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.lavanry/docfarm

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.lavanry/docfarm)](https://protocolprobe.com/mcp/servers/io.github.lavanry/docfarm)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology