Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

NoctHost

REMOTE · MCP.NOCTHOST.COM

Create, list and destroy hourly-billed servers on Vultr, DigitalOcean, Hetzner and Linode.

Available components

+4 this week 84 Trust /100

Last scanned (15 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Cloud Infrastructure

Trust breakdown (7 categories)

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 Security92
Transport & Reachability100
Schema Quality & AI Usability81
  • 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 4246 tokens (~117/item across 36 items; 35 tools + 1 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 Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 85% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 37 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “list_options” rewrote its description, which is the text the model reads security
  • 17 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “list_options” rewrote its description, which is the text the model reads security
  • 15 Nov 26 +1

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

  • 13 Nov 26 0
    • Tool “create_backup” rewrote its description, which is the text the model reads security
    • Tool “create_load_balancer” rewrote its description, which is the text the model reads security
    • Tool “create_server” rewrote its description, which is the text the model reads security
    • Tool “get_account” rewrote its description, which is the text the model reads security
    • Tool “list_apps” rewrote its description, which is the text the model reads security
    • Tool “list_options” rewrote its description, which is the text the model reads security
    • Tool “list_payment_methods” rewrote its description, which is the text the model reads security
    • Tool “reinstall_server” rewrote its description, which is the text the model reads security
    • Tool “reset_root_password” rewrote its description, which is the text the model reads security
    • Tool “server_power” rewrote its description, which is the text the model reads security
    • Tool “support_send” rewrote its description, which is the text the model reads security
    • Tool “top_up” rewrote its description, which is the text the model reads security
    • “list_options” added an optional parameter “gpu_model” cosmetic
    • “list_options” added an optional parameter “min_vram_gb” cosmetic
    • “change_ip” reworded the description of “confirm” cosmetic
    • “change_ip” reworded the description of “id” cosmetic
    • “console_link” reworded the description of “id” cosmetic
    • “create_backup” reworded the description of “server_id” cosmetic
    • “create_server” reworded the description of “app” cosmetic
    • “create_server” reworded the description of “plan” cosmetic
    • “delete_backup” reworded the description of “confirm” cosmetic
    • “destroy_server” reworded the description of “confirm” cosmetic
    • “get_app_password” reworded the description of “id” cosmetic
    • “get_bandwidth” reworded the description of “id” cosmetic
    • “get_server” reworded the description of “id” cosmetic
    • “get_windows_password” reworded the description of “id” cosmetic
    • “quote” reworded the description of “plan” cosmetic
    • “reinstall_server” reworded the description of “confirm” cosmetic
    • “reinstall_server” reworded the description of “id” cosmetic
    • “rename_server” reworded the description of “id” cosmetic
    • “reset_root_password” reworded the description of “id” cosmetic
    • “restore_backup” reworded the description of “backup_id” cosmetic
    • “restore_backup” reworded the description of “confirm” cosmetic
    • “set_rdns” reworded the description of “id” cosmetic
    • “top_up” reworded the description of “method” cosmetic
    • “top_up” reworded the description of “sanctions_confirmed” cosmetic
  • 12 Nov 26 +5
    • Authorization: fail → pass ▲ security
    • First check of Authorization: pass security
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “change_ip”, which the server declares destructive security
    • New tool “delete_backup”, which the server declares destructive security
    • New tool “delete_load_balancer”, which the server declares destructive security
    • New tool “reinstall_server”, which the server declares destructive security
    • Tool “create_server” rewrote its description, which is the text the model reads security
    • Schema quality: 152 → 118 ▲ functional
    • Tool coverage: 80% → 85% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • New prompt “get-help-from-support” functional
    • New prompt “pick-a-plan” functional
    • Server version: 1.0.0 → 2.0.0 functional
    • New tool “billing_history” functional
    • New tool “console_link” functional
    • New tool “create_backup” functional
    • New tool “create_load_balancer” functional
    • New tool “get_app_password” functional
    • New tool “get_bandwidth” functional
    • New tool “get_windows_password” functional
    • New tool “list_apps” functional
    • New tool “list_backups” functional
    • New tool “list_deposits” functional
    • New tool “list_invoices” functional
    • New tool “list_load_balancers” functional
    • New tool “list_payment_methods” functional
    • New tool “recommend_plan” functional
    • New tool “rename_server” functional
    • New tool “request_server_limit” functional
    • New tool “reset_root_password” functional
    • New tool “restore_backup” functional
    • New tool “set_load_balancer_backends” functional
    • New tool “set_rdns” functional
    • New tool “support_read” functional
    • New tool “support_send” functional
    • New tool “top_up” functional
    • “create_server” added an optional parameter “app” cosmetic
  • 11 Nov 26 75

    First indexed and scored.

Diagnostics

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 Nov 2026 · Probed https://mcp.nocthost.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=nocthost.com CN=WE1,O=Google Trust Services,C=US 11 Oct 2026 9 Jan 2027 ECDSA 256 ECDSA-SHA256 e94cc218211db4af0eb8b6ab3ce17f05
SANs: nocthost.com, *.nocthost.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.nocthost.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
nocthost.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="NoctHost", resource_metadata="https://mcp.nocthost.com/.well-known/oauth-protected-resource/mcp", scope="read deploy", error_description="Sign in to NoctHost when your app asks, or create an API key at https://nocthost.com/dashboard/profile (Profile, API keys) and send it as Authorization: Bearer nh_..."

Bearer realm="NoctHost", resource_metadata="https://mcp.nocthost.com/.well-known/oauth-protected-resource/mcp", scope="read deploy", error_description="Sign in to NoctHost when your app asks, or create an API key at https://nocthost.com/dashboard/profile (Profile, API keys) and send it as Authorization: Bearer nh_..."

Protected resource metadata

Document https://mcp.nocthost.com/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://mcp.nocthost.com/mcp
Authorisation server https://api.nocthost.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.nocthost.com/mcp Verified 200
http (plaintext) http://mcp.nocthost.com/mcp HTTPS enforced 301 https://mcp.nocthost.com/mcp
MCP tools · 35 exposed · ~3,683 tokens

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 →

Tool Tokens
billing_history ~54

Recent movements of the balance (newest first, up to 50): top-ups, hourly charges, refunds, referral credits, with the balance after each.

NameTypeReqDescription
limitinteger–How many entries, default 20.

No output schema declared.

No examples provided.

change_ip ~134

Moves a server to a new IPv4 address: it is snapshotted and recreated in the same city with the same disk contents, and the old address is released for good. Takes several minutes of downtime. Sets a new random root password, returned once (it stays in the chat history). Needs confirm: true and the server's exact label; without both it only describes what would happen.

NameTypeReqDescription
confirmboolean–true changes the IP; without it the tool only describes what would happen.
idstringyesServer id.
labelstring–The server's exact label, as a second check.

No output schema declared.

No examples provided.

console_link ~74

A fresh web console session for a server (keyboard and screen, works without SSH). Returns a link when the cloud gives one, otherwise the dashboard page where the console opens. The link is a live session: anyone who has it can use the console, so do not share it.

NameTypeReqDescription
idstringyesServer id.

No output schema declared.

No examples provided.

create_backup ~63

Takes a snapshot of a server's whole disk, at no extra charge, kept for 7 days. Works on Vultr cloud servers that are running or stopped. Takes a few minutes; the backup then shows status AVAILABLE.

NameTypeReqDescription
server_idstringyesServer id.

No output schema declared.

No examples provided.

create_load_balancer ~185

Creates a managed load balancer in a city in front of your servers there, $0.0247/hour ($18.00/month), billed per hour from the balance until it is deleted. Spends money. Backends are ACTIVE vultr or hetzner servers in that city, all on one cloud. Refused with the price if it is above max_hourly_usd (default $1).

NameTypeReqDescription
algorithmstring––
backend_server_idsarray–Server ids to balance across; can be added later.
forwarding_rulesarrayyesE.g. [{"frontend_protocol":"HTTP","frontend_port":80,"backend_protocol":"HTTP","backend_port":80}].
labelstringyes–
max_hourly_usdnumber––
regionstringyesCity id or name, e.g. "fra".

No output schema declared.

No examples provided.

create_server ~380

Creates 1 to 10 servers (default limit 3 per call) and waits up to about two minutes for ACTIVE, then returns ids, IPv4 and the SSH command. Spends money: billed per hour from the balance until the server is destroyed. Refused with the price if the total hourly price is above max_hourly_usd (default $1); more than 3 servers also need an explicit max_hourly_usd. Without ssh_public_key a random root password is generated and returned once, and it stays in the chat history. app installs a one-click app (Docker, WireGuard, WordPress and others) on Ubuntu 24.04 instead of a plain OS.

NameTypeReqDescription
appstring–One-click app id, e.g. "docker" or "wireguard". Replaces os; the app installs on first boot.
countinteger–How many identical servers, default 1.
labelstring–Server name: Latin letters, digits, dot, dash, underscore. With count > 1 it gets -1, -2, ...
max_hourly_usdnumber–Upper bound for the total hourly price of this call, default 1.
osstring–OS id or name, default "ubuntu-24.04". Ignored for GPU plans.
planstringyesPlan id, e.g. "vc2-1c-1gb", or a plan name like "Micro".
providerstring–Cloud; default is the cheapest that deploys this plan in this city.
regionstringyesCity id or name, e.g. "fra" or "Frankfurt".
ssh_public_keystring–One public key line (ssh-ed25519 ..., ssh-rsa ...), installed for root.

No output schema declared.

No examples provided.

delete_backup ~77

Permanently deletes a backup. Needs confirm: true and the backup's exact label; without both it only describes what would be deleted.

NameTypeReqDescription
backup_idstringyes–
confirmboolean–true deletes the backup; without it nothing is deleted.
labelstring–The backup's exact label, as a second check.

No output schema declared.

No examples provided.

delete_load_balancer ~90

Deletes a load balancer and its public IP; the servers behind it keep running. Billing for it stops in the hour it is deleted. Needs confirm: true and the exact label; without both it only describes what would be deleted.

NameTypeReqDescription
confirmboolean––
idstringyes–
labelstring–The load balancer's exact label, as a second check.

No output schema declared.

No examples provided.

destroy_server ~90

Permanently deletes a server and its disk; billing stops in the hour it is destroyed. Needs confirm: true and the server's exact label. Without both it only describes what would be destroyed.

NameTypeReqDescription
confirmboolean–true destroys the server; without it nothing is destroyed.
idstringyesServer id.
labelstring–The server's exact label, as a second check.

No output schema declared.

No examples provided.

get_account ~36

Balance in USD, current hourly spend, how long the balance lasts at that rate, and how many servers the account runs and may run.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_app_password ~61

Returns the admin login and password of a one-click app (for example WordPress or BTCPay) once it has finished installing. Secret: it stays in the chat history, so change it in the app.

NameTypeReqDescription
idstringyesServer id.

No output schema declared.

No examples provided.

get_bandwidth ~50

Outbound traffic a server used in the current billing period against the traffic its plan includes, in GB. Tracked for Vultr and Hetzner servers.

NameTypeReqDescription
idstringyesServer id.

No output schema declared.

No examples provided.

get_server ~64

One server by id: status (PROVISIONING, ACTIVE, STOPPED, ERROR and so on), IPv4, SSH command, plan, city, cloud and hourly price. Use it to follow a server that was still provisioning.

NameTypeReqDescription
idstringyesServer id.

No output schema declared.

No examples provided.

get_windows_password ~49

Returns the Administrator password of a Windows server for RDP. Secret: it stays in the chat history, so change it inside Windows after you log in.

NameTypeReqDescription
idstringyesServer id.

No output schema declared.

No examples provided.

list_apps ~57

One-click apps this account can deploy as the app of a new server: id, name, what it is, the minimum RAM and disk, and the clouds it deploys on. Each installs on Ubuntu 24.04 on first boot.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_backups ~70

Backups (disk snapshots) on the account, or of one server: id, label, status (PENDING, AVAILABLE, ERROR), city, cloud, size, when it was taken and until when it is kept (7 days).

NameTypeReqDescription
server_idstring–Only backups of this server.

No output schema declared.

No examples provided.

list_deposits ~50

Recent top-ups (open and credited, up to 20): amount to pay, amount credited, method, status (PENDING, CREDITED), payment link of open ones and when they expire.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_invoices ~46

Invoices issued for credited crypto top-ups: number, date and amount. The documents open from the Profile page of the dashboard (card payments get a receipt from the card processor instead).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_load_balancers ~38

Load balancers on the account: id, label, status, city, public IPv4, forwarding rules, backend servers and hourly price.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_options ~375

What can be deployed right now: sizes (shared vCPU, dedicated CPU, NVIDIA GPU, bare metal) with vCPU, RAM, disk, included traffic, hourly and monthly price in USD, and the clouds (Hetzner, Vultr, DigitalOcean, Linode and OVHcloud, plus bare metal on Cherry Servers) and city ids each one deploys in. Sorted by hourly price. Filter by city, country or continent, cloud, kind, GPU model and minimum VRAM, minimum vCPU/RAM/disk and maximum hourly price. GPU sizes carry gpu_model, gpu_count and vram_gb fields. Paginated; also returns the OS images.

NameTypeReqDescription
gpuboolean–true = only GPU servers, false = no GPU servers.
gpu_modelstring–NVIDIA GPU model, e.g. "L40S", "A16", "RTX 4000 Ada", "H100". Implies GPU servers only.
kindstring–vps = shared vCPU, dedicated = dedicated CPU cores, gpu = NVIDIA GPU, metal = bare metal.
limitinteger–Sizes per page, default 15.
max_hourly_usdnumber–Only sizes at or below this price per hour in some city.
min_disk_gbnumber––
min_ram_gbnumber––
min_vcpuinteger––
min_vram_gbnumber–Minimum total GPU memory in GB. Implies GPU servers only.
offsetinteger–Skip this many sizes (from next_offset).
providerstring–Only this cloud.
regionstring–City id or name ("fra", "Frankfurt"), country ("Germany", "US") or continent ("Europe").

No output schema declared.

No examples provided.

list_payment_methods ~42

How the balance can be topped up: crypto coins and networks (with their method codes) and the minimum amount for each, and card if offered to this account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_servers ~44

Servers on the account (everything not destroyed): id, label, status, cloud, city, plan, IPv4, hourly price and a ready SSH command for running Linux servers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

quote ~190

Price of a specific order: plan in a city (and optionally cloud, OS, count, hours). Returns the hourly price per server and in total, the cost for the given hours, the monthly price, and whether the current balance covers the first hour. Without a cloud it picks the cheapest one that deploys there. Does not create anything.

NameTypeReqDescription
countinteger–Number of servers, default 1.
hoursnumber–How long they run, default 1 hour.
osstring–OS id or name, default "ubuntu-24.04". Windows changes the price.
planstringyesPlan id, e.g. "vc2-1c-1gb", or a plan name like "Micro".
providerstring––
regionstringyesCity id or name, e.g. "fra" or "Frankfurt".

No output schema declared.

No examples provided.

recommend_plan ~295

Picks the cheapest sizes that fit a workload, across clouds and cities, from what can be deployed now. Describe the workload (e.g. "Minecraft for 12 players", "Llama 3.1 8B with Ollama", "WireGuard VPN for 5 people") and add numbers when known. Returns fitting options with hourly and monthly price, the sizing basis, and for cheaper sizes that do not fit, one line why. Sizing comes from NoctHost's published guides. Does not create anything.

NameTypeReqDescription
citystring–City, country or continent, e.g. "Frankfurt", "Germany", "Europe".
limitinteger–How many fitting options, default 5.
max_hourly_usdnumber–Budget per server per hour, USD.
model_size_bnumber–LLM size in billions of parameters, e.g. 8 for an 8B model (4-bit quantized).
monthly_traffic_gbnumber–Expected outbound traffic per month, GB.
need_gpuboolean–Only NVIDIA GPU servers.
need_windowsboolean–Windows Server instead of Linux (its own price, at least 4 GB RAM).
usersinteger–Players, VPN users, streams or services, depending on the workload.
workloadstringyesWhat the server is for, in plain words.

No output schema declared.

No examples provided.

reinstall_server ~149

Reinstalls the server's OS in place: the disk is ERASED, the IP stays. Needs confirm: true and the server's exact label; without both it only describes what would happen. Linux: pass ssh_public_key; without it a new random root password is returned once and stays in the chat history. Windows gets a new Administrator password. Runs on Vultr servers.

NameTypeReqDescription
confirmboolean–true reinstalls; without it the tool only describes what would happen.
idstringyesServer id.
labelstring–The server's exact label, as a second check.
ssh_public_keystring–Public key line installed for root after the reinstall.

No output schema declared.

No examples provided.

rename_server ~55

Changes a server's label (also renamed at the cloud). Latin letters, digits, dot, dash and underscore, up to 64 characters.

NameTypeReqDescription
idstringyesServer id.
labelstringyesNew label.

No output schema declared.

No examples provided.

request_server_limit ~85

Asks for a higher limit on how many servers the account may run at once. Often approved on the spot depending on the account's top-up history; otherwise the team reviews it. One open request at a time.

NameTypeReqDescription
reasonstring–What the servers are for; helps the review.
requested_limitintegeryesThe new limit (total servers at once).

No output schema declared.

No examples provided.

reset_root_password ~62

Sets a new random root password on a running Linux server, without touching the disk, and returns it once. The password stays in the chat history: log in, add an SSH key and change it. Linux only.

NameTypeReqDescription
idstringyesServer id.

No output schema declared.

No examples provided.

restore_backup ~166

Creates a NEW server from a backup in the backup's city and cloud, billed per hour like any server. Optionally on a bigger plan. Needs confirm: true; without it returns the price. Refused with the price if it costs more than max_hourly_usd (default $1). Sets a new random root password, returned once (it stays in the chat history).

NameTypeReqDescription
backup_idstringyesBackup id.
confirmboolean–true creates the server; without it the tool only returns the price.
max_hourly_usdnumber–Upper bound for the hourly price, default 1.
planstring–Plan id or name to restore onto; default the backup's own plan. The disk must be at least as big.

No output schema declared.

No examples provided.

server_power ~59

reboot, stop (power off) or start a server by id. A stopped server keeps its IP and disk and is still billed per hour while it exists; destroying it ends billing.

NameTypeReqDescription
actionstringyes–
idstringyes–

No output schema declared.

No examples provided.

set_load_balancer_backends ~73

Replaces the set of servers behind a load balancer (pass the full new list; an empty list removes all). Servers must be ACTIVE, in the load balancer's city and on its cloud.

NameTypeReqDescription
backend_server_idsarrayyes–
idstringyesLoad balancer id.

No output schema declared.

No examples provided.

set_rdns ~85

Sets the reverse DNS (PTR) of a server's IPv4 to a hostname, for example mail.example.com. The hostname's A record must already point at the server's IP. Works on Vultr, Linode and Hetzner servers.

NameTypeReqDescription
hostnamestringyesFully qualified hostname, e.g. mail.example.com.
idstringyesServer id.

No output schema declared.

No examples provided.

support_read ~63

The latest messages of this account's own support chat with NoctHost (oldest first): what the user wrote, replies from the support AI assistant and from the team. Marks replies as read.

NameTypeReqDescription
limitinteger–How many recent messages, default 20.

No output schema declared.

No examples provided.

support_send ~95

Sends a message to NoctHost support in this account's own chat, on the user's behalf; the team sees it marked as sent by an AI assistant. At most 5 messages per hour per key. The support AI assistant often replies at once, and the reply comes back in the result; replies from the team arrive later in the same chat.

NameTypeReqDescription
textstringyesThe message, in the user's words where possible.

No output schema declared.

No examples provided.

top_up ~177

Creates a payment request for the balance and returns where to pay: a payment link, or an address with the exact amount and network. Nothing is charged until the user pays it. Without sanctions_confirmed the tool creates nothing and returns the sanctions statement that the user confirms. method is a coin and network code (for example usdttrc20) or card. EU customers may see VAT added on top; the result shows the amount to pay.

NameTypeReqDescription
amount_usdnumberyesAmount to credit, USD. Minimum 5 for USDT and USDC through our own gateway, 20 for other coins and card.
methodstringyesCoin and network code, e.g. "usdttrc20", or "card".
sanctions_confirmedboolean–true when the user has confirmed the sanctions statement.

No output schema declared.

No examples provided.

Install

How do I install the NoctHost MCP server?

NoctHost is a hosted endpoint at https://mcp.nocthost.com/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 · mcp.nocthost.com

# add to Claude Code
claude mcp add --transport http com-nocthost-mcp 'https://mcp.nocthost.com/mcp'
Common questions

What is the NoctHost MCP server?

NoctHost is an MCP server listed in the public MCP registry as com.nocthost/mcp. Create, list and destroy hourly-billed servers on Vultr, DigitalOcean, Hetzner and Linode. This page covers its hosted endpoint (https://mcp.nocthost.com/mcp).

Is the NoctHost MCP server safe to use?

NoctHost scores 84 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 NoctHost MCP server expose?

NoctHost exposes 35 tools: get_account, list_options, quote, list_apps, list_servers, and 30 more. Their descriptions and schemas cost roughly 3,683 tokens of context every time the server is loaded.

Does the NoctHost MCP server require authentication?

Yes. NoctHost asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the NoctHost MCP server still maintained?

NoctHost 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 NoctHost MCP server?

VerifyMCP ran 13 checks on NoctHost, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.