# AgentDomains (npm · agentdomains-mcp)

Free domains under makes.fyi or agentdomains.co for the sites and APIs AI agents build.

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

## Components

- remote · `mcp.agentdomains.co`: 70/100, [markdown](https://verifymcp.io/servers/tashfeenahmed-agentdomains-mcp/mcp.md), [page](https://verifymcp.io/servers/tashfeenahmed-agentdomains-mcp/mcp)
- npm · `agentdomains-mcp`: 77/100 (this document), [markdown](https://verifymcp.io/servers/tashfeenahmed-agentdomains-mcp/agentdomains-mcp.md), [page](https://verifymcp.io/servers/tashfeenahmed-agentdomains-mcp/agentdomains-mcp)

## Channel facts

- Registry: `npm`
- Package: `agentdomains-mcp`
- Version: `0.1.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-10-23.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (FSL-1.1-Apache-2.0) isn't a recognized OSI-approved license.
  - Actively maintained (last published 25 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3291 tokens (~173/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 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.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_domain" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 19 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 AgentDomains MCP server?

AgentDomains runs locally as an npm package, launched with npx -y agentdomains-mcp. 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 tashfeenahmed-agentdomains-mcp -- npx -y agentdomains-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "tashfeenahmed-agentdomains-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "agentdomains-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tashfeenahmed-agentdomains-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "agentdomains-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add tashfeenahmed-agentdomains-mcp -- npx -y agentdomains-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tashfeenahmed-agentdomains-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "agentdomains-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tashfeenahmed-agentdomains-mcp --command npx --arg -y --arg agentdomains-mcp
```

### Hermes

```yaml
mcp_servers:
  tashfeenahmed-agentdomains-mcp:
    command: "npx"
    args: ["-y", "agentdomains-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "tashfeenahmed-agentdomains-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "agentdomains-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add tashfeenahmed-agentdomains-mcp -t stdio -c npx -a -y agentdomains-mcp
```

### Other

```json
{
  "mcpServers": {
    "tashfeenahmed-agentdomains-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "agentdomains-mcp"
      ]
    }
  }
}
```

## 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-10-23 (score 77, +1)

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

### 2026-10-21 (score 76, +1)

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

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

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

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

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

### 2026-10-15 (score 73, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-14 (score 72, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-13 (score 72, +6)

- [functional improvement] Stability: unverified → 0.43

### 2026-10-12 (score 66, 0)

- [functional regression] Security disclosure: unverified → fail

## MCP tools (19)

### `check_availability` (~143 tokens)

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).

Input parameters:

- `domain` (string): Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default.
- `label` (string, required): The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi).

### `signup` (~111 tokens)

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.

### `whoami` (~117 tokens)

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).

### `attach_email` (~66 tokens)

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.

Input parameters:

- `email` (string, required): The email address to attach and send the verification link to.

### `claim_domain` (~348 tokens)

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.

Input parameters:

- `content` (string): Value for that record (an IP for A/AAAA, a hostname for CNAME, text for TXT).
- `domain` (string): Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default.
- `email` (string): Required on the account's first registration if no email is attached yet. Sends a confirmation link.
- `host` (string): Optional extra sub-label for the record (e.g. 'www' gives www.myapp.makes.fyi).
- `label` (string, required): The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi).
- `type` (string): Optional DNS record to create immediately: A, AAAA, CNAME, or TXT.

### `list_domains` (~37 tokens)

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

### `get_domain` (~108 tokens)

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

Input parameters:

- `domain` (string): Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default.
- `label` (string, required): The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi).

### `delete_domain` (~153 tokens)

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.

Input parameters:

- `domain` (string): Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default.
- `label` (string, required): The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi).

### `add_dns_record` (~276 tokens)

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.

Input parameters:

- `content` (string, required): Record value: an IP for A/AAAA, a hostname for CNAME, the string for TXT.
- `domain` (string): Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default.
- `host` (string): Optional extra sub-label under the name (e.g. 'www' creates www.myapp.makes.fyi). Omit for the name itself.
- `label` (string, required): The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi).
- `type` (string, required): Record type: A, AAAA, CNAME, or TXT.

### `delete_record` (~212 tokens)

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.

Input parameters:

