AgentDomains MCP server

• add_acme_challengewrite actionFree

  Publish a Let's Encrypt DNS-01 challenge: creates a TXT record at _acme-challenge.<label>.<domain> with the token your ACME client printed. Use this to get a certificate without exposing port 80 (for example for a wildcard cert, or a host behind NAT). DNS propagates within seconds, then tell your ACME client to continue. For a normal public web server, HTTP-01 validation needs no DNS record at all.

• add_dns_recordFree

  Add a DNS record to a subdomain you already own. Use type A or AAAA to point at an IP address, CNAME to point at another hostname, or TXT for verification strings. Adding a record does not replace existing ones; use delete_record to remove a single one. Refused with a 409 while the label carries a forward or a proxy (they own the hostname) — call remove_forward or remove_proxy first, or add the record on a sub-label via 'host', which is a different hostname and unaffected.

• attach_emailwrite actionFree

  Attach an email address to the account and send it a verification link. A human must click that link within 30 days or the provisional account and its domains are deleted. Use this right after signup.

• check_availabilityFree

  Check whether a subdomain label is free before claiming it. Requires no API key. Returns { label, domain, fqdn, available, reason } where reason is 'available', 'taken', or 'invalid' (with a 'detail' explaining why the label is not usable).

• claim_domainFree

  Register a subdomain (label.makes.fyi or label.agentdomains.co) on this account, optionally creating its first DNS record in the same call. An email is required the first time an account registers a name — pass 'email' here or call attach_email first; the name is reaped if that email is not confirmed within 30 days. Returns the fqdn and, when a record was requested, the created record. The claim and its first record succeed or fail together: if the record is malformed (400) or the provider refuses it (503) the label is NOT claimed, so fix the record and call again. Re-claiming a name this account already holds answers 409 with owned:true — that means carry on using it, not pick another label.

• delegate_nameserversFree

  Delegate the subdomain to your own nameservers, handing you full control of it and everything beneath it (your own records, MX, deeper sub-domains). AgentDomains stops answering for the name, so its existing records, forwards, and proxies no longer apply. Supply at least two nameservers.

• delete_accountwrite actionFree

  DESTRUCTIVE AND IRREVERSIBLE, AND THE LARGEST ONE HERE: delete the whole AgentDomains account and invalidate its API key, which cannot be recovered or reissued — every later tool call fails with a 401 until a new signup. Without force it REFUSES while the account still holds names, answering 409 with the list of them; that refusal is a safety net, so show the list to the user and get an explicit yes before retrying. With force:true those names are deleted too: they stop resolving at once and are released for anyone else to claim. Only ever call this when the user has asked to close the account itself — never as cleanup after a task, and never to 'start fresh' on your own initiative.

• delete_domainwrite actionFree

  DESTRUCTIVE AND IRREVERSIBLE: permanently delete a subdomain and every DNS record, forward, and proxy attached to it. The hostname stops resolving immediately and the label is released for anyone else to claim. There is no undo and no recovery. Only call this when the user has explicitly asked for this specific name to be deleted.

• delete_recordwrite actionFree

  DESTRUCTIVE: permanently remove ONE DNS record from a subdomain, keeping the name and every other record. Use this to undo a single record — a wrong IP, a spent ACME challenge — instead of delete_domain, which takes the whole name. The record_id is the 'id' field shown by get_domain (and returned by claim_domain and add_dns_record); it is not the record's name or content. The hostname stops resolving through that record immediately and there is no undo.

• get_domainFree

  Show one subdomain in full: its fqdn, DNS records, forward or proxy configuration, and delegation state.

• list_domainsFree

  List every subdomain on this account, with each one's DNS records and whether it is forwarding, proxying, or delegated to external nameservers.

• manage_billingFree

  Get a Stripe billing-portal link for a Pro account: update the card, see invoices, switch between monthly and yearly, or cancel. A human must open it. Cancelling keeps Pro to the end of the paid period and never deletes a name. Answers 409 if the account has never subscribed (use upgrade_to_pro).

• remove_forwardwrite actionFree

  Stop forwarding a subdomain. The name itself stays registered on the account; only the redirect is removed.

