MCP servers observed by Lowdown
ai.borealhost/mcp MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 184 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; no tool definition change in 2 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.borealhost/mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.borealhost/mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
184 tools on 2026-11-17:
add_cronadd_domain_dnsadd_firewall_ruleadd_mailbox_aliasadd_port_forwardadd_redirectadd_siteadd_ssh_keyadd_subdomainadopt_compute_instanceattach_compute_volumebrowse_backupcache_flushcache_statuscache_togglecancel_checkoutcancel_scheduled_snapshotclaim_api_keyclear_mailbox_forwardingcloudflare_proxy_statuscloudflare_purge_cachecloudflare_set_proxycomplete_checkoutconfigure_email_dnscontainer_actioncreate_alert_rulecreate_api_keycreate_b2_snapshotcreate_backupcreate_checkoutcreate_compute_volumecreate_directorycreate_email_mailboxcreate_ftp_accountcreate_mailboxcreate_mailbox_tokencreate_snapshotcreate_support_ticketcreate_webhookdatabase_search_replacedecommissiondelete_accountdelete_alert_ruledelete_backupdelete_compute_volumedelete_crondelete_domain_dnsdelete_email_mailboxdelete_filedelete_mailboxdelete_redirectdelete_snapshotdelete_subdomaindelete_webhookdetach_compute_volumedisable_email_domaindomain_detaildomain_settingsenable_email_domainenable_smtp_relayenable_wildcardexecute_queryfind_addressget_app_statusget_backup_retentionget_billing_portalget_checkout_statusget_compute_instanceget_compute_volumeget_database_infoget_database_recoveryget_email_domainget_email_statusget_email_webmail_urlget_file_recoveryget_logsget_mailboxget_metricsget_resource_snapshotget_site_nginx_snippetget_site_statusget_smtp_relayget_snapshot_usageget_ssh_infoget_stack_infoget_support_ticketget_walletget_webmail_urlinstall_applaunch_compute_instancelink_domainlist_alert_ruleslist_api_keyslist_appslist_backupslist_checkoutslist_compute_imageslist_compute_instanceslist_compute_typeslist_compute_volumeslist_cronlist_databaseslist_db_userslist_domain_dnslist_domainslist_email_auditlist_email_domainslist_fileslist_firewall_ruleslist_ftp_accountslist_mailbox_aliaseslist_mailboxeslist_moduleslist_php_versionslist_planslist_pluginslist_port_forwardslist_redirectslist_snapshotslist_subdomainslist_subscriptionslist_support_ticketslist_tableslist_themeslist_webhookslogout_mailbox_sessionsmanage_db_usermanage_dnsmanage_pluginmanage_themeoptimize_databaseread_filereboot_compute_instancerecover_backup_databaserecover_backup_filesregister_domainremove_firewall_ruleremove_ftp_accountremove_mailbox_aliasremove_port_forwardreply_support_ticketrequest_api_keyresend_registrant_verificationreset_email_mailbox_passwordreset_mailbox_passwordrestore_backuprestore_mailboxrevoke_api_keyrevoke_smtp_relayrollback_snapshotrotate_email_keyrotate_keyrun_malware_scanscaleschedule_snapshotsearch_domainset_api_keyset_backup_retentionset_domain_usageset_force_httpsset_mailbox_aliasesset_site_nginx_snippetset_site_typesetup_emailsnapshot_compute_volumessl_infossl_renewstart_compute_instancestop_compute_instanceswitch_phpterminate_compute_instancetest_webhooktoggle_moduletransfer_out_domainupdate_accountupdate_checkoutupdate_email_domainupdate_mailboxupload_fileupload_ssl_certwhoamiwp_check_updateswp_update_allwrite_file
MCP Registry declaration
- Registry name:
ai.borealhost/mcp - Declared version: 0.4.2
- Status: active
- Declared hosts:
borealhost.ai
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:ai.borealhost/mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.borealhost/mcp?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:ai.borealhost/mcp -- uvx borealhost-mcp
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).