BorealHost
REMOTE · BOREALHOST.AI · 2 COMPONENTS · SCANNED SEP 21
Agent-native web hosting — deploy sites, manage DNS, register domains, scale infrastructure
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 184 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 27636 tokens (~146/item across 189 items; 184 tools + 5 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management99
- Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 41 additions. See how to fix → Fail
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 27 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_snapshot" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 186 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the BorealHost MCP server?
BorealHost is a hosted endpoint at https://borealhost.ai/mcp/, 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.
remote · borealhost.ai
claude mcp add --transport http ai-borealhost-mcp 'https://borealhost.ai/mcp/'
{
"mcpServers": {
"ai-borealhost-mcp": {
"url": "https://borealhost.ai/mcp/"
}
}
} {
"servers": {
"ai-borealhost-mcp": {
"type": "http",
"url": "https://borealhost.ai/mcp/"
}
}
} [mcp_servers.ai-borealhost-mcp] url = "https://borealhost.ai/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-borealhost-mcp": {
"type": "remote",
"url": "https://borealhost.ai/mcp/",
"enabled": true
}
}
} openclaw mcp add ai-borealhost-mcp --url 'https://borealhost.ai/mcp/' --transport streamable-http
mcp_servers:
ai-borealhost-mcp:
url: "https://borealhost.ai/mcp/" {
"McpServers": {
"ai-borealhost-mcp": {
"Transport": "http",
"Url": "https://borealhost.ai/mcp/"
}
}
} assistant mcp add ai-borealhost-mcp -t streamable-http -u 'https://borealhost.ai/mcp/'
{
"mcpServers": {
"ai-borealhost-mcp": {
"type": "http",
"url": "https://borealhost.ai/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 0
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.27.0 ▼ security
- Tool “register” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_domain” rewrote its description, which is the text the model reads security
- Tool “add_domain_dns” rewrote its description, which is the text the model reads security
- Tool “create_api_key” rewrote its description, which is the text the model reads security
- Tool “decommission” rewrote its description, which is the text the model reads security
- Tool “domain_settings” rewrote its description, which is the text the model reads security
- Tool “execute_query” rewrote its description, which is the text the model reads security
- Tool “install_app” rewrote its description, which is the text the model reads security
- Tool “list_domain_dns” rewrote its description, which is the text the model reads security
- Tool “manage_dns” rewrote its description, which is the text the model reads security
- Tool “register_domain” rewrote its description, which is the text the model reads security
- Tool “rotate_key” rewrote its description, which is the text the model reads security
- Tool “set_api_key” rewrote its description, which is the text the model reads security
- Schema quality: 24346 → 27636 ▼ functional
- Schema quality: excellent → good functional
- New tool “add_mailbox_alias” functional
- New tool “add_port_forward” functional
- New tool “browse_backup” functional
- New tool “clear_mailbox_forwarding” functional
- New tool “configure_email_dns” functional
- New tool “create_mailbox_token” functional
- New tool “delete_email_mailbox” functional
- New tool “disable_email_domain” functional
- New tool “enable_email_domain” functional
- New tool “find_address” functional
- New tool “get_database_recovery” functional
- New tool “get_email_domain” functional
- New tool “get_email_webmail_url” functional
- New tool “get_file_recovery” functional
- New tool “get_mailbox” functional
- New tool “list_email_audit” functional
- New tool “list_email_domains” functional
- New tool “list_mailbox_aliases” functional
- New tool “list_mailboxes” functional
- New tool “list_port_forwards” functional
- New tool “logout_mailbox_sessions” functional
- New tool “recover_backup_database” functional
- New tool “recover_backup_files” functional
- New tool “remove_mailbox_alias” functional
- New tool “remove_port_forward” functional
- New tool “resend_registrant_verification” functional
- New tool “reset_email_mailbox_password” functional
- New tool “restore_mailbox” functional
- New tool “rotate_email_key” functional
- New tool “set_mailbox_aliases” functional
- New tool “update_email_domain” functional
- New tool “update_mailbox” functional
- New tool “create_email_mailbox” functional
- “create_api_key” added an optional parameter “email_domains” cosmetic
- “create_api_key” added an optional parameter “expires_at” cosmetic
- “create_api_key” added an optional parameter “ip_allowlist” cosmetic
- “register_domain” added an optional parameter “quote_only” cosmetic
- “register_domain” added an optional parameter “quote_token” cosmetic
- “register_domain” added an optional parameter “whois_privacy” cosmetic
- “rotate_key” added an optional parameter “grace_minutes” cosmetic
- “add_domain_dns” dropped the optional parameter “ttl” cosmetic
- “manage_dns” dropped the optional parameter “ttl” cosmetic
- 4 Sept 26 0
- Stability: fail → pass ▲ security
- 29 Aug 26 0
- Tool “complete_checkout” rewrote its description, which is the text the model reads security
- Tool “list_plans” rewrote its description, which is the text the model reads security
- Tool “request_api_key” rewrote its description, which is the text the model reads security
- Tool “update_checkout” rewrote its description, which is the text the model reads security
- Tool “claim_api_key” rewrote its description, which is the text the model reads security
- New tool “add_site” functional
- New tool “get_wallet” functional
- New tool “set_site_type” functional
- “update_checkout” added an optional parameter “site_type” cosmetic
- 26 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_checkout” rewrote its description, which is the text the model reads security
- Tool “get_checkout_status” rewrote its description, which is the text the model reads security
- Tool “complete_checkout” rewrote its description, which is the text the model reads security
- Tool “link_domain” rewrote its description, which is the text the model reads security
- New tool “cancel_checkout” functional
- New tool “delete_subdomain” functional
- New tool “list_checkouts” functional
- New tool “set_site_nginx_snippet” functional
- New tool “get_site_nginx_snippet” functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 5 Aug 26 0
- Stability: 0.30 → fail ▼ security
- A breaking change shipped without a version bump: still 1.27.0 ▼ security
- Tool “deploy” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 18211 → 21134 ▼ functional
- New tool “get_support_ticket” functional
- New tool “get_webmail_url” functional
- New tool “list_db_users” functional
- New tool “list_redirects” functional
- New tool “list_subdomains” functional
- New tool “list_support_tickets” functional
- New tool “create_mailbox” functional
- New tool “manage_db_user” functional
- New tool “reply_support_ticket” functional
- New tool “reset_mailbox_password” functional
- New tool “revoke_smtp_relay” functional
- New tool “set_backup_retention” functional
- New tool “set_force_https” functional
- New tool “setup_email” functional
- New tool “test_webhook” functional
- New tool “transfer_out_domain” functional
- New tool “upload_ssl_cert” functional
- New tool “list_webhooks” functional
- New tool “create_support_ticket” functional
- New tool “create_webhook” functional
- New tool “delete_backup” functional
- New tool “delete_mailbox” functional
- New tool “delete_redirect” functional
- New tool “delete_webhook” functional
- New tool “enable_smtp_relay” functional
- New tool “enable_wildcard” functional
- New tool “get_backup_retention” functional
- New tool “get_email_status” functional
- New tool “get_smtp_relay” functional
- New tool “container_action” functional
- New tool “add_subdomain” functional
- New tool “add_redirect” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://borealhost.ai/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=borealhost.ai | CN=YE1,O=Let's Encrypt,C=US | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5bc108d01b5e6db29a7f7c52e60fd4f2090 |
| SANs: *.borealhost.ai, borealhost.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of borealhost.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| borealhost.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; script-src 'self' https://challenges.cloudflare.com 'unsafe-inline' 'unsafe-eval' https://esm.sh https://js.stripe.com https://unpkg.com https://cdn.jsdelivr.net https://cdnjs.cloudflare.com https://www.googletagmanager.com https://connect.facebook.net https://static.cloudflareinsights.com https://www.googleadservices.com https://www.google.com https://googleads.g.doubleclick.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdn.jsdelivr.net https://cdnjs.cloudflare.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https://www.facebook.com https://www.googletagmanager.com https://pagead2.googlesyndication.com https://www.google.com https://googleads.g.doubleclick.net https://www.google.ca https://www.google-analytics.com; connect-src 'self' https://esm.sh https://www.google-analytics.com https://analytics.google.com https://www.googletagmanager.com https://googleads.g.doubleclick.net https://td.doubleclick.net https://www.facebook.com https://con |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://borealhost.ai/mcp/ | Verified | 200 | |
| http (plaintext) | http://borealhost.ai/mcp/ | HTTPS enforced | 301 | https://borealhost.ai/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
rotate_email_key ~31
Rotate the current email-only key with overlap, preserving scope and expiry.
| Name | Type | Req | Description |
|---|---|---|---|
| grace_minutes | integer | – | – |
No output schema declared.
No examples provided.
rotate_key ~163
Rotate an API key, optionally keeping the old key valid for up to 1,440 minutes. Creates a new key with the same name, scopes, and rate limits. The new key is returned once — store it immediately. Requires: API key with write scope. Args: key_id: UUID of the API key to rotate (get from whoami()) Returns: {"api_key": "bh_...", "key_id": "uuid", "prefix": "bh_...", "scopes": ["read", "write"], "message": "Key rotated. Store securely."} Expiry and all restrictions are preserved. Without a grace period the old key stops working immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| grace_minutes | integer | – | – |
| key_id | string | yes | – |
No output schema declared.
No examples provided.
run_malware_scan ~180
Run a ClamAV malware scan on a site's container. Scans the web root (or specified path) for malware, viruses, and trojans. ClamAV is installed automatically if not present. Excludes node_modules, vendor, .git, and cache directories. May take up to 5 minutes for large sites. Requires: API key with write scope. Args: slug: Site identifier path: Directory to scan (default: /var/www/html) Returns: {"infected_files": [{"path": "/var/www/html/shell.php", "threat": "Php.Malware.Agent"}], "scanned_count": 1234, "infected_count": 1, "scan_time_s": 45.2}
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
scale ~146
Change a site's hosting plan (upgrade or downgrade). Requires: API key with admin scope. Best practice: create a snapshot before downgrading. Args: slug: Site identifier new_plan: Target plan slug (e.g. "site_pro", "site_managed"). Call list_plans() to see available plans. Returns: {"success": true, "old_plan": "site_starter", "new_plan": "site_pro", "message": "Plan changed successfully"} Errors: NOT_FOUND: Unknown slug VALIDATION_ERROR: Invalid plan slug or same plan
| Name | Type | Req | Description |
|---|---|---|---|
| new_plan | string | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
schedule_snapshot ~131
Schedule a snapshot for future execution. Requires: API key with write scope. Max 3 pending schedules per site. Args: slug: Site identifier scheduled_at: ISO 8601 datetime (must be in the future) description: Optional description (max 200 chars) Returns: {"id": "uuid", "scheduled_at": "iso8601", "status": "scheduled"} Errors: VALIDATION_ERROR: Invalid datetime, not in future, or too many pending
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| scheduled_at | string | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
search_domain ~124
Check domain availability and get pricing. Requires: API key with read scope. Args: domain: Full domain name (e.g. "example.com", "mybiz.ca") Returns: {"domain": "example.com", "available": true, "registration_estimate_cad": "15.99", "currency": "CAD", "price_cad_includes_privacy": false, "total_cad": null, "quote_required": true} Note: .ca domains require ca_legal_type when registering.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
set_api_key ~116
Set your BorealHost API key for this session. Call this if you already have an API key (from checkout completion, the BorealHost panel, or a container claim). All subsequent tool calls will use this key for authentication. Args: api_key: Your BorealHost API key (format: bh_<48 hex chars>) Returns: {"success": true, "message": "API key set for this session", "key_prefix": "bh_..."}
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
No output schema declared.
No examples provided.
set_backup_retention ~135
Set the backup retention policy for a VPS site. Storage is billed on real stored bytes, so deeper history costs the customer, not the platform. Values are clamped to platform bounds; the response reports what was actually stored. Pass -1 to leave a knob unchanged, or reset=true to restore defaults. Requires: API key with write scope. Returns: {"site", "retention": {...}}
| Name | Type | Req | Description |
|---|---|---|---|
| keep_daily | integer | – | – |
| keep_monthly | integer | – | – |
| keep_weekly | integer | – | – |
| reset | boolean | – | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
set_domain_usage ~461
Set what a registered domain points at — a site, someone else's nameservers, our DNS with no site, or a redirect to another URL. Use this to park a domain, hand it to an external host, or forward it. Switching modes tears down the previous one (a forwarded domain that becomes a site domain loses its redirect, and vice versa). Requires: API key with write scope. Args: domain_name: Full domain name (e.g. "example.com") usage_mode: "site" — link it to a hosted site (needs site_slug); "external_ns" — delegate to the customer's own nameservers (needs nameservers), we stop managing its DNS entirely; "dns_only" — our nameservers, records edited by hand, nothing served; "forward" — our nameservers plus an HTTP redirect to forward_url (needs forward_url) site_slug: Site to link to, when usage_mode="site" nameservers: Ordered list of 2–6 nameserver hostnames, when usage_mode="external_ns" forward_url: Redirect target, when usage_mode="forward" forward_type: "301" permanent (default) or "302" temporary forward_include_path: Append the visitor's path to the target (default: True) Returns: {"domain": "example.com", "usage_mode": "forward", "forward_url": "https://example.org", "configuration": {"dns": true, "nginx": true, "ssl": false, ...}} For forward mode, ssl=false usually just means DNS has not propagated yet — call this tool again a few minutes later to finish the cert. Errors: NOT_FOUND: Domain or site not found VALIDATION_ERROR: Bad nameserver hostname, bad redirect URL, missing site_slug, or a self-referential redirect
| Name | Type | Req | Description |
|---|---|---|---|
| domain_name | string | yes | – |
| forward_include_path | boolean | – | – |
| forward_type | string | – | – |
| forward_url | string | – | – |
| nameservers | array | – | – |
| site_slug | string | – | – |
| usage_mode | string | yes | – |
No output schema declared.
No examples provided.
set_force_https ~60
Enable or disable the HTTP→HTTPS redirect for a site. Requires: API key with write scope. Returns: {"site", "force_https": true|false, "message"}
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
set_mailbox_aliases ~54
Replace the complete alias list idempotently (maximum 2,000).
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | – | – |
| aliases | array | yes | – |
| string | yes | – | |
| reason | string | – | – |
No output schema declared.
No examples provided.
set_site_nginx_snippet ~589
Set custom nginx config on the BorealHost host proxy — WebSocket, timeouts, headers. Use this when configuring your container's own nginx is not enough because something in front of it is interfering. The host proxy sits between the internet and your container, and by default its catch-all `location /` does not do anything special per-site. WEBSOCKETS: if your WebSocket endpoint returns 400 through your domain but upgrades correctly (101) when tested inside your container, the Upgrade header is being dropped in front of you. Add a location block that relays it: location ^~ /your/ws/path/ { proxy_pass <your site's existing upstream>; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_read_timeout 3600; proxy_send_timeout 3600; error_page 502 503 504 =502; } When testing with curl, force HTTP/1.1 (curl --http1.1). A WebSocket handshake uses the Upgrade header, which is invalid in HTTP/2 — curl negotiates h2 with a CDN by default and the edge answers 400, which looks exactly like the bug you are trying to fix. This config lives OUTSIDE the generated vhost, so it survives domain re-linking, autoconfig, plan changes and reprovisioning. Sending "" clears it. Bounds — the file is parsed by a root process on a machine shared with BorealHost infrastructure, so only per-site proxy directives are accepted: location, proxy_pass, proxy_set_header, proxy_http_version, proxy_*_timeout, proxy_buffering, client_max_body_size, add_header, error_page, expires, gzip. `root`, `alias`, `include`, `access_log`, `error_log`, `server` and `upstream` are refused, and proxy_pass must target your own site's existing upstream. A rejection names the directive and why. The config is validated with `nginx -t` before it is applied and rolled back automatically if it does not pass, so a mistake cannot take your site down. Requires: API key with write scope. Args: do…
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| domain_name | string | yes | – |
No output schema declared.
No examples provided.
set_site_type ~368
Change what a site's docroot IS, without deleting anything. Types: wordpress WordPress, PHP and a database (the default) php PHP and a database, no WordPress php-nodb PHP, no database static-site HTML/CSS/JS only, no PHP and no database ⚠ NON-DESTRUCTIVE. Existing files stay on disk and existing databases are not dropped. They remain the customer's data and keep counting against their plan's quota — this changes how the site is SERVED, not what it holds. Converting back later finds everything where it was. ⚠ Moving to a type without PHP does not merely stop executing .php — it stops serving them. The vhost returns 404 for php/phtml, because falling through to the static handler would return the file's SOURCE, and a docroot converted from WordPress still contains wp-config.php with the database password in it. Shared hosting only. On a VPS the whole container is the customer's and they reconfigure it with the tools inside it. Requires: API key with write scope. Args: slug: Site identifier site_type: One of the four values above Returns: {"from": "wordpress", "to": "static-site", "database_created": false, "placeholder_seeded": false, "pool_removed": true} `placeholder_seeded` is true only when the docroot was EMPTY — an existing site's content is never overwritten. Errors: VALIDATION_ERROR: Unknown type, or the site is not on shared hosting NOT_FOUND: Unknown slug or not reachable by this account
| Name | Type | Req | Description |
|---|---|---|---|
| site_type | string | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
setup_email ~115
Enable business email (hosted mailboxes + webmail) on a domain. Creates the hosted-email domain, sets up outbound authentication (DKIM/SPF), and auto-configures MX/SPF DNS when the zone is hosted by BorealHost. Mailboxes are billed per-mailbox on the site subscription. Requires: API key with write scope. Returns: {"configured": true, "domain", "dns_auto_configured", "message"}
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
snapshot_compute_volume ~186
Queue a checkpoint snapshot without detaching — before a risky change. ASYNCHRONOUS. Returns immediately with state "snapshotting"; poll get_compute_volume until it is back to "attached" (done) or "error". Named systemd units are stopped for the capture so the snapshot is application-consistent (a live database directory copied mid-write is not reliably restorable). The worker restarts nothing — reboot or start them yourself afterwards. Requires: API key with write scope. Args: volume_id: A volume in state "attached" quiesce_units: Services to stop during capture, e.g. ["ollama.service", "postgresql.service"] Returns: Volume dict with state "snapshotting". Poll for the outcome.
| Name | Type | Req | Description |
|---|---|---|---|
| quiesce_units | array | – | – |
| volume_id | string | yes | – |
No output schema declared.
No examples provided.
ssl_info ~90
Get SSL certificate information for a site. Returns certificate details, expiry date, and issuer. Requires: API key with read scope. Args: slug: Site identifier Returns: {"issuer": "Let's Encrypt", "domain": "example.com", "expires_at": "iso8601", "days_remaining": 60, "force_https": true}
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
ssl_renew ~58
Force SSL certificate renewal via certbot. Requires: API key with write scope. Args: slug: Site identifier Returns: {"renewed": true, "expires_at": "iso8601"}
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
start_compute_instance ~31
Start a stopped compute instance. Requires: API key with write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | string | yes | – |
No output schema declared.
No examples provided.
stop_compute_instance ~48
Stop a compute instance. WARNING: hourly billing continues while stopped. Use terminate_compute_instance to stop the charges permanently. Requires: API key with write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | string | yes | – |
No output schema declared.
No examples provided.
switch_php ~88
Switch the active PHP version for a site. Requires: API key with write scope. Args: slug: Site identifier version: Target PHP version (e.g. "8.3", "8.2", "8.1") Returns: {"version": "8.3", "result": {...}}
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
| version | string | yes | – |
No output schema declared.
No examples provided.
terminate_compute_instance ~76
Permanently terminate a compute instance — this stops hourly billing. The instance and its disk are destroyed and cannot be recovered. Copy any results off the instance before terminating. Requires: API key with write scope. Returns: Final instance dict with state "terminated" and total accrued_cad.
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | string | yes | – |
No output schema declared.
No examples provided.
test_webhook ~54
Send a test event to a webhook endpoint (async). Poll list_webhooks afterwards for last_status. Requires: API key with write scope. Returns: {"id", "message"}
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_id | string | yes | – |
No output schema declared.
No examples provided.
toggle_module ~150
Enable or disable an AI module on a site. The module must be in the plan's available module list. Requires: API key with write scope. Args: slug: Site identifier module_name: Module to toggle. Available modules: "chatbot" (AI chat widget), "seo" (SEO optimization), "translation" (content translation), "content" (AI content generation) Returns: {"module": "chatbot", "enabled": true, "message": "Module enabled"} Errors: NOT_FOUND: Unknown slug or module not in plan VALIDATION_ERROR: Invalid module name
| Name | Type | Req | Description |
|---|---|---|---|
| module_name | string | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
transfer_out_domain ~98
Prepare a domain to transfer to another registrar. Unlocks the domain and emails the EPP/auth code to the registrant contact on file (BorealHost never sees the code). The domain keeps working here until the transfer completes. Requires: API key with write scope. Returns: {"domain", "unlocked": true, "auth_code_emailed": true, "message"}
| Name | Type | Req | Description |
|---|---|---|---|
| domain_name | string | yes | – |
No output schema declared.
No examples provided.
update_account ~159
Update account profile fields (email, language, name). Requires: API key with write scope. Only provided (non-empty) fields are updated. Args: email: New email address language: Language preference — "fr" (French) or "en" (English) first_name: First name last_name: Last name Returns: {"success": true, "account": {"email": "...", "language": "fr", "first_name": "...", "last_name": "..."}} Errors: VALIDATION_ERROR: Invalid email format or language code
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – | |
| first_name | string | – | – |
| language | string | – | – |
| last_name | string | – | – |
No output schema declared.
No examples provided.
update_checkout ~331
Set buyer email and desired site slug on a checkout session. The checkout must be in "not_ready" status. Setting requested_slug transitions status to "ready" (required before completing). Args: checkout_id: Checkout session ID from create_checkout buyer_email: Optional email — if omitted, a synthetic agent identity (agent-{uuid}@api.borealhost.ai) is created at completion requested_slug: Desired site identifier. Must be 3-50 chars, lowercase alphanumeric + hyphens, cannot start/end with hyphen. Must be globally unique. site_type: What the docroot should serve — wordpress (default), php, php-nodb or static-site. ⚠ Set it HERE: the checkout locks once buyer info is set, so choosing later means provisioning a WordPress you then convert away from, abandoning its tree in the docroot and paying a minute of provisioning for nothing. Returns: {"id": "uuid", "sku": "...", "plan_slug": "...", "billing_period": "monthly", "status": "ready", "buyer_email": "...", "requested_slug": "my-site", "created_at": "iso8601"} Errors: VALIDATION_ERROR: Invalid slug format or slug already taken FORBIDDEN: Missing checkout_secret NOT_FOUND: Unknown checkout_id
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_email | string | – | – |
| checkout_id | string | yes | – |
| requested_slug | string | – | – |
| site_type | string | – | – |
No output schema declared.
No examples provided.
update_email_domain ~56
Set mailbox_limit, alias_limit, quota_gb, smtp_sent_limit, services or language.
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | – | – |
| domain | string | yes | – |
| reason | string | – | – |
| settings | object | yes | – |
No output schema declared.
No examples provided.
update_mailbox ~67
Set display_name, quota_gb, smtp_sent_limit, label, services or suspended. Suspension disables client access and outbound SMTP while preserving receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | – | – |
| string | yes | – | |
| reason | string | – | – |
| settings | object | yes | – |
No output schema declared.
No examples provided.
upload_file ~154
Upload a base64-encoded file to a site's container. Use this for binary files (images, archives, fonts, etc.). For text files, prefer write_file(). Requires: API key with write scope. Args: slug: Site identifier path: Relative path including filename (e.g. "images/logo.png") content_b64: Base64-encoded file content Returns: {"success": true, "path": "images/logo.png", "size": 45678} Errors: VALIDATION_ERROR: Invalid base64 encoding FORBIDDEN: Protected system path
| Name | Type | Req | Description |
|---|---|---|---|
| content_b64 | string | yes | – |
| path | string | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
upload_ssl_cert ~137
Install your own SSL certificate for a site's domain. The certificate must be a PEM fullchain (leaf + intermediates) and the key unencrypted PEM. Validated (parse, key match, domain coverage, expiry) before nginx is touched; nginx config is tested before reload. Requires: API key with write scope. Returns: {"site", "domain", "server_names", "installed": true, "ssl_active": true, "not_after"}
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| fullchain_pem | string | yes | – |
| privkey_pem | string | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
whoami ~137
Check the current API key's account info, scopes, and site count. Requires: BOREALHOST_API_KEY env var (read scope). Returns: {"user": {"id": "uuid", "email": "...", "date_joined": "iso8601"}, "api_key": {"id": "uuid", "name": "...", "prefix": "bh_...", "scopes": ["read", "write"], "created_at": "iso8601"}, "account": {"sites": 2, "active_subscriptions": 1}} Errors: UNAUTHORIZED: Missing or invalid API key
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wp_check_updates ~99
Check for available WordPress core, plugin, and theme updates. Requires: API key with read scope. Args: slug: Site identifier Returns: {"core": {"current": "6.5", "update": "6.6"}, "plugins": [{"name": "...", "current": "1.0", "new": "1.1"}], "themes": [...]}
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
wp_update_all ~76
Update WordPress core, all plugins, and all themes. Runs all updates in sequence. May take up to 2 minutes. Requires: API key with write scope. Args: slug: Site identifier Returns: {"core": {...}, "plugins": [...], "themes": [...]}
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
write_file ~123
Write or overwrite a text file in a site's container. Creates parent directories if they don't exist. Requires: API key with write scope. Args: slug: Site identifier path: Relative path to the file content: File content as a UTF-8 string Returns: {"success": true, "path": "...", "size": 1234} Errors: NOT_FOUND: Unknown slug FORBIDDEN: Protected system path
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| path | string | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
What is the BorealHost MCP server?
BorealHost is an MCP server listed in the public MCP registry as ai.borealhost/mcp. Agent-native web hosting, deploy sites, manage DNS, register domains, scale infrastructure. This page covers its hosted endpoint (https://borealhost.ai/mcp/).
Is the BorealHost MCP server safe to use?
BorealHost scores 75 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 BorealHost MCP server expose?
BorealHost exposes 184 tools: set_api_key, whoami, request_api_key, claim_api_key, list_plans, and 179 more. Their descriptions and schemas cost roughly 25,764 tokens of context every time the server is loaded.
Does the BorealHost MCP server require authentication?
No. We connected to BorealHost without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BorealHost MCP server still maintained?
BorealHost is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.