jethost.com valid

JetHost MCP API

Model Context Protocol server for JetHost MCP hosting accounts. Endpoint: https://mcp.jethost.com/mcp (JSON-RPC over streamable HTTP). Auth: OAuth 2.1 + Dynamic Client Registration + PKCE.

For agents: Model Context Protocol server for managing JetHost hosting accounts; documents OAuth 2.1 auth, scopes, rate limits and service endpoints for agents.

mcp serverweb hostingoauth 2.1hosting services apicpanel

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T17:17:44.008Z. Cached copy · Source on jethost.com

# JetHost MCP API

> Model Context Protocol server for JetHost MCP hosting accounts. Endpoint: https://mcp.jethost.com/mcp (JSON-RPC over streamable HTTP). Auth: OAuth 2.1 + Dynamic Client Registration + PKCE.

> Last updated: 2026-10-15

- [Authentication & registration](https://mcp.jethost.com/docs/authentication.html): how to connect, endpoints, scopes
- [Advanced Token Manager](https://mcp.jethost.com/docs/security.html): opt-in credentials — named, expiring keys scoped per account, service, tool, and cPanel module
- [Rate limits](https://mcp.jethost.com/docs/limits.html): per-connection and per-account request limits, RateLimit-* headers, 429 + Retry-After

## Services

- [list_services](https://mcp.jethost.com/docs/list_services.html): List the caller's active and suspended hosting services. Requires the read:services scope.
- [get_service](https://mcp.jethost.com/docs/get_service.html): Get a single hosting service by ID, including status, billing cycle, disk/bandwidth usage, server, and default nameservers. Requires the read:services scope.
- [get_service_usage](https://mcp.jethost.com/docs/get_service_usage.html): Get CPU usage for one of the caller's hosting services by ID: current, today, and month-to-date CPU-minutes (UTC). Pass month=YYYY-MM to also get a per-day series. Data may be up to ~60s stale. Requires the read:services scope.

## VPS

- [list_vps_operations](https://mcp.jethost.com/docs/list_vps_operations.html): List the VPS operations ONE of the customer's VPS services supports, by service_id (from list_services, where service_kind is "vps" or "managed_vps"). Only the operations that service's plan includes are listed — a Managed VPS is typically limited to details — each with a one-line summary and its parameters (name, type, required, allowed values, pattern, bounds). `listing` is the same menu as text: one line per operation, "name(params)" with optional parameters marked "?", behind a two-character flag column: "!" in the first column means the operation changes the VPS and vps_manage refuses it without confirm:true; "x" in the second means it is not available through the assistant (reinstall and snapshot restore answer "Not implemented, contact support"). `notes` carries the rules to follow. Root credentials and password resets are never available here. A service that is not the customer's, or not a VPS, returns error="not_found"; a suspended or cancelled one returns error="service_not_active". Call this first, then vps_manage. Requires read access to services.
- [vps_manage](https://mcp.jethost.com/docs/vps_manage.html): Run one operation on the customer's own VPS and return { ok, data, errors[], warnings[] }: details and status, power (start, stop, reboot), IPs and reverse DNS, null-routing, firewall rules, traffic, snapshots, rescue ISOs, notification settings and the console. Call list_vps_operations(service_id) first for the operations this VPS supports and their parameters; pass service_id, operation and params (
…

Related sites

Find similar publishers by meaning →

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=jethost.com · GET /v1/domain/jethost.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for jethost.com:
1. POST https://agentwebmap.com/v1/sites/jethost.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://jethost.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/jethost.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/jethost.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.