Apexly is answering right now. Last checked 7 min ago. It exposes 8 tools.
Add, check, diagnose and remove your SaaS customers' custom domains from any MCP client.
Uptime history
13 days of history
13 days agonow
100.0%
Uptime 24h
91 of 91 checks
8
Tools
read from the server
564 ms
Response time
average over 24h
open, no key
Access
streamable-http
Nothing serious here today
Today is the operative word: we check Apexly every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.
run in your terminal
claude mcp add mcp --transport http https://mcp.apexly.dev/mcpSettings → Connectors → Add custom connector, then paste this address
https://mcp.apexly.dev/mcp~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.apexly.dev/mcp".cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.apexly.dev/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "http",
"url": "https://mcp.apexly.dev/mcp"
}
}
}Available tools 8
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
domain
create_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.
delete_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.
get_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.
connect
get_connect_url
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.
diagnose
diagnose_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.
dns
get_dns_instructions
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).
domains
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.
verify
verify_domain
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.apexly.dev/mcp | streamable-http | answering | 560 ms | 7 min ago |
Alternatives to Apexly
same job, measured the same waySupportWire
by supportwire
Run your SupportWire support inbox from any MCP client: conversations, replies, customers, team.
JustEmails
by justemails
Email hosting from your AI: read and send mail, add domains, check DNS and manage mailboxes.
ShipLog
by amacgregor
Read user feedback and draft your changelog from any MCP client.
RenewRoster
by renewroster
Track domain and SSL certificate expiry for your agency clients from any MCP client.
Worldku Memory
by worldku
Save AI conversations into your Worldku memory and recall them from any MCP client.
Clean
by cleanmcp
Clean finds your next customers: ICP, researched leads, replies and sequences, from any agent.
Whatsapp
by wacli
Your own WhatsApp as an MCP server: read, search and send from any MCP client.
Gisti — AI Checklists
by antonchuraev99
Read, AI-create, and edit your Gisti checklists in plain language from any MCP client.
Apexly — questions
Answers built from our own checks of this server.
What can Apexly do?
It exposes 8 tools, read directly from the server on our last check. Among them: create_domain, delete_domain, diagnose_domain, get_connect_url, get_dns_instructions, get_domain and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Apexly working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 564 ms. The bar chart above shows every period we have measured.
How do I connect Apexly?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Apexly need an API key?
No. Apexly completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Apexly?
It answers our handshake in 564 ms on average, which is faster than 20% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.