Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.zyli5313/dochost-mcp

REMOTE · DOCHOST.IO · SCANNED AUG 3

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

Available components

+8 this week 76 Trust /100
Trust breakdown (6 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 →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 446 tokens (~63/item across 7 items; 6 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · dochost.io

# add to Claude Code
claude mcp add --transport http zyli5313-dochost-mcp 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"
// 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.

  • 2 Aug 26 +1

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

  • 31 Jul 26 +6
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 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
  • 29 Jul 26 +1

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

  • 27 Jul 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
  • 26 Jul 26 67

    First indexed and scored.

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 3 Aug 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
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
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 — 6 exposed · ~417 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.

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 ~42

Get your plan, page-quota usage, and entitlement flags (size cap, custom slug, password, branding). Call before publishing so you know your limits up front.

Input schema present but exposes no named parameters.

NameTypeReqDescription
analyticsstring
customSlugboolean
noBrandingboolean
okbooleanyes
pageQuotainteger|null
pagesRemaininginteger|null
pagesUsedinteger
passwordboolean
permanentLinksboolean
planstringyes
sizeCapMbinteger

No examples provided.

get_page ~53

Get one of your pages by slug: title, format, status, view/like counts, expiry, and whether it is password-protected. Never returns the page body or the password.

NameTypeReqDescription
slugstringyes
NameTypeReqDescription
createdAtstring
expiresAtstring|null
formatstring
hasPasswordboolean
likesinteger
okbooleanyes
permanentboolean
slugstringyes
statusstring
titlestring|null
urlstringyes
viewsinteger

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 ~113

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.

NameTypeReqDescription
bodystringyes
customSlugstring
formatstring
noBrandingboolean
passwordstring
publicboolean
NameTypeReqDescription
expiresAtstring|nullISO timestamp, or null when the link is permanent.
formatstringyes
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 dochost.co page URL.

No examples provided.

update_page ~113

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.

NameTypeReqDescription
bodystringyes
formatstring
slugstringyes
titlestring
NameTypeReqDescription
formatstring
okbooleanyes
slugstringyes
titlestring|null
versioninteger

No examples provided.