# OrbitFour (remote · www.orbitfour.com)

Check domain availability and live registry pricing, or search for available names.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.orbitfour.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-orbitfour-domains/www.md), [page](https://verifymcp.io/servers/com-orbitfour-domains/www)

## Channel facts

- Endpoint: `https://www.orbitfour.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1232 tokens (~308/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "check_transfer" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the OrbitFour MCP server?

OrbitFour is a hosted endpoint at https://www.orbitfour.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.

### Claude

```bash
claude mcp add --transport http com-orbitfour-domains 'https://www.orbitfour.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-orbitfour-domains": {
      "url": "https://www.orbitfour.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-orbitfour-domains": {
      "type": "http",
      "url": "https://www.orbitfour.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-orbitfour-domains]
url = "https://www.orbitfour.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-orbitfour-domains": {
      "type": "remote",
      "url": "https://www.orbitfour.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-orbitfour-domains --url 'https://www.orbitfour.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-orbitfour-domains:
    url: "https://www.orbitfour.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-orbitfour-domains": {
      "Transport": "http",
      "Url": "https://www.orbitfour.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-orbitfour-domains -t streamable-http -u 'https://www.orbitfour.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-orbitfour-domains": {
      "type": "http",
      "url": "https://www.orbitfour.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 77, +1)

- [security] Tool “get_tld_requirements” rewrote its description, which is the text the model reads

### 2026-11-02 (score 76, +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.

### 2026-10-31 (score 75, +1)

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

### 2026-10-29 (score 74, +1)

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

### 2026-10-27 (score 73, +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.

### 2026-10-25 (score 72, +1)

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

### 2026-10-24 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 71)

First indexed and scored.

## MCP tools (4)

### `check_domain` (~306 tokens)

Check domain availability and price

Look up exact domain names: whether each can be registered now, and its per-year registration, renewal and transfer price in USD, premium names included, from a live registry check. Use it for names you already have and to confirm a search_domains suggestion. Up to 10 names per call; read-only. available is true, false, or null (the registry could not be asked; not the same as taken). An unavailable name says why in reason: taken, reserved, unavailable or unknown. purchasable is false for an available name OrbitFour can't sell now, and for a null one, and purchase_blocker says why. first_term is the shortest term (min_years: .ai is 2) and its total with the ICANN fee. A malformed name or an extension OrbitFour doesn't sell comes back with an error field. pricing_source says where the registration price came from: "registry" is a live quote for that name, "baseline" is the extension's standard rate and final for the name (the extension has no premium names, or the registry quoted none for it), and "unconfirmed" means the registry lookup did not finish, so the price is not final for a name that may be premium. pricing_sources breaks this out per action.

Input parameters:

- `names` (array, required): Domain names to check, e.g. ["example.com", "example.net"]. Max 10.
- `years` (integer): Registration term in years (default 1).

Output parameters:

- `domains` (array)

### `search_domains` (~375 tokens)

Search for available domain names

Find domain names from a free-text idea, brand or phrase; a phrase yields short combinations of its words. top_picks answers "how does my name look": the name as typed (when its extension isn't .com/.net/.org) and the name on .com, .net and .org, or on each extension in tlds, with its real status, taken and unknown included, as check_domain reports it. suggestions are up to `limit` ranked names a live check found available, never repeating a top pick, with per-year prices in USD, premium names included unless include_premium is false; match is exact_sld or variation, and hack is true for a domain hack such as danger.zone. unchecked_names lists names whose check came back unknown, left_out counts why other names checked aren't suggested, and with tlds, each extension says why it found nothing. Search is advisory: confirm the chosen name with check_domain before quoting it, and a purchase checks again. Read-only, no side effects.

Input parameters:

- `include_premium` (boolean): false leaves premium names out of the suggestions (default true).
- `limit` (integer): Target number of suggestions (default 10).
- `max_price` (string): Leave out suggestions whose first_term.total, the first term's price with the ICANN fee (what buying it costs), is above this USD amount, e.g. "25.00".
- `query` (string, required): Free-text seed, e.g. "learning studio app", a bare SLD, or a full domain.
- `tlds` (array): Optional TLDs to restrict the search to, e.g. ["com", "app", "io"]. The name on each becomes a top pick.
- `years` (integer): Registration term in years (default 1).

Output parameters:

- `count` (integer)
- `left_out` (object): How many checked candidates aren't suggestions, by reason, so a short list explains itself: over_limit (past limit), over_max_price, premium (include_premium is false), premium_over_cap (above the pu…
- `query` (string)
- `suggestions` (array): Available names, never one of the top picks.
- `tlds` (array|null): With tlds, one entry per extension asked for, in that order; null without it.
- `top_picks` (array): The name as typed (when its TLD isn't .com/.net/.org) and the SLD on .com, .net and .org, or with tlds on each extension listed (up to 12), taken or unknown included.
- `unchecked` (integer): How many names unchecked_names lists. A count, never an estimate.
- `unchecked_names` (array): Names whose check came back unknown (top picks included): not taken, just unanswered. Check them again to know.

### `get_tld_requirements` (~187 tokens)

Get an extension's prices and registration rules

Look up what OrbitFour charges and requires for domain extensions (TLDs): standard per-year registration, renewal, transfer and restore prices in USD plus the ICANN fee, the shortest and longest term, the fixed transfer term, whether WHOIS privacy is allowed, any eligibility or use restriction, whether browsers require HTTPS for its websites (https_required: .app, .dev), and JSON Schemas for what a registration must include (.us, for example, needs Nexus data on the registrant contact). Up to 10 extensions per call; read-only. These are standard prices: when premium_possible is true a particular name can cost more, so quote it with check_domain. An extension OrbitFour does not sell comes back as tld_not_found.

Input parameters:

- `tlds` (array, required): Extensions without the dot, e.g. ["us", "ai", "com"].

Output parameters:

- `constraints` (object): Account-wide rules that apply to every TLD.
- `tlds` (array)

### `check_transfer` (~185 tokens)

Check whether domains can be transferred in

Ask each name's registry whether it can be transferred to OrbitFour now (not locked, no transfer or delete pending) and quote the full first-term transfer price in USD: the per-year price plus the ICANN fee for the registry's transfer term. Up to 5 names per call; read-only. transferable is true, false, or null (the registry could not be asked just now; not the same as locked), and reasons says why: invalid_name, unsupported_tld, already_here, not_registered (nobody holds it, so register it instead), locked, pending_transfer, pending_delete, premium_over_cap, price_unconfirmed, unknown. The price is what the transfer would cost if it goes ahead. Never send a transfer authorization code here: the transfer itself asks for it.

Input parameters:

- `names` (array, required): Domain names, e.g. ["example.com"].

Output parameters:

- `data` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-orbitfour-domains/www#diagnostics

## Score history

- 2026-11-05: 77
- 2026-11-04: 77
- 2026-11-03: 76
- 2026-11-02: 76
- 2026-11-01: 75
- 2026-10-31: 75
- 2026-10-30: 74
- 2026-10-29: 74
- 2026-10-28: 73
- 2026-10-27: 73
- 2026-10-26: 72
- 2026-10-25: 72
- 2026-10-24: 71
- 2026-10-23: 71

## Common questions

### What is the OrbitFour MCP server?

OrbitFour is an MCP server listed in the public MCP registry as com.orbitfour/domains. Check domain availability and live registry pricing, or search for available names. This page covers its hosted endpoint (https://www.orbitfour.com/mcp).

### Is the OrbitFour MCP server safe to use?

OrbitFour scores 77 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 OrbitFour MCP server expose?

OrbitFour exposes 4 tools: check_domain, search_domains, get_tld_requirements, check_transfer. Their descriptions and schemas cost roughly 1,053 tokens of context every time the server is loaded.

### Does the OrbitFour MCP server require authentication?

No. We connected to OrbitFour without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the OrbitFour MCP server still maintained?

OrbitFour is still listed as active in the MCP registry. We last reached this channel on 5 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 OrbitFour MCP server?

VerifyMCP ran 13 checks on OrbitFour, 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.

## Links

- Remote endpoint: https://www.orbitfour.com/mcp
- Website: https://www.orbitfour.com/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-orbitfour-domains/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-orbitfour-domains/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-orbitfour-domains/www.json
- HTML version of this page: https://verifymcp.io/servers/com-orbitfour-domains/www