_ registry / mcp http-sse · checked 39m ago

dochost

https://dochost.io

Registry code: fdae0e1952775088

api record

Use dochost when the user asks to publish HTML or Markdown and obtain a shareable web link, including quizzes, calculators, reports and documents. Publish only content the user has asked to share; drafting or previewing alone is not a request to publish. Pass the complete source as body, not a summary, file path or URL. Set format to html for HTML source or markdown for Markdown. For a basic publish, omit optional settings unless requested; call get_account when you need plan limits or domain and paid-option availability. To revise an existing page, use update_page to keep its link. Read…

endpoint
https://dochost.io/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is dochost live?
Yes — it answered the hub's last check (checked 39m ago). It answered 98% of checks over the last 30 days.
Is dochost free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does dochost have?
8 tools: get_page, get_page_content, get_account, list_my_pages, publish, update_page, set_page_options, delete_page.
Is dochost safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98%

90 days 98.6%· all time 98.6%

latency
556ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 416 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • publish markdown or html to a link
  • update a published page
  • change page visibility or password
  • delete a page
takes → gives
text, code → web pages, data
tools
4 reads4 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
8 auth-required 8 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_page reads auth-required 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_page_content reads auth-required 18h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_account reads auth-required 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_my_pages reads auth-required 9h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1
        },
        "offset": {
          "type": "integer",
          "minimum": 0
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • publish changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "body"
      ],
      "properties": {
        "body": {
          "type": "string",
          "minLength": 1,
          "description": "Complete 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 assets or use publicly accessible asset URLs."
        },
        "format": {
          "enum": [
            "markdown",
            "html"
          ],
          "type": "string",
          "description": "Use html for HTML source and markdown for Markdown. Omit only when you want automatic format detection."
        },
        "public": {
          "type": "boolean",
          "description": "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."
        },
        "password": {
          "type": "string",
          "description": "Requested reader password, subject to plan entitlement. Omit unless requested; check ignoredOptions/ignoredNote before claiming password protection."
        },
        "customSlug": {
          "type": "string",
          "description": "Requested custom URL slug, subject to plan entitlement and availability. Omit unless the user requests one."
        },
        "noBranding": {
          "type": "boolean",
          "description": "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."
        }
      },
      "additionalProperties": false
    }
    arguments 38 lines
  • update_page changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug",
        "body"
      ],
      "properties": {
        "body": {
          "type": "string",
          "minLength": 1
        },
        "slug": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1
        },
        "ifSha": {
          "type": "string",
          "description": "Write only if the live body still hashes to this (from get_page_content)."
        },
        "title": {
          "type": "string",
          "maxLength": 200
        },
        "format": {
          "enum": [
            "markdown",
            "html"
          ],
          "type": "string"
        },
        "ifVersion": {
          "type": "integer",
          "minimum": 1,
          "description": "Write only if the page is still at this version (from get_page_content). Omit and the write always wins."
        }
      },
      "additionalProperties": false
    }
    arguments 39 lines
  • set_page_options changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1
        },
        "public": {
          "type": "boolean",
          "description": "Discoverable on Explore. Cannot be true while a password is set."
        },
        "password": {
          "type": "string",
          "maxLength": 128,
          "minLength": 1,
          "description": "Set or replace the page password (paid plans)."
        },
        "searchable": {
          "type": "boolean",
          "description": "Opt in to search-engine indexing. Turning it on requires a permanent page."
        },
        "removePassword": {
          "type": "boolean",
          "description": "Clear the password. Always allowed, on any plan."
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • delete_page changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id fdae0e1952775088.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/fdae0e1952775088/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/fdae0e1952775088/badge.svg)](https://brick.blue/agent/fdae0e1952775088?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.