Skip to content

GearHost MCP server

com.gearhost/mcpgearhost.comstreamable-httpv1.2.2Scanned

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

21 tools: 3 can delete or cancel things, 1 do something that can't be undone, 5 change things and 12 only read.

Tools: 3 delete, 1 irreversible, 5 write, 12 read.
  • Reads private data · 2
  • Reads text others write · 6
  • Can send data out · 3
  • 5 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the GearHost MCP server can do

The GearHost MCP server is published by gearhost.com, a domain the MCP Registry verified. It has 21 tools. It can delete or cancel things (3 tools: unpublish_website, publish_to_my_site and delete_my_site), do things that cannot be undone, such as sending, paying or publishing (publish_website) and create or change data (5 tools: check_site, report_abuse, rollback_website, attach_custom_domain and 1 more). 12 tools only read.

2 tools read private data (get_publish_info and list_form_messages); 6 tools bring in text other people can write (publish_website, check_site, get_site_status and 3 more); 3 tools can send data out of your system (publish_website, check_site and publish_to_my_site). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 5 findings (credentials-mention, tool-shadowing and long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 1.2.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

21 tools

Deletes or cancels 3Claude Code: deny
  • delete_my_siteRequires signing in to GearHost.No findings

    Why it is in this group

    • The name "delete_my_site" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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 }.

    Annotations the server declares

    • title: Delete my site
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • publish_to_my_siteRequires signing in to GearHost.Can send data outNo findings

    Why it is in this group

    • The name "publish_to_my_site" says "publish": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "publish_to_my_site" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    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 }.

    Annotations the server declares

    • title: Publish to my site
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • unpublish_websiteTake a published site DOWN immediately (delete it).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.)

    Annotations the server declares

    • title: Unpublish website
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Can't be undone 1Claude Code: ask
  • publish_websitePublish a website to a live public URL on GearHost in seconds (no account).Reads text others writeCan send data out4 findings

    Why it is in this group

    • The name "publish_website" says "publish": a word for a change that another call does not undo.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "publish_website" says "publish": it sends or publishes something to other people.

    Findings

    • Info

      The description mentions "CREDENTIAL".

      Matched text

      description: "...te files. The returned token is a WRITE CREDENTIAL - keep it private."

      What this check looks for
    • Info

      The input schema at properties.token.description mentions "credential".

      Matched text

      inputSchema.properties.token.description: "...updates the SAME url. Treat as a secret credential."

      What this check looks for
    • Warn

      The description names a tool "verify_with" that this server does not list.

      Matched text

      description: "...lure; confirm with get_site_status (the verify_with tool) instead. On FAILURE: isError=true + st..."

      What this check looks for
    • Info

      The description is 2,913 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ets or private files. The returned token is a WRITE CREDENTIAL - keep it private."

      What this check looks for
    Description, as the server wrote it
    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_with tool) instead. On FAILURE: isError=true + structuredContent { status:"error", error, kind }. kind drives recovery: invalid_token (your update token is stale - retry WITHOUT token to publish a fresh site) | expired (preview hit max lifetime - claim it to keep editing) | rate_limited (back off - there is an hourly limit on NEW sites; the quota field in every publish response shows what is left) | too_large (>25 MB - shrink) | name_taken (the requested name is in use - pick another or omit name) | name_invalid (bad name - 3-40 chars, lowercase letters/numbers/hyphens) | forbidden (that name is managed with a different project_key - you cannot update it) | unavailable (publishing off / service down - retry later) | bad_request (fix the input) | publish_failed (transient - retryable). Content is PUBLIC - never include secrets or private files. The returned token is a WRITE CREDENTIAL - keep it private.

    Annotations the server declares

    • title: Publish website
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 5Claude Code: ask
  • attach_custom_domainRequires signing in to GearHost.No findings

    Why it is in this group

    • The name "attach_custom_domain" says "attach": a word for a change.
    Description, as the server wrote it
    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 }.

    Annotations the server declares

    • title: Attach custom domain
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_siteLoads 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…Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check site for problems
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • claim_websiteKeep 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).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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 }.

    Annotations the server declares

    • title: Claim website to my account
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • report_abuseReport a GearHost preview site being used for phishing/malware/abuse.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Report a GearHost preview site being used for phishing/malware/abuse.

    Annotations the server declares

    • title: Report abusive site
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • rollback_websiteRestore a site to a previous version (undo).1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The input schema at properties.token.description mentions "credential".

      Matched text

      inputSchema.properties.token.description: "Manage token (write credential)."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Roll back website
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 12Show 12 read-only tools
  • get_claim_statusCheck 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).No findings

    Why it is in this group

    • The name "get_claim_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get claim status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_domain_setupGet everything needed to put a custom domain (e.g.No findings

    Why it is in this group

    • The name "get_domain_setup" says "get": a word for reading.
    Description, as the server wrote it
    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 }.

    Annotations the server declares

    • title: Get custom domain setup
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_domain_statusCheck whether a custom domain is wired up and serving yet — the verify/poll half of the custom-domain flow.Reads text others writeNo findings

    Why it is in this group

    • The name "get_domain_status" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 }.

    Annotations the server declares

    • title: Check custom domain status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_plansGearHost CloudSite plans and monthly prices in USD, read live from GearHost (the free plan included).No findings

    Why it is in this group

    • The name "get_plans" says "get": a word for reading.
    Description, as the server wrote it
    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 }.

    Annotations the server declares

    • title: Get plans and prices
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_publish_infoOptional: read the GearHost publishing docs (methods, limits ~25 MB and an hourly cap on new sites, 72h lifecycle).Reads private dataNo findings

    Why it is in this group

    • The name "get_publish_info" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "doc": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get publishing guide
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_site_statsRequires signing in to GearHost.No findings

    Why it is in this group

    • The name "get_site_stats" says "get": a word for reading.
    Description, as the server wrote it
    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}]}] }.

    Annotations the server declares

    • title: Get site traffic
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_site_statusFull status of a published site — the one call to confirm a publish landed and inspect it.Reads text others writeNo findings

    Why it is in this group

    • The name "get_site_status" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get site status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • list_form_messagesRequires signing in to GearHost.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_form_messages" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_form_messages" says "list" and "message": it reads messages.
    • untrusted-inputThe name "list_form_messages" says "list" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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}] }.

    Annotations the server declares

    • title: List contact form messages
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_my_previewsList the live preview sites you created with a given project_key (your cross-session identity).No findings

    Why it is in this group

    • The name "list_my_previews" says "list": a word for reading.
    Description, as the server wrote it
    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 }] }.

    Annotations the server declares

    • title: List my previews
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_my_sitesRequires signing in to GearHost.No findings

    Why it is in this group

    • The name "list_my_sites" says "list": a word for reading.
    Description, as the server wrote it
    Requires signing in to GearHost. List the CloudSites in the user's GearHost account. Returns structuredContent { status, sites:[{domain,url,status,plan,node}] }.

    Annotations the server declares

    • title: List my sites
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_versionsList the recent publish history for a site (newest first), so you can undo a change.No findings

    Why it is in this group

    • The name "list_versions" says "list": a word for reading.
    Description, as the server wrote it
    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 }] }.

    Annotations the server declares

    • title: List site versions
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_domainsSearch 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 avail…Reads text others writeNo findings

    Why it is in this group

    • The name "search_domains" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search domain names
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

