mcp-registry/ai.borealhost/mcp · v1.27.0
Also listed as glama/alainsvrd/borealhost-mcp-server
As of 2026-10-18 23:16 UTC, the Borealhost MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Agent-native web hosting — deploy sites, manage DNS, register domains, scale infrastructure
Claude Code
claude mcp add --transport http borealhost-mcp-server https://borealhost.ai/mcp/
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"borealhost-mcp-server": {
"type": "http",
"url": "https://borealhost.ai/mcp/"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
184 of 184 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
184 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
435 parameter(s) across 174 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
51 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Loading this server's tool list costs an agent ~31,973 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Handshake + tools/list takes ~1,737 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 1 tool(s) removed and 5 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 174 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.borealhost%2Fmcp/fixes
{
"name": "add_cron",
"description": "Add a cron job to a site.\n\nRequires: API key with write scope.\n\nArgs:\n slug: Site identifier\n schedule: Cron schedule (e.g. \"*/5 * * * *\", \"0 2 * * *\")\n command: Command to execute\n\nReturns:\n {\"added\": true, \"result\": {...}}\n",
"inputSchema": {
"type": "object",
"title": "add_cronArguments",
"required": [
"slug",
"schedule",
"command"
],
"properties": {
"slug": {
"type": "string",
"title": "Slug"
},
"command": {
"type": "string",
"title": "Command"
},
"schedule": {
"type": "string",
"title": "Schedule"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "add_domain_dns",
"description": "Add a DNS record to a domain.\n\nRequires: API key with write scope.\n\nArgs:\n domain_name: Full domain name (e.g. \"example.com\")\n record_type: \"A\", \"AAAA\", \"CNAME\", \"MX\", \"TXT\", or \"SRV\"\n value: Record value (e.g. \"1.2.3.4\" for A, \"mail.example.com\" for MX)\n subdomain: Subdomain part (e.g. \"www\", \"mail\"). Empty for apex domain.\n priority: MX priority (required for MX records)\n\n The DNS provider manages the effective TTL and does not expose a\n per-record value through this servi",
"inputSchema": {
"type": "object",
"title": "add_domain_dnsArguments",
"required": [
"domain_name",
"record_type",
"value"
],
"properties": {
"value": {
"type": "string",
"title": "Value"
},
"priority": {
"type": "integer",
"title": "Priority",
"default": null
},
"subdomain": {
"type": "string",
"title": "Subdomain",
"default": ""
},
"domain_name": {
"type": "string",
"title": "Domain Name"
},
"record_type": {
"type": "string",
"title": "Record Type"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "add_firewall_rule",
"description": "Add an IP firewall rule (allow or deny) and reload Nginx.\n\nSupports IPv4, IPv6, and CIDR notation. Max 100 rules per site.\nIf a rule already exists for the IP, the action is updated.\n\nRequires: API key with write scope.\n\nArgs:\n slug: Site identifier\n ip: IP address or CIDR (e.g. \"1.2.3.4\", \"10.0.0.0/8\", \"2001:db8::/32\")\n action: \"deny\" (block) or \"allow\" (whitelist). Default: \"deny\"\n\nReturns:\n {\"added\": true, \"ip\": \"1.2.3.4\", \"action\": \"deny\"}\n",
"inputSchema": {
"type": "object",
"title": "add_firewall_ruleArguments",
"required": [
"slug",
"ip"
],
"properties": {
"ip": {
"type": "string",
"title": "Ip"
},
"slug": {
"type": "string",
"title": "Slug"
},
"action": {
"type": "string",
"title": "Action",
"default": "deny"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.borealhost/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.borealhost/mcp"}) over MCP.
register_domain ~542 tokenslaunch_compute_instance ~340 tokenscreate_alert_rule ~331 tokenscreate_api_key ~324 tokensset_domain_usage ~322 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fai.borealhost%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.borealhost%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.borealhost%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.borealhost%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fai.borealhost%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:73d030ae884c8ac6…, first seen 2026-10-17, included at leaf 1880 of 23,760. Version history · verify what your client received.
Compare: most reliable devops servers · most reliable database servers · most reliable security servers · most reliable email servers · most reliable web servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 23:16 UTC, the Borealhost MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Borealhost MCP server advertises 184 tools, including add_cron, add_domain_dns, add_firewall_rule, add_mailbox_alias, add_port_forward.
Point your MCP client at this streamable-http endpoint: https://borealhost.ai/mcp/
Glimind scanned all 184 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.