# Apexly (remote · mcp.apexly.dev)

Add, check, diagnose and remove your SaaS customers' custom domains from any MCP client.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `mcp.apexly.dev`: 81/100 (this document), [markdown](https://verifymcp.io/servers/dev-apexly-mcp/mcp.md), [page](https://verifymcp.io/servers/dev-apexly-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.apexly.dev/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.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-06.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1104 tokens (~138/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 87% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

Apexly is a hosted endpoint at https://mcp.apexly.dev/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 dev-apexly-mcp 'https://mcp.apexly.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-apexly-mcp": {
      "url": "https://mcp.apexly.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-apexly-mcp": {
      "type": "http",
      "url": "https://mcp.apexly.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-apexly-mcp]
url = "https://mcp.apexly.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-apexly-mcp": {
      "type": "remote",
      "url": "https://mcp.apexly.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-apexly-mcp --url 'https://mcp.apexly.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-apexly-mcp:
    url: "https://mcp.apexly.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-apexly-mcp": {
      "Transport": "http",
      "Url": "https://mcp.apexly.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-apexly-mcp -t streamable-http -u 'https://mcp.apexly.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-apexly-mcp": {
      "type": "http",
      "url": "https://mcp.apexly.dev/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-06 (score 81, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

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

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

### 2026-11-02 (score 79, +1)

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

### 2026-10-30 (score 78, +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-29 (score 77, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 77, +41)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Tool coverage: 87
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: 100

### 2026-10-26 (score 36)

First indexed and scored.

## MCP tools (8)

### `create_domain` (~237 tokens)

Add a custom domain

Add a customer's hostname (e.g. careers.acme.com or acme.com) to the app this API key belongs to. Idempotent: adding a hostname the app already has returns the existing domain. The domain starts in pending_dns; the customer must then add the DNS record in status_explained / get_dns_instructions, or open the connect_url to be guided through it. Apexly checks DNS every 15 seconds and issues the TLS certificate itself. With a test key (sk_test_…) the domain is a sandbox one that goes active by itself in about 30 seconds. Never invent a hostname: ask the user which one.

Input parameters:

- `apex_redirect` (string): Apex domains only: also serve www.<apex> and redirect it
- `hostname` (string, required): The customer's hostname, no scheme or path, e.g. careers.acme.com
- `metadata` (object): Any JSON object up to 4 KB, e.g. {"customer": "Acme", "tenant_id": "42"}
- `origin` (string): Per-domain origin override (paid plans); omit to use the app origin

### `get_domain` (~103 tokens)

Get a domain

Current state of one domain: status (pending_dns → verifying → issuing → active; or dns_broken, cert_failed, held, expired), the DNS record the customer must add, the connect_url and the certificate. status_explained says in one sentence why it is in that status and what to do next. Use it to poll after create_domain or verify_domain.

Input parameters:

- `id` (string, required): The domain id (dom_…), from create_domain or list_domains

### `list_domains` (~95 tokens)

List domains

The app's domains, newest first, one page at a time. Pass next_cursor back as cursor for the next page (null means there are no more). Filter by status or by hostname prefix to find a domain id.

Input parameters:

- `cursor` (string): next_cursor of the previous page
- `hostname` (string): Hostname prefix, e.g. careers.
- `limit` (integer)
- `status` (string)

### `verify_domain` (~90 tokens)

Check a domain now

Queue a DNS check right away instead of waiting for the next scheduled one; use it after the customer says they added the record. On cert_failed it retries the certificate. At most one per 15 seconds per domain. The check runs in the background: call get_domain a few seconds later for the result.

Input parameters:

- `id` (string, required): The domain id (dom_…), from create_domain or list_domains

### `get_connect_url` (~89 tokens)

Get the connect page link

The link to send the customer (the domain owner): a page branded with the app that detects their DNS provider, shows the exact record with copy buttons and tells them when the domain is live. Prefer it when the customer is not technical. It is safe to share with the customer, not publicly.

Input parameters:

- `id` (string, required): The domain id (dom_…), from create_domain or list_domains

### `get_dns_instructions` (~108 tokens)

DNS instructions for the customer

The exact DNS record(s) the customer must add for this domain, plus step-by-step instructions for their DNS provider (detected from the domain's nameservers: GoDaddy, Cloudflare, Namecheap, Route 53 and ~40 more; generic steps otherwise). Record names are relative to the registrable domain ("careers" in acme.com, "@" for the apex).

Input parameters:

- `id` (string, required): The domain id (dom_…), from create_domain or list_domains

### `diagnose_domain` (~196 tokens)

Diagnose a domain

Why a domain is not live and what to change (the domain doctor, same as GET /v1/domains/{id}/diagnose): runs every check live (the record at 1.1.1.1, 8.8.8.8 and the domain's own nameservers, other A and stale AAAA records, the Cloudflare proxy, CAA, the certificate, the origin, the www pair). Each check is pass, fail, warn or skip with what we saw (detail) and what to change (fix); blocking_check_id is the one to fix first. status_explained says why the domain is in its status. Use it when a domain stays in pending_dns, dns_broken or cert_failed, then relay the fix to the customer. Results are reused for 20 seconds.

Input parameters:

- `id` (string, required): The domain id (dom_…), from create_domain or list_domains

### `delete_domain` (~96 tokens)

Delete a domain

Remove a domain: it stops being served within 5 seconds and its certificate is dropped. Irreversible (adding the hostname again starts over with a new record). Only call it after the user explicitly confirmed deleting this hostname, and pass confirm: true.

Input parameters:

- `confirm` (boolean): Must be true: the user confirmed deleting this domain
- `id` (string, required): The domain id (dom_…), from create_domain or list_domains

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-apexly-mcp/mcp#diagnostics

## Score history

- 2026-11-06: 81
- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 77
- 2026-10-28: 77
- 2026-10-27: 36
- 2026-10-26: 36

## Common questions

### What is the Apexly MCP server?

Apexly is an MCP server listed in the public MCP registry as dev.apexly/mcp. Add, check, diagnose and remove your SaaS customers' custom domains from any MCP client. This page covers its hosted endpoint (https://mcp.apexly.dev/mcp).

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

Apexly scores 81 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 Apexly MCP server expose?

Apexly exposes 8 tools: create_domain, get_domain, list_domains, verify_domain, get_connect_url, and 3 more. Their descriptions and schemas cost roughly 1,014 tokens of context every time the server is loaded.

### Does the Apexly MCP server require authentication?

Yes. Apexly 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 Apexly MCP server still maintained?

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

VerifyMCP ran 13 checks on Apexly, 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://mcp.apexly.dev/mcp
- Authorisation metadata: https://mcp.apexly.dev/.well-known/oauth-protected-resource/mcp
- Website: https://docs.apexly.dev/guides/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-apexly-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-apexly-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-apexly-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-apexly-mcp/mcp