- `domain` (string): Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default.
- `label` (string, required): The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi).
- `record_id` (string, required): The record's 'id' as reported by get_domain — not its name, type, or content.

### `add_acme_challenge` (~203 tokens)

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.

Input parameters:

- `domain` (string): Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default.
- `label` (string, required): The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi).
- `value` (string, required): The challenge token from your ACME client, published verbatim as the TXT value.

### `set_forward` (~362 tokens)

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.

Input parameters:

- `cloak` (boolean): Keep the AgentDomains hostname in the address bar and load the target inside a frame. Discouraged — breaks many sites.
- `domain` (string): Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default.
- `email` (string): Email, if this call also claims a new name on an account without one.
- `label` (string, required): The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi).
- `permanent` (boolean): Use a 301 permanent redirect instead of the default 302 temporary one.
- `preserve_path` (boolean): Append the incoming path and query to the target. Defaults to true; set false to always land on the target root.
- `target` (string, required): Destination URL, including scheme (e.g. https://example.com/docs).

### `remove_forward` (~106 tokens)

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

Input parameters:

- `domain` (string): Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default.
- `label` (string, required): The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi).

### `set_proxy` (~301 tokens)

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.

Input parameters:

- `domain` (string): Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default.
- `email` (string): Email, if this call also claims a new name on an account without one.
- `label` (string, required): The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi).
- `origin` (string, required): Backend hostname to proxy to, without a scheme (e.g. myapp.fly.dev). Must be a hostname, not an IP.

### `remove_proxy` (~117 tokens)

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.

Input parameters:

- `domain` (string): Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default.
- `label` (string, required): The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi).

### `delegate_nameservers` (~182 tokens)

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.

Input parameters:

- `domain` (string): Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default.
- `label` (string, required): The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi).
- `nameservers` (array, required): Your nameserver hostnames, e.g. ['ns1.yourdns.com', 'ns2.yourdns.com']. At least two.

### `delete_account` (~194 tokens)

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.

Input parameters:

- `force` (boolean): Delete the names the account still holds along with it. Without this the call is refused while any name remains, which is the intended default.

### `upgrade_to_pro` (~180 tokens)

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.

Input parameters:

- `interval` (string): Billing interval: 'month' ($5, the default) or 'year' ($48).

### `manage_billing` (~75 tokens)

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).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/tashfeenahmed-agentdomains-mcp/agentdomains-mcp#diagnostics

## Score history

- 2026-10-23: 77
- 2026-10-22: 76
- 2026-10-21: 76
- 2026-10-20: 75
- 2026-10-19: 75
- 2026-10-18: 74
- 2026-10-17: 74
- 2026-10-16: 73
- 2026-10-15: 73
- 2026-10-14: 72
- 2026-10-13: 72
- 2026-10-12: 66
- 2026-10-11: 66
- 2026-10-04: 66
- 2026-10-03: 66
- 2026-10-02: 66
- 2026-10-01: 66
- 2026-09-30: 51

## Common questions

### What is the AgentDomains MCP server?

AgentDomains is an MCP server listed in the public MCP registry as io.github.tashfeenahmed/agentdomains-mcp. Free domains under makes.fyi or agentdomains.co for the sites and APIs AI agents build. This page covers its npm package (agentdomains-mcp).

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

AgentDomains scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. 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 AgentDomains MCP server expose?

AgentDomains exposes 19 tools: check_availability, signup, whoami, attach_email, claim_domain, and 14 more. Their descriptions and schemas cost roughly 3,291 tokens of context every time the server is loaded.

### Is the AgentDomains MCP server still maintained?

AgentDomains is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the AgentDomains MCP server under?

AgentDomains declares the FSL-1.1-Apache-2.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/agentdomains-mcp
- Socket report: https://socket.dev/npm/package/agentdomains-mcp
- Repository: https://github.com/tashfeenahmed/AgentDomains-mcp
- Changelog RSS feed: https://verifymcp.io/servers/tashfeenahmed-agentdomains-mcp/agentdomains-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tashfeenahmed-agentdomains-mcp/agentdomains-mcp.json
- HTML version of this page: https://verifymcp.io/servers/tashfeenahmed-agentdomains-mcp/agentdomains-mcp