docbin
REMOTE · MCP.DOCBIN.APP · SCANNED OCT 4
Give an agent a place to put large output. Build logs and reports get a stable versioned URL.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- 67% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 501 tokens (~100/item across 5 items; 3 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the docbin MCP server?
docbin is a hosted endpoint at https://mcp.docbin.app/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 · mcp.docbin.app
claude mcp add --transport http app-docbin-docbin 'https://mcp.docbin.app/mcp'
{
"mcpServers": {
"app-docbin-docbin": {
"url": "https://mcp.docbin.app/mcp"
}
}
} {
"servers": {
"app-docbin-docbin": {
"type": "http",
"url": "https://mcp.docbin.app/mcp"
}
}
} [mcp_servers.app-docbin-docbin] url = "https://mcp.docbin.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-docbin-docbin": {
"type": "remote",
"url": "https://mcp.docbin.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-docbin-docbin --url 'https://mcp.docbin.app/mcp' --transport streamable-http
mcp_servers:
app-docbin-docbin:
url: "https://mcp.docbin.app/mcp" {
"McpServers": {
"app-docbin-docbin": {
"Transport": "http",
"Url": "https://mcp.docbin.app/mcp"
}
}
} assistant mcp add app-docbin-docbin -t streamable-http -u 'https://mcp.docbin.app/mcp'
{
"mcpServers": {
"app-docbin-docbin": {
"type": "http",
"url": "https://mcp.docbin.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Oct 2026 · Probed https://mcp.docbin.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=docbin.app | CN=WE1,O=Google Trust Services,C=US | 6 Aug 2026 | 4 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 9b51084785a4f5000ecc2af225459bdb |
| SANs: docbin.app, mcp.docbin.app, *.mcp.docbin.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.docbin.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| docbin.app. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.docbin.app/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.docbin.app/mcp | Inconclusive | 401 |
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 →
create_doc ~390
Create a document and return its public URL. Re-using an existing name adds a new immutable version. Omit the name to get a random one. For content larger than ~10KB or any file already on disk, do NOT inline it here - run `docbin push <file> [--name <doc>]` in your shell instead (set DOCBIN_TOKEN to an API key from https://docbin.app/settings/keys). Inlining large content streams it through the model token-by-token and will time out.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | The HTML, Markdown, MDX, or code body of the document. |
| content_type | string | – | Defaults to html. 'mdx' renders Markdown with JSX components; 'code' renders a single syntax-highlighted block. |
| files | array | – | Optional: a multi-file group. When provided, supersedes content/content_type. The entry file is auto-selected (index/readme/main, else first). CROSS-FILE LINKS: to link from one file in the group to… |
| language | string | – | Syntax-highlight language hint, used when content_type is 'code' (e.g. 'rust'). |
| name | string | – | Document name. A random slug is generated if omitted. |
| visibility | string | – | Defaults to public. private = owner only; unlisted = anyone with the link; public = listed, searchable, and crawlable. |
| Name | Type | Req | Description |
|---|---|---|---|
| appUrl | string | yes | – |
| contentType | string | – | – |
| deleted | boolean | – | – |
| handle | string | yes | – |
| language | string|null | – | – |
| name | string | yes | – |
| rawUrl | string | yes | – |
| snippet | string | – | – |
| version | number | yes | – |
| visibility | string | – | – |
No examples provided.
get_doc ~65
Fetch the raw stored content of a document. Defaults to your own handle and the latest version.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | – | Owner handle. Defaults to the authenticated user. |
| name | string | yes | Document name. |
| version | number | – | Version number. Defaults to the latest. |
| Name | Type | Req | Description |
|---|---|---|---|
| appUrl | string | yes | – |
| contentType | string | – | – |
| deleted | boolean | – | – |
| handle | string | yes | – |
| language | string|null | – | – |
| name | string | yes | – |
| rawUrl | string | yes | – |
| snippet | string | – | – |
| version | number | yes | – |
| visibility | string | – | – |
No examples provided.
search_docs ~36
Search your documents by name. Returns matches with their URLs and latest versions.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | Search query matched against doc names. |
| Name | Type | Req | Description |
|---|---|---|---|
| docs | array | yes | – |
| query | string | – | – |
No examples provided.
What is the docbin MCP server?
docbin is an MCP server listed in the public MCP registry as app.docbin/docbin. Give an agent a place to put large output. Build logs and reports get a stable versioned URL. This page covers its hosted endpoint (https://mcp.docbin.app/mcp).
Is the docbin MCP server safe to use?
docbin scores 78 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 docbin MCP server expose?
docbin exposes 3 tools: create_doc, get_doc, search_docs. Their descriptions and schemas cost roughly 491 tokens of context every time the server is loaded.
Does the docbin MCP server require authentication?
No. We connected to docbin without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the docbin MCP server still maintained?
docbin is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.