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.

dochost

REMOTE · DOCHOST.IO

Publish, list, update and delete shareable Markdown/HTML pages from your AI assistant.

Available components

0 this week 92 Trust /100

Last scanned (20 hours ago)

Scores higher than 99% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Documents and Files

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security94
Transport & Reachability100
Schema Quality & AI Usability75
  • 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 1503 tokens (~167/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 Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 55% 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 10 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
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.

  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 30 Oct 26 0
    • Tool “publish” rewrote its description, which is the text the model reads security
  • 26 Oct 26 +2
    • Authorization: fail → pass ▲ security
  • 25 Oct 26 −2
    • Authorization: pass → fail ▼ security
  • 20 Oct 26 +2
    • HSTS header: fail → pass ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
  • 9 Oct 26 0
    • Schema quality: 117 → 159 ▼ functional
    • Tool coverage: 27% → 55% ▲ functional
  • 28 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
  • 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
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 4 Nov 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 29 Sept 2026 28 Dec 2026 ECDSA 256 ECDSA-SHA256 84ccadf2515b4f880e6449b5afbc91de
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 38690 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"
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff

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,207 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 ~88

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 when you need plan limits, domain details or paid-option availability; a basic publish can use defaults without this extra call. The primary host is chosen in the dashboard (manageDomainsUrl), not through this API.

Input schema present but exposes no named parameters.

NameTypeReqDescription
analyticsstring––
customDomainboolean–Whether this plan may point a hostname the user owns at their pages (set it at manageDomainsUrl).
customSlugboolean––
customSubdomainboolean–Whether this plan may claim a {name}.dochost.co subdomain (set it at manageDomainsUrl).
manageDomainsUrlstring–Dashboard 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–
primaryHoststring–Host 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
brandingHiddenboolean–Whether 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–
notestring–Present when the page is expired or under review. Relay it before editing.
sha256string|null–Pass 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 ~345

Publish HTML or Markdown as a hosted web page and return a shareable URL. Use when the user asks to share an HTML quiz, calculator, report or Markdown document as a link. HTML JavaScript runs in a sandbox. Free links expire after seven days, or three days when published with public set to false; paid link lifetime and options follow account entitlements. For revisions of an existing page, use update_page to keep the same link. Results report expiry and any ignored options; relay ignoredOptions/ignoredNote instead of claiming all requested settings were applied. New links use the account primary host; get_account reports it.

NameTypeReqDescription
bodystringyesComplete HTML or Markdown source to publish, preserving scripts and styles. Pass the content itself, not a summary, file path, URL or surrounding Markdown code fence. Single-file HTML must inline ass…
customSlugstring–Requested custom URL slug, subject to plan entitlement and availability. Omit unless the user requests one.
formatstring–Use html for HTML source and markdown for Markdown. Omit only when you want automatic format detection.
noBrandingboolean–Omit to use the plan default: paid plans hide branding, free plans keep it. Set false if the user wants to keep the dochost mark.
passwordstring–Requested reader password, subject to plan entitlement. Omit unless requested; check ignoredOptions/ignoredNote before claiming password protection.
publicboolean–Whether the page is discoverable on Explore (default true). False does not password-protect the link; readers with its URL can still access an unprotected page.
NameTypeReqDescription
expiresAtstring|null–ISO timestamp, or null when the link is permanent.
firstPublishWelcomestring–Present only on the account's first publish: relay the link and offer the one next step it describes.
formatstringyes–
ignoredNotestring–Plain-language consequence of ignoredOptions. Relay it instead of reporting plain success.
ignoredOptionsarray–Paid options this account does not have, which were dropped. Present only when non-empty — the publish still succeeded, but NOT as asked.
iterateHintstring–How to revise this page later. Follow it instead of publishing a second time.
notestring–Free-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
passwordstring–Set or replace the page password (paid plans).
publicboolean–Discoverable on Explore. Cannot be true while a password is set.
removePasswordboolean–Clear the password. Always allowed, on any plan.
searchableboolean–Opt in to search-engine indexing. Turning it on requires a permanent page.
slugstringyes–
NameTypeReqDescription
changedboolean–False 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––
ifShastring–Write only if the live body still hashes to this (from get_page_content).
ifVersioninteger–Write 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.

Install

How do I install the dochost MCP server?

dochost 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'
Common questions

What is the dochost MCP server?

dochost is an MCP server listed in the public MCP registry as io.github.zyli5313/dochost-mcp. Publish, list, update and delete shareable Markdown/HTML pages from your AI assistant. This page covers its hosted endpoint (https://dochost.io/api/mcp).

Is the dochost MCP server safe to use?

dochost scores 92 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 dochost MCP server expose?

dochost exposes 8 tools: publish, list_my_pages, get_account, get_page, get_page_content, and 3 more. Their descriptions and schemas cost roughly 1,207 tokens of context every time the server is loaded.

Does the dochost MCP server require authentication?

Yes. dochost 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 dochost MCP server still maintained?

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