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.

io.github.zyli5313/dochost-mcp

REMOTE · DOCHOST.IO · SCANNED SEP 20

Publish Markdown or HTML to a shareable link from your AI assistant. OAuth, no API keys.

Available components

0 this week 90 Trust /100
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 Security89
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1060 tokens (~117/item across 9 items; 8 tools + 1 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 27% of tool parameters carry a description.Partial
  • 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
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 9 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
  • Supports UI / widget rendering.Pass
Install

How do I install the io.github.zyli5313/dochost-mcp server?

io.github.zyli5313/dochost-mcp is a hosted endpoint at https://dochost.io/api/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 · dochost.io

# add to Claude Code
claude mcp add --transport http zyli5313-dochost-mcp 'https://dochost.io/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "zyli5313-dochost-mcp": {
      "url": "https://dochost.io/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "zyli5313-dochost-mcp": {
      "type": "http",
      "url": "https://dochost.io/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.zyli5313-dochost-mcp]
url = "https://dochost.io/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zyli5313-dochost-mcp": {
      "type": "remote",
      "url": "https://dochost.io/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add zyli5313-dochost-mcp --url 'https://dochost.io/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  zyli5313-dochost-mcp:
    url: "https://dochost.io/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "zyli5313-dochost-mcp": {
      "Transport": "http",
      "Url": "https://dochost.io/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add zyli5313-dochost-mcp -t streamable-http -u 'https://dochost.io/api/mcp'
// mcp.json
{
  "mcpServers": {
    "zyli5313-dochost-mcp": {
      "type": "http",
      "url": "https://dochost.io/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 20 Sept 26 0
    • Tool “get_account” rewrote its description, which is the text the model reads security
    • Tool “get_page” rewrote its description, which is the text the model reads security
    • Tool “publish” rewrote its description, which is the text the model reads security
    • Tool “update_page” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail functional
    • Tool coverage: 0% → 27% functional
    • New tool “get_page_content” functional
    • New tool “set_page_options” functional
    • “update_page” added an optional parameter “ifSha” cosmetic
    • “update_page” added an optional parameter “ifVersion” cosmetic
  • 18 Sept 26 −1

    No change was recorded against any check on this day. Endpoint Security went from 91 to 89.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Endpoint Security went from 89 to 91.

  • 6 Sept 26 0
    • Tool “get_account” rewrote its description, which is the text the model reads security
    • Tool “publish” rewrote its description, which is the text the model reads security
    • Schema quality: 63 → 72 functional
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

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

  • 11 Aug 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
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 20 Sept 2026 · Probed https://dochost.io/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dochost.io CN=WE1,O=Google Trust Services,C=US 1 Aug 2026 30 Oct 2026 ECDSA 256 ECDSA-SHA256 522aa5c777063d56135bee68793a981a
SANs: dochost.io, www.dochost.io, *.www.dochost.io
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 dochost.io. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
dochost.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://dochost.io/api/auth/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://dochost.io/api/auth/.well-known/oauth-protected-resource"

Protected resource metadata

Document https://dochost.io/api/auth/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://dochost.io
Authorisation server https://dochost.io

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://dochost.io/api/mcp Verified 200
http (plaintext) http://dochost.io/api/mcp HTTPS enforced 301 https://dochost.io/api/mcp
MCP tools · 8 exposed · ~1,031 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
delete_page ~49

Permanently delete one of your pages by slug. The link stops working immediately and the slug is freed. Deleting an already-deleted page is a safe no-op.

NameTypeReqDescription
slugstringyes
NameTypeReqDescription
alreadyDeletedboolean
okbooleanyes
slugstringyes

No examples provided.

get_account ~74

Get your plan, page-quota usage, entitlement flags (size cap, custom slug, password, branding, subdomain, custom domain), and the primary host new links publish on. Call before publishing so you know your limits up front. The primary host is chosen in the dashboard (manageDomainsUrl), not through this API.

Input schema present but exposes no named parameters.

NameTypeReqDescription
analyticsstring
customDomainbooleanWhether this plan may point a hostname the user owns at their pages (set it at manageDomainsUrl).
customSlugboolean
customSubdomainbooleanWhether this plan may claim a {name}.dochost.co subdomain (set it at manageDomainsUrl).
manageDomainsUrlstringDashboard page where the user adds domains and picks the primary one. Send them here to change it.
noBrandingboolean
okbooleanyes
pageQuotainteger|null
pagesRemaininginteger|null
pagesUsedinteger
passwordboolean
permanentLinksboolean
planstringyes
primaryHoststringHost new links publish on: a custom domain, `{sub}.dochost.co`, or `dochost.co/d`.
sizeCapMbinteger

No examples provided.

get_page ~86

Get one of your pages by slug: title, format, status, view/like counts, expiry, whether it is password-protected, and its current visibility / indexing / branding state. Never returns the page body or the password — call get_page_content when you need the source itself, and set_page_options to change any of the settings it reports.

NameTypeReqDescription
slugstringyes
NameTypeReqDescription
brandingHiddenbooleanWhether the RENDERED page hides the dochost mark, resolved from the live plan — not a per-page setting. Read-only.
createdAtstring
expiresAtstring|null
formatstring
hasPasswordboolean
likesinteger
okbooleanyes
permanentboolean
publicboolean
searchableboolean
slugstringyes
statusstring
titlestring|null
urlstringyes
viewsinteger

No examples provided.

get_page_content ~129

Read back the CURRENT Markdown or HTML of one of your pages. Call this before update_page whenever you did not write the live content yourself in this same conversation — update_page replaces the body wholesale, so editing from memory silently discards anything you cannot see, including edits the user made in the browser. Returns `version` and `sha256`; pass them to update_page as ifVersion / ifSha so the write is refused instead of overwriting a change you did not read. Expired pages are readable, and updating one republishes it on the same URL.

NameTypeReqDescription
slugstringyes
NameTypeReqDescription
bodystringyesThe raw Markdown or HTML exactly as published.
bytesintegeryes
editablebooleanyes
formatstringyes
notestringPresent when the page is expired or under review. Relay it before editing.
sha256string|nullPass to update_page as ifSha to guard the write.
slugstringyes
statusstringyes
titlestring|null
urlstringyes
versionintegeryesPass to update_page as ifVersion to guard the write.

No examples provided.

list_my_pages ~47

List the pages you have published to dochost, newest first. Paginated; returns compact records (no page bodies).

NameTypeReqDescription
limitinteger
offsetinteger
NameTypeReqDescription
hasMorebooleanyes
limitintegeryes
offsetintegeryes
pagesarrayyes
totalintegeryes

No examples provided.

publish ~183

Publish Markdown or HTML as a hosted dochost page and get a shareable URL. Respects your plan: link lifetime, password protection, custom slug, and branding all follow your account entitlements. Paid plans publish without dochost branding by default — pass noBranding: false to keep the mark. When the account cannot have an option you asked for, the publish still succeeds and the result carries ignoredOptions + ignoredNote — relay that instead of reporting plain success. The link is issued on the account's primary host (a custom domain or subdomain when one is set in Settings › Domains, otherwise dochost.co/d); get_account reports which.

NameTypeReqDescription
bodystringyes
customSlugstring
formatstring
noBrandingboolean
passwordstring
publicboolean
NameTypeReqDescription
expiresAtstring|nullISO timestamp, or null when the link is permanent.
formatstringyes
ignoredNotestringPlain-language consequence of ignoredOptions. Relay it instead of reporting plain success.
ignoredOptionsarrayPaid options this account does not have, which were dropped. Present only when non-empty — the publish still succeeded, but NOT as asked.
iterateHintstringHow to revise this page later. Follow it instead of publishing a second time.
notestringFree-tier only: expiry warning + upgrade link. Relay this to the user.
permanentbooleanyes
slugstringyes
urlstringyesThe shareable page URL, on the account's primary host (custom domain, subdomain, or dochost.co/d). Relay it verbatim.

No examples provided.

set_page_options ~238

Change a published page's visibility, search-engine indexing or password WITHOUT republishing it — the URL, view count and content all stay the same. Use this instead of deleting and publishing again, which changes the link the user already shared. Send only the fields you want to change. Turning a paid capability off never needs an entitlement; turning one on is checked against the current plan. A password always forces the page private, so asking for both `public: true` and a password is refused rather than silently resolved. dochost branding is NOT settable here: it is resolved from the account's live plan at render time, so there is nothing per-page to flip — read `brandingHidden` from get_page for the rendered answer.

NameTypeReqDescription
passwordstringSet or replace the page password (paid plans).
publicbooleanDiscoverable on Explore. Cannot be true while a password is set.
removePasswordbooleanClear the password. Always allowed, on any plan.
searchablebooleanOpt in to search-engine indexing. Turning it on requires a permanent page.
slugstringyes
NameTypeReqDescription
changedbooleanFalse when the page already had exactly these settings.
hasPasswordboolean
okbooleanyes
publicboolean
searchableboolean
slugstringyes
urlstring

No examples provided.

update_page ~225

Replace the content of one of your pages in place. The URL, view/like counts, and expiry stay the same; only the body, format, and title change. Resending identical content is a no-op. Prefer this over publishing again whenever the user is revising something you already published for them — a second publish creates a second link and strands the one they already shared. This replaces the WHOLE body, so unless you wrote the live content yourself in this conversation, call get_page_content first and pass its version/sha256 back as ifVersion/ifSha — the write is then refused with the current version instead of overwriting an edit you never saw.

NameTypeReqDescription
bodystringyes
formatstring
ifShastringWrite only if the live body still hashes to this (from get_page_content).
ifVersionintegerWrite only if the page is still at this version (from get_page_content). Omit and the write always wins.
slugstringyes
titlestring
NameTypeReqDescription
formatstring
okbooleanyes
slugstringyes
titlestring|null
versioninteger

No examples provided.

Common questions

What is the io.github.zyli5313/dochost-mcp server?

io.github.zyli5313/dochost-mcp is listed in the public MCP registry as io.github.zyli5313/dochost-mcp. Publish Markdown or HTML to a shareable link from your AI assistant. OAuth, no API keys. This page covers its hosted endpoint (https://dochost.io/api/mcp).

Is the io.github.zyli5313/dochost-mcp server safe to use?

io.github.zyli5313/dochost-mcp scores 90 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 io.github.zyli5313/dochost-mcp server expose?

io.github.zyli5313/dochost-mcp exposes 8 tools: publish, list_my_pages, get_account, get_page, get_page_content, and 3 more. Their descriptions and schemas cost roughly 1,031 tokens of context every time the server is loaded.

Does the io.github.zyli5313/dochost-mcp server require authentication?

Yes. io.github.zyli5313/dochost-mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the io.github.zyli5313/dochost-mcp server still maintained?

io.github.zyli5313/dochost-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.