# GearHost (remote · mcp.gearhost.com)

Publish a website to a live HTTPS URL in seconds, no account needed. Keep it free on GearHost.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.gearhost.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-gearhost-mcp/mcp.md), [page](https://verifymcp.io/servers/com-gearhost-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.gearhost.com/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (unpublish_website).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 6796 tokens (~226/item across 30 items; 29 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
  - Structured output schemas are declared (93% of tools); any adoption earns full credit.
- **Tool Safety**: 94/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 3 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_publish_info" implies "publish" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 31 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the GearHost MCP server?

GearHost is a hosted endpoint at https://mcp.gearhost.com/, 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.

### Claude

```bash
claude mcp add --transport http com-gearhost-mcp 'https://mcp.gearhost.com/'
```

### Cursor

```json
{
  "mcpServers": {
    "com-gearhost-mcp": {
      "url": "https://mcp.gearhost.com/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-gearhost-mcp": {
      "type": "http",
      "url": "https://mcp.gearhost.com/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-gearhost-mcp]
url = "https://mcp.gearhost.com/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-gearhost-mcp": {
      "type": "remote",
      "url": "https://mcp.gearhost.com/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-gearhost-mcp --url 'https://mcp.gearhost.com/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-gearhost-mcp:
    url: "https://mcp.gearhost.com/"
```

### Netclaw

```json
{
  "McpServers": {
    "com-gearhost-mcp": {
      "Transport": "http",
      "Url": "https://mcp.gearhost.com/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-gearhost-mcp -t streamable-http -u 'https://mcp.gearhost.com/'
```

### Other

```json
{
  "mcpServers": {
    "com-gearhost-mcp": {
      "type": "http",
      "url": "https://mcp.gearhost.com/"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 70, +1)

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

### 2026-11-19 (score 69, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 6034 → 6796
- [functional] New tool “create_database”
- [functional] New tool “create_mailbox”
- [functional] New tool “enable_email”

### 2026-11-18 (score 68, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 5198 → 6034
- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] MCP protocol version: 2025-11-25 → 2026-07-28
- [functional] Server version: 1.0.0 → 1.3.0
- [functional] New tool “list_orders”
- [functional] New tool “list_saved_domains”
- [functional] New tool “save_domain”
- [functional] New tool “save_products”
- [functional] New tool “set_up_store”

### 2026-11-15 (score 67, +1)

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

### 2026-11-13 (score 66, +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.

### 2026-11-11 (score 65, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_plans” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “search_domains”

### 2026-11-10 (score 64)

First indexed and scored.

## MCP tools (29)

### `publish_website` (~1342 tokens)

Publish website

Publish a website to a live public URL on GearHost in seconds (no account). For when the user has you build a website, landing page, portfolio, or HTML/CSS/JS app and wants to see it live or share a link. Provide ONE of: html (a one-page site), files (a map of relative path => text contents), or zip_base64. Pass token to update a site you published before (same URL). Optionally pass name to request a specific subdomain (e.g. name:"daily-grind" → daily-grind.gearhost.io); omit it for an auto-generated fun-name. Pair name with project_key (a secret you generate and STORE) for a PERSISTENT handle: re-publishing the same name + project_key in any future session updates that same URL, even after the token is gone. config applies serving behavior. Supported today: spa (serve index.html for any unmatched route — REQUIRED for client-side-routed apps like React/Vue so deep links + refresh work) and not_found. Unsupported config keys (e.g. redirects, headers) are rejected with bad_request. The response echoes config_applied with EXACTLY what took effect — read it to confirm what was honored instead of assuming. To verify SPA end-to-end, fetch any non-existent deep path and confirm it returns 200 with your index page, not 404. The published site is served at https://<name>.gearhost.io. This tool does the whole publish; static sites can have a working contact form by posting it to https://octane.gearhost.com/forms/ (get_publish_info has the exact markup; messages are emailed to the owner once the site is kept). octane.gearhost.com/preview/ in the docs is the equivalent raw HTTP API for non-MCP clients. Returns structuredContent { status, url, name, token, token_is_secret, updated, url_ready_in_seconds, verify_with, expires_at, claim }. live_now:true means the URL works right away (most publishes, and every update). If live_now is false the address is brand new and its DNS can take ~10s, so do NOT GET it immediately and assume failure; confirm with get_site_status (the verify_w…

Input parameters:

- `config` (object): Optional serving config. Supported today: { "spa": true } — serve index.html for any path that is not a real file (so client-routed React/Vue/SvelteKit apps work on deep links + refresh), and optiona…
- `files` (object): Map of relative path => contents. MUST include "index.html" at the root (served at /). Paths are relative (no leading slash, no ".."). Each value is EITHER a string (text file) OR, for a binary asset…
- `html` (string): HTML for a one-page site (served as index.html at the root).
- `name` (string): Optional subdomain for a NEW site: name:"daily-grind" → daily-grind.gearhost.io. 3-40 chars, lowercase letters/numbers/hyphens, no leading/trailing hyphen. Taken → kind:name_taken; bad format/reserve…
- `note` (string): Optional short label for this version, shown in list_versions (e.g. "added pricing section"). Max 200 chars.
- `notify_url` (string): Optional HTTPS webhook. GearHost POSTs lifecycle events to it as JSON { event, name, url, ... } where event is "expiring_soon" (~6h before auto-removal), "expired" (removed), or "claimed" (the user k…
- `project_key` (string): Optional PERSISTENT HANDLE for cross-session editing without an account. A random secret of AT LEAST 16 characters (shorter is rejected with kind:bad_request) that you generate once and STORE. Best p…
- `source` (string): Optional attribution tag for the builder/app/integration publishing on the user's behalf (e.g. "lovable", "v0", "my-gpt-name"). Shown on the claim page ("published with …"). Free-form, short.
- `token` (string): Manage token from a previous publish - updates the SAME url. Treat as a secret credential.
- `zip_base64` (string): Base64 of a .zip of the built site. MUST contain index.html at the archive root. Max ~25 MB.

Output parameters:

- `claim` (object): How to keep the site permanently (free).
- `config_applied` (object|null): Present only when you sent config — confirms what was actually applied (e.g. {"spa":true,"not_found":"index.html"}). A positive ack: if spa is true here, deep links/refresh serve index.html. Unsuppor…
- `content_hash` (string|null): Stable hash of the published content (timestamp-independent). Re-publishing identical content returns unchanged:true with no redeploy.
- `expires_at` (string|null): When the site auto-expires unless claimed (ISO 8601), or null.
- `live_now` (boolean): True when the URL works right away (a ready-made site, or an update to an existing one). Open or share it immediately.
- `name` (string): The site's fun-name slug (e.g. "fuzzy-gecko").
- `quota` (object|null): Your new-preview budget for the rolling hour, so you can pace yourself instead of hitting rate_limited. { hourly_limit, used_this_hour, remaining, unlimited }.
- `status` (string): "success" on publish.
- `token` (string): Manage token. A WRITE CREDENTIAL - reuse it (as the token arg) to update this same URL. Treat as secret; do not echo in public logs.
- `token_is_secret` (boolean): Always true - a reminder that token must be handled as a credential.
- `unchanged` (boolean): True if the content was identical to the current version — idempotent no-op (no redeploy, version held). The 72h expiry timer IS reset, so re-publishing identical content is a safe "touch to keep ali…
- `updated` (boolean): True if this updated a previously published site (token was supplied) rather than creating a new one.
- `url` (string): Live public URL of the published site.
- `url_ready_in_seconds` (integer|null): Approx seconds before the URL resolves: 0 = live now. Above 0 the address is brand new, and an immediate GET may fail with a DNS/connection error even though the publish SUCCEEDED — wait this long, o…
- `verify` (object): Exact verify cadence: wait poll_after_ms, then call the named tool every poll_every_ms until the `until` condition holds, giving up after give_up_after_ms. Saves you from guessing the DNS delay or ha…
- `verify_with` (string): The tool to call to confirm the site is live (get_site_status) — more reliable than fetching url right after publishing.
- `version` (integer|null): Monotonic version number of this publish (1, 2, 3…). Pass it to rollback_website / see it in list_versions.
- `warnings` (array): Non-blocking quality hints about the published site (e.g. no <title>, http:// mixed-content asset, large size). Fix-then-republish if you want, but the publish DID succeed.

### `get_publish_info` (~75 tokens)

Get publishing guide

Optional: read the GearHost publishing docs (methods, limits ~25 MB and an hourly cap on new sites, 72h lifecycle). The docs describe a raw HTTP API (octane.gearhost.com/preview/) for non-MCP clients - when using MCP you do NOT need it; just call publish_website.

### `get_plans` (~154 tokens)

Get plans and prices

GearHost CloudSite plans and monthly prices in USD, read live from GearHost (the free plan included). Each plan: name, monthly_price_usd, disk_mb, monthly_requests (null = no fixed limit). Every plan, including free, can use custom domains with automatic HTTPS. Add-on prices (email, high availability, databases) are per plan. Plans are changed in the GearHost panel (the CloudSite's "Change plan" link); this tool only reads prices. pricing_model states how billing works: flat monthly prices, no credits or usage charges, and what happens when a site passes its request limit. Returns structuredContent { status, currency, plans:[...], pricing_model, change_plan }.

Output parameters:

- `change_plan` (string)
- `currency` (string)
- `plans` (array)
- `pricing_model` (object)
- `status` (string)

### `unpublish_website` (~132 tokens)

Unpublish website

Take a published site DOWN immediately (delete it). Pass the manage token you got when you published. Use this to remove a site the moment it is no longer needed - or RIGHT AWAY if you accidentally published a secret (sites are public). Without this, a site only auto-expires ~72h after its last publish. Returns structuredContent { status:"deleted", url, deleted:true }. (A site that was CLAIMED into an account is a real CloudSite - delete it from the GearHost dashboard, not here.)

Input parameters:

- `token` (string, required): The manage token returned when the site was published.

Output parameters:

- `deleted` (boolean)
- `status` (string)
- `url` (string)

### `check_site` (~272 tokens)

Check site for problems

Loads a published GearHost site from GearHost's servers and reports problems to fix: missing files and broken links on the site, external scripts/stylesheets that fail to load (e.g. a wrong CDN version), no mobile viewport tag, no <title>, images without alt text, http:// resources on an https page, images over 1 MB, contact forms that send nowhere, and leftover placeholder text (Lorem ipsum, example.com). Pass the site url (or token / name + project_key) and optionally a path. Works for GearHost-hosted sites only. JavaScript is not executed, so runtime script errors are not detected. Each issue has a severity (error, warning, info) and a suggested fix.

Input parameters:

- `name` (string): Alternative to url: site name (pair with project_key).
- `path` (string): Optional page path to check on the site, e.g. "/contact.html". Default: the home page.
- `project_key` (string): The project_key the named site was published with.
- `token` (string): Alternative to url: the manage token returned by publish_website.
- `url` (string): The site or page address, e.g. https://my-site.gearhost.io/ or https://my-site.gearhost.io/about.html.

Output parameters:

- `bytes` (integer)
- `checked` (object)
- `counts` (object)
- `final_url` (string)
- `http_status` (integer|null)
- `issues` (array)
- `ms` (integer): Time to load the page from GearHost, in milliseconds.
- `not_checked` (string)
- `ok` (boolean): true when no error-level issues were found.
- `status` (string)
- `url` (string)

### `get_site_status` (~172 tokens)

Get site status

Full status of a published site — the one call to confirm a publish landed and inspect it. Identify the site by token, OR by name + project_key. Runs a real server-side HTTP probe (live_http) so you get a definitive "is it serving?" answer even while the fresh DNS has not propagated to you yet — prefer this over fetching the URL directly right after publishing. Also returns the current version, content_hash (to detect drift from what you published), size, file_count, source, and the claim/expiry state.

Input parameters:

- `name` (string): Site name (alternative to token; pair with project_key).
- `project_key` (string): The project_key you published the named site with (>=16 chars).
- `token` (string): The manage token returned when the site was published.

Output parameters:

- `claim` (object|null): If unclaimed: how to keep it forever (free) — { time_left, seconds_left, claimable_until, claim_url }. Surface claim_url to the user so they can own the site before it expires.
- `claimed` (boolean)
- `content_hash` (string|null): Hash of the live content — compare to your publish content_hash to confirm the live site matches what you sent.
- `deploy_count` (integer|null)
- `exists` (boolean)
- `expires_at` (string|null)
- `expiring_soon` (boolean): True when unclaimed and < 6h from expiry — prompt the user to claim it NOW so it is not auto-removed.
- `file_count` (integer|null)
- `last_published` (string|null): ISO-8601 time of the most recent deploy.
- `live_http` (object): Server-side HTTP probe of the live URL: { ok, status_code, ms, final_url, error }. ok=true means it is genuinely serving right now.
- `name` (string|null)
- `source` (string|null): The attribution tag it was published with.
- `status` (string)
- `total_bytes` (integer|null): Total uncompressed size of the site.
- `url` (string|null)
- `version` (integer|null): Current published version number.

### `report_abuse` (~64 tokens)

Report abusive site

Report a GearHost preview site being used for phishing/malware/abuse.

Input parameters:

- `name` (string, required): The preview fun-name, e.g. 'azure-lynx'.
- `reason` (string, required): What's wrong with it (phishing, malware, etc.).

### `list_my_previews` (~101 tokens)

List my previews

List the live preview sites you created with a given project_key (your cross-session identity). Reuse one project_key across several named publishes, then call this to enumerate + manage them all. Returns structuredContent { status, count, sites:[{ name, url, expires_at, last_published, claimed }] }.

Input parameters:

- `project_key` (string, required): The secret project_key you published with (>=16 chars). Lists every live preview that shares it.

Output parameters:

- `count` (integer)
- `sites` (array)
- `status` (string)

### `search_domains` (~319 tokens)

Search domain names

Search for domain names: checks with the domain registry which names are available to register, across popular endings (.com, .co, .net, .org, .io, .app by default), and adds available ideas suggested by the registry. Pass the user's words in query (a business name, an idea, or a full domain) and/or your own name ideas in names (e.g. ["harborgrind", "harborgrindcoffee", "drinkharbor.com"]); up to 24 names are checked per search. When GearHost domain registration is open, available names include the yearly price GearHost charges and a buy_url where the user completes the purchase in their GearHost account; no purchase happens through this tool. Status "unknown" means the registry did not answer for that name, not that it is free. No sign-in needed.

Input parameters:

- `names` (array): Optional name ideas to check, with or without an ending (e.g. "harborgrind" or "harborgrind.co"). Names without an ending are tried on every ending in tlds.
- `query` (string): The user's words: a business or project name ("Harbor Grind coffee"), or a full domain to check ("harborgrind.com").
- `tlds` (array): Optional endings to try, e.g. ["com","shop","cafe"]. Default: com, co, net, org, io, app.
- `years` (integer): Registration length for prices, in years (default 1).

Output parameters:

- `available_count` (integer)
- `checked` (integer)
- `note` (string)
- `results` (array)
- `selling` (boolean): true when domains can be bought at GearHost right now (prices and buy_url are included).
- `status` (string)

### `get_domain_setup` (~276 tokens)

Get custom domain setup

Get everything needed to put a custom domain (e.g. yourshop.com) on a GearHost site: the exact DNS records, plus how to attach it. Identify the site by token, or by name+project_key. A custom domain can only be attached to a site in a GearHost account (it binds the domain to a real owner). The steps are: (1) the preview is claimed into a free account (claim_website or claim_url), (2) the domain is attached (attach_custom_domain when signed in, or "Attach Custom Domain" in the GearHost panel), (3) the DNS records are added at the domain's DNS host, (4) get_domain_status reports when it is live. Returns structuredContent { status, domain, claim_first, requires_account, attach_in_dashboard, claim_url, how_to_attach, records:[{ type, host, value, priority, note }], steps }.

Input parameters:

- `domain` (string, required): The custom domain to point here, e.g. "yourshop.com".
- `name` (string): The site name (with project_key) instead of a token.
- `project_key` (string): The project_key (with name) instead of a token.
- `token` (string): The site manage token (or use name+project_key).

Output parameters:

- `attach_in_dashboard` (boolean): Always true — the attach itself is a click in Octane (Attach Custom Domain), not an API call.
- `claim_first` (boolean): True if the site is not yet claimed — it must be claimed to an account before a custom domain can be attached.
- `claim_url` (string|null): Surface this to the user to claim the site (one click if signed in). null if already claimed.
- `domain` (string)
- `how_to_attach` (string): A ready-to-relay walkthrough of the claim → attach → DNS → verify steps.
- `records` (array)
- `requires_account` (boolean): Always true — attaching needs the owner's GearHost account; it is not API-automatable by design.
- `status` (string)
- `steps` (array)

### `get_domain_status` (~227 tokens)

Check custom domain status

Check whether a custom domain is wired up and serving yet — the verify/poll half of the custom-domain flow. After you give the user the DNS records (get_domain_setup) and they attach the domain + add the records, call this to see live progress: is it attached to the CloudSite, does DNS resolve to the GearHost node, and is HTTPS active. Identify the site by token or name+project_key. Poll this every ~30-60s after the user adds DNS until https:"active" — like get_site_status for a publish. Returns structuredContent { status, domain, attached, dns_ok, apex_ok, www_ok, https, live, live_url, next }.

Input parameters:

- `domain` (string, required): The custom domain to check, e.g. "yourshop.com".
- `name` (string): The site name (with project_key) instead of a token.
- `project_key` (string): The project_key (with name) instead of a token.
- `token` (string): The site manage token (or use name+project_key).

Output parameters:

- `apex_ok` (boolean)
- `attach_in_dashboard` (boolean)
- `attached` (boolean): True if the domain is attached to your CloudSite (done in the Octane dashboard via Attach Custom Domain).
- `claim_url` (string|null): If the site is unclaimed, surface this so the user can claim it before attaching. null if already claimed.
- `dns_ok` (boolean): True if DNS for the apex OR www resolves to your GearHost site.
- `domain` (string)
- `https` (string): "active" (serving over HTTPS), "provisioning" (DNS resolves, cert issuing), or "waiting_dns" (records not visible yet).
- `live` (boolean)
- `live_url` (string|null)
- `next` (string): The single next action to get it live.
- `requires_account` (boolean): Always true — if not attached yet, the attach is done in the user's Octane account, not via the API.
- `status` (string)
- `www_ok` (boolean)

### `get_claim_status` (~151 tokens)

Get claim status

Check whether a preview has been claimed into a GearHost account, and how long is left to claim it (the site is auto-removed at expiry unless claimed). Pass token, or name+project_key. Read-only. Returns structuredContent { status, url, claimed, claimable, expiring_soon, seconds_left, time_left, claim_url, owner }. claim_url is the page where the user can keep the site.

Input parameters:

- `name` (string): The site name (with project_key) instead of a token.
- `project_key` (string): The project_key (with name) instead of a token.
- `token` (string): The manage token (or use name+project_key).

Output parameters:

- `claim_url` (string|null): Browser claim link (null once claimed).
- `claimable` (boolean): True if still within the claim window and not yet claimed.
- `claimed` (boolean)
- `expiring_soon` (boolean): True within ~6h of expiry — prompt the user to claim now.
- `owner` (string|null): Masked account once claimed, e.g. "z***@gmail.com".
- `seconds_left` (integer|null)
- `status` (string)
- `time_left` (string|null): Human, e.g. "2d 23h".
- `url` (string)

### `list_versions` (~105 tokens)

List site versions

List the recent publish history for a site (newest first), so you can undo a change. Pass token, or name+project_key. Each publish is a version; use a version number with rollback_website to restore it. Returns structuredContent { status, url, current_version, count, versions:[{ version, published_at, sha, is_current }] }.

Input parameters:

- `name` (string)
- `project_key` (string)
- `token` (string)

Output parameters:

- `count` (integer)
- `current_version` (integer|null)
- `status` (string)
- `url` (string)
- `versions` (array)

### `rollback_website` (~116 tokens)

Roll back website

Restore a site to a previous version (undo). Pass the manage token and the version number from list_versions. Restores that version's content to the live URL and resets the expiry timer. Returns structuredContent { status, url, restored_from, updated, url_ready_in_seconds }. Errors: version_not_found (no such version) | no_versions (nothing to roll back to) | invalid_token.

Input parameters:

- `token` (string, required): Manage token (write credential).
- `version` (integer, required): The version to restore, from list_versions.

Output parameters:

- `restored_from` (integer)
- `status` (string)
- `updated` (boolean)
- `url` (string)
- `url_ready_in_seconds` (integer)

### `list_my_sites` (~45 tokens)

List my sites

Requires signing in to GearHost. List the CloudSites in the user's GearHost account. Returns structuredContent { status, sites:[{domain,url,status,plan,node}] }.

Output parameters:

- `sites` (array)
- `status` (string)

### `list_form_messages` (~197 tokens)

List contact form messages

Requires signing in to GearHost. Lists messages visitors sent through contact forms on the user's CloudSites (GearHost Forms), newest first. Use when the user asks whether anyone contacted them through their site or wants to read form submissions. Optionally limit to one site (domain), to messages since a date, and the number returned (default 20, max 50). Read-only; visitor IP addresses are not included. Returns structuredContent { status, total, messages:[{site, received_at, subject, reply_to, fields}] }.

Input parameters:

- `domain` (string): Only messages from this site (e.g. mysite.gearhost.io or a custom domain on the site). Omit for all sites.
- `limit` (integer): How many messages to return, newest first (1-50, default 20).
- `since` (string): Only messages received on or after this date (YYYY-MM-DD, UTC).

Output parameters:

- `messages` (array)
- `status` (string)
- `total` (integer): Messages matching the filters (may be more than returned).

### `get_site_stats` (~183 tokens)

Get site traffic

Requires signing in to GearHost. Traffic for the user's CloudSites: requests per day for the last 7 or 30 days (successful and not-found), bandwidth, and this billing cycle's requests against the plan's limit. Requests count every page and file served, not unique visitors; the numbers are refreshed about hourly. Use when the user asks how many visits or how much traffic a site gets. Omit domain for all sites. Read-only. Returns structuredContent { status, days, sites:[{domain, requests, ok, not_found, bandwidth_mb, cycle_requests, cycle_limit, daily:[{date, requests}]}] }.

Input parameters:

- `days` (integer): Period in days: 7 or 30 (default 7).
- `domain` (string): One CloudSite (its main address). Omit for all sites in the account.

Output parameters:

- `days` (integer)
- `refreshed_at` (string|null)
- `sites` (array)
- `status` (string)

### `publish_to_my_site` (~175 tokens)

Publish to my site

Requires signing in to GearHost. Publish/update content to a CloudSite ALREADY in the user's GearHost account (by domain). To put a NEW site online, use publish_website instead: it needs no account. Provide ONE of: html, files map (must include index.html at the root), or zip_base64. Returns structuredContent { status, url, domain, files, updated }.

Input parameters:

- `domain` (string, required): The CloudSite domain to publish to (must be in your account).
- `files` (object): Map of relative path => contents. MUST include "index.html" at the root.
- `html` (string): HTML for a one-page site (served as index.html at the root).
- `zip_base64` (string): Base64 .zip with index.html at the archive root.

Output parameters:

- `domain` (string)
- `files` (integer): Number of files deployed.
- `status` (string)
- `updated` (boolean)
- `url` (string)

### `delete_my_site` (~144 tokens)

Delete my site

Requires signing in to GearHost. Delete one of the user's GearHost CloudSites (by domain): its hosting, files, certificates, DNS, HA replicas and Git Push repo, exactly like deleting it in the GearHost panel. Destructive - set confirm:true. Databases linked to the site are KEPT (unlinked, still in the account) unless delete_databases:true. Returns structuredContent { status, domain, deleted, databases }.

Input parameters:

- `confirm` (boolean, required): Must be true to actually delete.
- `delete_databases` (boolean): Also permanently delete the databases linked to this site. Default false: they are kept.
- `domain` (string, required)

Output parameters:

- `databases` (string): kept | deleted | none
- `deleted` (boolean)
- `domain` (string)
- `status` (string)

### `attach_custom_domain` (~194 tokens)

Attach custom domain

Requires signing in to GearHost. Attach a custom domain (e.g. mycoffeeshop.com or www.mycoffeeshop.com) to one of the user's CloudSites, the same as "Attach Custom Domain" in the GearHost panel. Works on every plan, including free. Afterwards the domain's DNS must point at the site: the result lists the exact records to add at the domain's DNS host. HTTPS is issued automatically once DNS resolves; get_domain_status reports progress. Returns structuredContent { status, domain, site, attached, records:[{ type, host, value }], next }.

Input parameters:

- `domain` (string, required): The custom domain to attach, e.g. "mycoffeeshop.com".
- `site` (string, required): The CloudSite to attach to, by its current address (e.g. "glowing-raven.gearhost.io"; list_my_sites shows them).

Output parameters:

- `attached` (boolean)
- `domain` (string)
- `next` (string)
- `records` (array)
- `site` (string)
- `status` (string)

### `save_domain` (~180 tokens)

Save domain for later

Requires signing in to GearHost. Save a domain name to the user's GearHost account to decide on later. It is checked with the domain registry now and every time the saved list is looked at. Saving does NOT register, hold or reserve the name with the registry and costs nothing: anyone can still register it until the user buys it. The user buys it themselves in their GearHost account (Domains). Use when the user likes a name but is not ready to buy, or asks to keep it in mind. Returns structuredContent { status, domain, availability, already_saved, saved_count, where }.

Input parameters:

- `domain` (string, required): The full domain to save, e.g. "harborgrind.com".
- `note` (string): Optional short note shown with it, e.g. "for the coffee shop site". Max 200 chars.

Output parameters:

- `already_saved` (boolean)
- `availability` (string): available, taken or unknown (the registry did not answer; not the same as available).
- `domain` (string)
- `saved_count` (integer)
- `status` (string)
- `where` (string): Where the user sees the saved list.

### `list_saved_domains` (~85 tokens)

List saved domains

Requires signing in to GearHost. The domain names the user saved for later (with save_domain or in the GearHost panel), each re-checked with the registry: available, taken (someone else registered it) or unknown. Read-only; nothing is bought. Returns structuredContent { status, domains:[{domain, availability, note, saved_at, checked_at}] }.

Output parameters:

- `domains` (array)
- `status` (string)

### `claim_website` (~132 tokens)

Claim website to my account

Keep a preview permanently: claims a site made with publish_website into the user's GearHost account, so it becomes a free, permanent CloudSite at the same URL (no 72h expiry). Use when the user wants to keep their site. Requires signing in to GearHost: if they aren't signed in, they are asked to sign in or create a free account. Needs the preview's manage token (from publish_website). Returns structuredContent { status, url, claimed, expires_at, dashboard_url }.

Input parameters:

- `token` (string, required): The manage token of the preview to claim (keep it forever).

Output parameters:

- `claimed` (boolean)
- `dashboard_url` (string)
- `expires_at` (string|null)
- `setup` (string): in_progress while the CloudSite is set up in the background (~2 min; the site keeps serving), then done.
- `status` (string)
- `url` (string)

### `set_up_store` (~157 tokens)

Set up online payments

Requires signing in to GearHost. Let one of the user's CloudSites take payments (GearHost Store): returns a link where the user connects their OWN Stripe account (or creates one) on Stripe's website; buyers then pay on Stripe-hosted pages and the money goes straight to the user. Nothing is charged by this tool. Give the user the link to open themselves. If payments are already on, says so. Then use save_products and add the returned Buy buttons to the site. Returns structuredContent { status, site, payments_ready, connect_url }.

Input parameters:

- `site` (string, required): The CloudSite address (list_my_sites shows them), e.g. "glowing-raven.gearhost.io" or its custom domain.

Output parameters:

- `connect_url` (string|null): Stripe page for the user to open (expires after a few minutes; call again for a new one).
- `payments_ready` (boolean)
- `site` (string)
- `status` (string)

### `save_products` (~211 tokens)

Save store products

Requires signing in to GearHost. Add or update products a CloudSite sells (GearHost Store). Prices are kept by GearHost, not in the page, so visitors cannot change what they pay. Each product: name, price (e.g. 12.5 for 12.50), optional id (used in the Buy button; made from the name if omitted), currency (default the store's), description, shipping (true = ask for a shipping address), active (false = hidden). Returns the products and ready-to-paste Buy button HTML (plain forms posting to https://octane.gearhost.com/checkout/) to put on the site with publish_to_my_site. Works before Stripe is connected; buttons start working once set_up_store is finished. Returns structuredContent { status, site, products:[{id,name,price,currency,shipping,active}], buy_buttons_html, payments_ready }.

Input parameters:

- `products` (array, required)
- `site` (string, required): The CloudSite address.

Output parameters:

- `buy_buttons_html` (string)
- `errors` (array)
- `payments_ready` (boolean)
- `products` (array)
- `site` (string)
- `status` (string)

### `list_orders` (~141 tokens)

List store orders

Requires signing in to GearHost. Paid orders from a CloudSite's GearHost Store, newest first: items, total, buyer name and email, shipping address. Use when the user asks what sold or who to ship to. Read-only; refunds are made in the user's Stripe dashboard. Returns structuredContent { status, site, orders:[{order, total, items, customer_name, customer_email, shipping, paid_at}] }.

Input parameters:

- `limit` (integer): 1-100, default 20.
- `since` (string): Only orders paid on or after this date (YYYY-MM-DD).
- `site` (string, required): The CloudSite address.

Output parameters:

- `orders` (array)
- `site` (string)
- `status` (string)

### `enable_email` (~258 tokens)

Turn on email for a domain

Requires signing in to GearHost. Turn on GearHost email for a custom domain in the user's account (e.g. mycoffeeshop.com), so it can have mailboxes like hello@mycoffeeshop.com. The domain must already be in the account (attach_custom_domain adds one to a site); gearhost.io addresses cannot have email. When the domain's DNS is managed at GearHost (or a Cloudflare zone the user connected), the mail records (MX, SPF, DKIM, DMARC) are added automatically; otherwise the result lists the records to add at the DNS host. If email costs extra on the site's plan, the first call changes nothing and returns needs_confirmation with the monthly charges; tell the user the charge and call again with accept_charges:true ONLY after they agree. Then use create_mailbox. Returns structuredContent { status, domain, dns:{ applied, records:[{type,name,content,priority}] }, settings:{ incoming, outgoing } }.

Input parameters:

- `accept_charges` (boolean): Set true only after the user agreed to the monthly charge a previous call returned.
- `domain` (string, required): The custom domain to receive email, e.g. "mycoffeeshop.com".

Output parameters:

- `charges` (object): Present with needs_confirmation: monthly USD amounts.
- `dns` (object)
- `domain` (string)
- `settings` (object): Mail client settings for every mailbox on the domain.
- `status` (string): success, or needs_confirmation (nothing changed yet).

### `create_mailbox` (~215 tokens)

Create a mailbox

Requires signing in to GearHost. Create a mailbox (e.g. hello@mycoffeeshop.com) on a domain that has GearHost email turned on (enable_email). A strong password is generated and returned once: give it to the user and suggest they change it after signing in to webmail. If each mailbox costs extra on the site's plan, the first call changes nothing and returns needs_confirmation with the monthly charge; call again with accept_charges:true ONLY after the user agrees. Returns structuredContent { status, address, password, webmail, settings:{ incoming, outgoing } }.

Input parameters:

- `accept_charges` (boolean): Set true only after the user agreed to the monthly charge a previous call returned.
- `domain` (string, required): The email domain, e.g. "mycoffeeshop.com".
- `username` (string, required): The part before the @, e.g. "hello" for hello@mycoffeeshop.com. Letters, numbers, dots, hyphens and underscores.

Output parameters:

- `address` (string)
- `charges` (object)
- `password` (string): Shown once. A credential: give it only to the user.
- `settings` (object)
- `status` (string): success, or needs_confirmation (nothing changed yet).
- `webmail` (string)

### `create_database` (~251 tokens)

Create a database

Requires signing in to GearHost. Create a MySQL or SQL Server database in the user's GearHost account (the first 25 MB of each is free; larger sizes are chosen in the GearHost panel). Optionally link it to one of the user's CloudSites: its connection string is then set on the site as an environment variable (default name ConnectionStrings__Default). Returns the connection details once, including the password: they are credentials, so do not publish them in a site's public files. Returns structuredContent { status, name, engine, host, port, database, user, password, connection_string, linked_site, env_var }.

Input parameters:

- `engine` (string): mysql (PHP, WordPress, Node, Python) or sqlserver (.NET). Default mysql.
- `env_var` (string): Optional environment variable name for the link (default ConnectionStrings__Default).
- `name` (string, required): Database name: letters, numbers, hyphens and underscores, starting with a letter or number, up to 63 characters (e.g. "shop_orders").
- `site` (string): Optional: a CloudSite address in the account to link the database to (list_my_sites shows them).

Output parameters:

- `connection_string` (string)
- `database` (string)
- `engine` (string)
- `env_var` (string|null)
- `host` (string)
- `linked_site` (string|null)
- `name` (string)
- `note` (string|null)
- `password` (string)
- `port` (integer)
- `status` (string)
- `user` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-gearhost-mcp/mcp#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 68
- 2026-11-17: 67
- 2026-11-16: 67
- 2026-11-15: 67
- 2026-11-14: 66
- 2026-11-13: 66
- 2026-11-12: 65
- 2026-11-11: 65
- 2026-11-10: 64

## Common questions

### What is the GearHost MCP server?

GearHost is an MCP server listed in the public MCP registry as com.gearhost/mcp. Publish a website to a live HTTPS URL in seconds, no account needed. Keep it free on GearHost. This page covers its hosted endpoint (https://mcp.gearhost.com/).

### Is the GearHost MCP server safe to use?

GearHost scores 70 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 GearHost MCP server expose?

GearHost exposes 29 tools: publish_website, get_publish_info, get_plans, unpublish_website, check_site, and 24 more. Their descriptions and schemas cost roughly 6,074 tokens of context every time the server is loaded.

### Does the GearHost MCP server require authentication?

No. We connected to GearHost without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the GearHost MCP server still maintained?

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

### What did VerifyMCP test on the GearHost MCP server?

VerifyMCP ran 14 checks on GearHost, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.gearhost.com/
- Website: https://octane.gearhost.com/preview/integrations/
- Changelog RSS feed: https://verifymcp.io/servers/com-gearhost-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-gearhost-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-gearhost-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-gearhost-mcp/mcp