36 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 private-data tools breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__gearhost__get_publish_info",
      "mcp__gearhost__list_form_messages"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:20 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
12
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.gearhost.com/.well-known/oauth-protected-resource
Authorization servers
https://octane.gearhost.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 12 tools that change things (3 destructive, 1 irreversible, 8 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.gearhost.com/: tools/list returned 26 tools to an anonymous client, including unpublish_website (destructive), publish_to_my_site (destructive), delete_my_site (destructive), publish_website (irreversible), check_site (write) and 7 more

    What this check looks for

Posture changes

  1. Nov 18, 2026
    • Tools that change things, listed without credentials: 9 to 12
    • Client ID metadata documents: no to yes

Findings

Matches of fixed checks, with the text they matched.

1 warn4 info
  • The description names a tool "verify_with" that this server does not list.

    Matched text

    description: "...lure; confirm with get_site_status (the verify_with tool) instead. On FAILURE: isError=true + st..."

    What this check looks for
  • The description mentions "CREDENTIAL".

    Matched text

    description: "...te files. The returned token is a WRITE CREDENTIAL - keep it private."

    What this check looks for
  • The input schema at properties.token.description mentions "credential".

    Matched text

    inputSchema.properties.token.description: "...updates the SAME url. Treat as a secret credential."

    What this check looks for
  • The description is 2,913 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ets or private files. The returned token is a WRITE CREDENTIAL - keep it private."

    What this check looks for
  • The input schema at properties.token.description mentions "credential".

    Matched text

    inputSchema.properties.token.description: "Manage token (write credential)."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 9 -> 12; Client ID metadata documents: no -> yes.View diff
    • Tools that change things, listed without credentials: 9 to 12
    • Client ID metadata documents: no to yes
  2. Tools3 added, 10 changed.+3 added~10 changedView diff

