dochost-mcp

Get my dochost account

get_account

Read-only

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

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`plan`	Yes
`password`	No
`analytics`	No
`pageQuota`	No
`pagesUsed`	No
`sizeCapMb`	No
`customSlug`	No
`noBranding`	No
`primaryHost`	No	Host new links publish on: a custom domain, `{sub}.dochost.co`, or `dochost.co/d`.
`customDomain`	No	Whether this plan may point a hostname the user owns at their pages (set it at manageDomainsUrl).
`pagesRemaining`	No
`permanentLinks`	No
`customSubdomain`	No	Whether this plan may claim a {name}.dochost.co subdomain (set it at manageDomainsUrl).
`manageDomainsUrl`	No	Dashboard page where the user adds domains and picks the primary one. Send them here to change it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 20, 2026

addedOutput schema / properties / customDomain

Added value: +{
+  "description": "Whether this plan may point a hostname the user owns at their pages (set it at manageDomainsUrl).",
+  "type": "boolean"
+}

addedOutput schema / properties / customSubdomain

Added value: +{
+  "description": "Whether this plan may claim a {name}.dochost.co subdomain (set it at manageDomainsUrl).",
+  "type": "boolean"
+}

Changed2 schema fields changedSep 6, 2026

addedOutput schema / properties / manageDomainsUrl

Added value: +{
+  "description": "Dashboard page where the user adds domains and picks the primary one. Send them here to change it.",
+  "type": "string"
+}

addedOutput schema / properties / primaryHost

Added value: +{
+  "description": "Host new links publish on: a custom domain, `{sub}.dochost.co`, or `dochost.co/d`.",
+  "type": "string"
+}

Changed1 schema field changedJun 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "analytics": {
+      "enum": [
+        "none",
+        "totals",
+        "full"
+      ],
+      "type": "string"
+    },
+    "customSlug": {
+      "type": "boolean"
+    },
+    "noBranding": {
+      "type": "boolean"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "pageQuota": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "pagesRemaining": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "pagesUsed": {
+      "type": "integer"
+    },
+    "password": {
+      "type": "boolean"
+    },
+    "permanentLinks": {
+      "type": "boolean"
+    },
+    "plan": {
+      "enum": [
+        "free",
+        "pro",
+        "max"
+      ],
+      "type": "string"
+    },
+    "sizeCapMb": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "ok",
+    "plan"
+  ],
+  "type": "object"
+}

First observedJun 18, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by revealing behavioral details beyond the annotations: the call should happen before publishing, and the primary host is set in the dashboard (manageDomainsUrl) rather than through this API. This helps an agent understand the tool's role and limitations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly written sentences. The first sentence front-loads the returned data, and the second provides use-case timing and a key limitation. No filler or redundant phrasing—every clause adds practical guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero parameters, the readOnly annotation, and an existing output schema, the description covers what an agent needs to know: what data is returned, when to call it, and one important caveat (host maintenance is in dashboard). There are no gaps in call prerequisites or expected behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters and 100% schema coverage, the schema fully describes the empty input. Baseline for 0 params is 4, and the description appropriately focuses on what the returned data represents (plan, quotas, flags, host) rather than inventing parameter semantics. It adds no parameter detail, but none is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Get' and clearly enumerates the exact resources returned: plan, page-quota usage, entitlement flags, and primary host. This differentiates it from page-level siblings like get_page and list_my_pages by focusing on account-level data rather than individual pages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit timing guidance: 'Call before publishing so you know your limits up front.' It also clarifies that the primary host is chosen in the dashboard and not through this API, setting a boundary on what the tool cannot do. However, it doesn't explicitly contrast with sibling alternatives like list_my_pages or get_page, which would make the guidance stronger.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All dochost-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.