• remove_proxywrite actionFree

  Stop reverse-proxying a subdomain, so the edge no longer serves the backend or terminates TLS for it. The name stays registered on the account.

• set_forwardFree

  Forward (HTTP-redirect) a subdomain to another URL. Claims the label first if you do not own it yet, in which case an email may be required exactly as for claim_domain. Defaults to a 302 temporary redirect that preserves the request path and query. HTTPS at the edge is handled for you. A forward TAKES OVER the hostname: any A/AAAA/CNAME record on the label itself is deleted as part of this call and returned in 'replaced_records' — report those to the user, since the name no longer points where it did. Records on a sub-label (www.myapp.makes.fyi) and TXT records are untouched. If the forward fails to come up the replaced records are restored, with new ids.

• set_proxyFree

  Serve a backend at this subdomain through the AgentDomains edge, which terminates TLS with its own certificate — this is how you get working HTTPS on an origin that has no certificate of its own (a bare IP-less PaaS host, a tunnel, an internal box). Unlike a forward, the URL stays on your domain and the response is proxied, not redirected. Claims the label first if needed. Like a forward, a proxy TAKES OVER the hostname: A/AAAA/CNAME records on the label itself are deleted and returned in 'replaced_records', while sub-label and TXT records are untouched. A proxy and a forward are mutually exclusive on one label. Caveat: apps that hardcode their own hostname (OAuth callbacks especially) may need your new hostname registered on their side.

• signupwrite actionFree

  Create a new AgentDomains account and get an API key. Requires no existing key. IMPORTANT: the returned api_key is shown ONCE and is never retrievable again — you must store it immediately (save it to ~/.agentdomains/config.json or set AGENTDOMAINS_API_KEY) or the account is lost. The account is provisional: attach and confirm an email within 30 days (see the attach_email tool) or it is deleted along with its domains. This endpoint is rate-limited per IP address.

• upgrade_to_proFree

  Get a Stripe checkout link for AgentDomains Pro: 100 names instead of the free 10, names never released for being unreachable, and priority email support, for $5/month (or $48/year with interval 'year'). Use this when a claim is refused because the account is at its name limit and the user wants more. It only returns a link and never charges anything: a human must open the URL and pay. Show them the url and say what Pro costs; do not open it or pay on their behalf. If the account is already Pro the answer has kind:'portal' and a link to manage the subscription instead. Answers 404 'billing is not enabled' on a server that does not sell Pro.

• whoamiFree

  Show the current account: id, state, attached email and whether it is verified, domains used, and which domains are available to claim under. When quotas are disabled the response omits 'quota' and says unlimited:true; 'max_subdomains' is the separate hard cap on how many names one account may hold at once (10 on the free plan, 100 on Pro). 'plan' is 'free' or 'pro'; when Pro is on sale a free account also gets an 'upgrade' hint (see upgrade_to_pro).

• Code scan9 source files scanned25/25
• Live reliabilityremote reachable in 307ms20/20
• Tool poisoning19 tool descriptions checked15/15
• Auth qualityAPI key sent as a header8/15
• Maintenancelast push 1 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

91/100

higher than 85% of 48,255 servers

Tools

19

the typical server has 7

Tools that change things

42%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

57 ms

faster than 91% of 30,031 servers

GitHub stars

2

more than 75% of 28,688 servers

Downloads a week

191

more than 74% of 12,191 servers with a package

AgentDomains: common questions

Is AgentDomains MCP server safe?

Yes, by our scan: it is graded A (91/100). Read the AgentDomains safety report

How do I install AgentDomains?

It runs remotely at mcp.agentdomains.co. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does AgentDomains need an API key?

Yes. The registry entry asks for AGENTDOMAINS_API_KEY, Authorization.

Is AgentDomains maintained?

The last commit was 35 days ago (2026-09-30). The latest release is v0.1.3.

Is AgentDomains up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does AgentDomains compare with other MCP servers?

safety score 91/100 (higher than 85% of 48,255 servers); tools 19 (the typical server has 7); tools that change things 42% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.