Install

Pinned to version 1.2.2. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__gearhost__get_publish_info",
      "mcp__gearhost__get_plans",
      "mcp__gearhost__get_site_status",
      "mcp__gearhost__list_my_previews",
      "mcp__gearhost__search_domains",
      "mcp__gearhost__get_domain_setup",
      "mcp__gearhost__get_domain_status",
      "mcp__gearhost__get_claim_status",
      "mcp__gearhost__list_versions",
      "mcp__gearhost__list_my_sites",
      "mcp__gearhost__list_form_messages",
      "mcp__gearhost__get_site_stats"
    ],
    "ask": [
      "mcp__gearhost__publish_website",
      "mcp__gearhost__check_site",
      "mcp__gearhost__report_abuse",
      "mcp__gearhost__rollback_website",
      "mcp__gearhost__attach_custom_domain",
      "mcp__gearhost__claim_website"
    ],
    "deny": [
      "mcp__gearhost__unpublish_website",
      "mcp__gearhost__publish_to_my_site",
      "mcp__gearhost__delete_my_site"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as gearhost. Review it before you use it.

Capability tags behind 8 rules
  • mcp__gearhost__publish_website untrusted-input, outbound
  • mcp__gearhost__get_publish_info private-data
  • mcp__gearhost__check_site untrusted-input, outbound
  • mcp__gearhost__get_site_status untrusted-input
  • mcp__gearhost__search_domains untrusted-input
  • mcp__gearhost__get_domain_status untrusted-input
  • mcp__gearhost__list_form_messages private-data, untrusted-input
  • mcp__gearhost__publish_to_my_site outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.gearhost/mcp/verify?hash=d00aef256db597fa30f145a569b87b9dea3f4401d802d54e5c592e67d2282ee2" | jq -e '.changed == false'

Pinned hash d00aef256db5, from Nov 14, 2026, 04:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.gearhost/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.gearhost/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.gearhost/mcp.svg)](https://radar.anlyon.com/servers/com.gearhost/mcp)

Source: MCP Registry. Synced Nov 14, 2026, 05:17 UTC.

GearHost MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the GearHost MCP server safe?

No scan can promise that. What its definitions show: 21 tools, 9 of which can change, send or delete something, and 5 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the GearHost MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: unpublish_website, publish_to_my_site and delete_my_site.

Can the GearHost MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: publish_website.

What tools does the GearHost MCP server have?

21 tools: 3 destructive, 1 irreversible, 5 write, 12 read. unpublish_website, publish_to_my_site, delete_my_site, publish_website, check_site, report_abuse, rollback_website, attach_custom_domain and 13 more.

Does the GearHost MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the GearHost MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): publish_website, check_site and publish_to_my_site.

Has the GearHost MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.