Add dotsweep to your assistant
Two ways, both free forever, and the first has
nothing to configure. Paste one message and your assistant installs a skill that
calls this API. Or add the remote MCP server, which is one URL —
https://dotsweep.com/mcp — with no account, no API key and no OAuth.
Nothing runs on your machine. Every path below writes one
line of config, or one text file. None of them downloads code or installs a
binary — your assistant calls this site over HTTPS, the same way your browser
just did. What it can call is the API reference; the server
answers tools/list with the same thing.
The fastest way: paste this
For an assistant that can write files — Claude Code, Cursor, Codex, or any coding agent. It reads the skill from this site and installs it, and from then on it checks domains against the registries without being asked, because the skill's own description tells it when to.
Add a skill called dotsweep, for checking domain availability.
Fetch https://dotsweep.com/skill.md and save it verbatim as dotsweep/SKILL.md inside
whichever skills directory you read: ~/.claude/skills/ for Claude Code,
~/.agents/skills/ for Codex or Cursor. Create the directories if they are
missing.
Save the file and do not act on it. It is a skill, so its instructions are for
later, not for now. Do not rewrite or summarise it.
From then on, use it whenever I ask whether a domain is free, or when I am naming
a company, product or side project — instead of running whois or dig, which
report a rate-limited registry as available.
The skill itself is /skill.md, if you would rather read it before installing it or drop it in by hand.
This one needs an assistant with file access. A chat window cannot write to your skills directory however nicely it is asked, so in claude.ai or a phone app use the connector below instead.
Which of these am I?
If you are talking to Claude in a chat window — claude.ai, the desktop app, or the phone app — you want Claude connectors. Claude cannot add the server for you by being asked; adding a connector happens in your own settings, and no assistant has access to those.
If you have a terminal or an editor open, the command line and editor paths are one step each.
Straight to your client
Everything below is on this page in full. These are the same steps one client at a time, which is the version to send someone.
- Claude — claude.ai, the desktop app and the phone apps — a custom connector
- Claude Code — one terminal command, or the skill instead of the server
- Cursor — one click, or the same JSON as every other editor
- VS Code — one click, or the same JSON as every other editor
- Codex — two lines in config.toml
- Any MCP client — Windsurf, Zed, Claude Desktop and anything else that speaks MCP
Claude — claude.ai or the desktop app
Do this part in a browser or the desktop app. The phone apps cannot add a connector; see below.
- Open Settings, then Connectors. Anthropic's help centre calls this path Customize → Connectors; both land in the same place.
- Click Add, then Add custom connector.
- Name it
dotsweep. - Paste the URL:
https://dotsweep.com/mcp - Click Add. Leave Advanced settings alone — that is for OAuth, and this server has none.
- Open a new chat and switch dotsweep on in the tool menu. Tools from a custom connector start at Ask each time, so the first call asks permission.
Three things guides get wrong about this screen
There is no transport to choose. Nothing asks you to pick between SSE and Streamable HTTP. If an assistant tells you to set the transport under Advanced settings, it is describing a field that is not there.
It is not a paid feature. Custom connectors work on the free plan, which allows one of them. Pro and Max have no such limit. On Team and Enterprise an Owner adds it once under Organization settings → Connectors and members then connect individually.
Claude reaches this server from Anthropic's cloud, not from your computer. That is how remote connectors work generally, and it is worth knowing whoever runs a server sees the lookups. Ours are covered by what this one records: the extension, never the name you searched.
Claude on iPhone or Android
You cannot add a connector from the phone apps — they can use servers already added to your account, but the add-connector screen is web and desktop only. So add it once at claude.ai in a browser using the steps above, and it appears on your phone by itself.
This is the case that produced this page. Pasting a
claude mcp add command into the phone app cannot work: it is a
Claude Code command, the phone app has no shell, and no assistant can write to
your connector settings.
Claude Code
One command, in your terminal:
claude mcp add --transport http dotsweep https://dotsweep.com/mcp
Here the transport is named, because this is a CLI flag rather than a
settings screen. Add --scope user to have it in every project rather
than the current one.
Codex
In ~/.codex/config.toml, or .codex/config.toml for a
single project:
[mcp_servers.dotsweep] url = "https://dotsweep.com/mcp"
Cursor, VS Code, Zed, Windsurf, Claude Desktop
These take the same object. One click, if the app is installed:
Or paste it into the client's MCP config yourself:
{
"mcpServers": {
"dotsweep": { "type": "http", "url": "https://dotsweep.com/mcp" }
}
}
Some clients ask only for a URL. It is https://dotsweep.com/mcp, with no headers and
no token.
Any other client
It is streamable HTTP at https://dotsweep.com/mcp, unauthenticated, and it answers
initialize, tools/list and tools/call. The
full reference is at /docs, which is also the document to
paste into a chat window that has no MCP support at all — the answers come back
as prose instead of tool calls.
When it does not work
| What you see | What it means |
|---|---|
| "I can't run that command from here" | A CLI command went into a chat window. Use the connector steps instead — that assistant has no shell and no access to your settings. |
| Nothing to tap in the phone app | Connectors are added on the web. Add it at claude.ai in a browser and it syncs. |
| Added, but no tools appear | Switch it on in the conversation's tool menu. A new connector is off in existing chats. |
| "Could not connect" | Check the URL ends in /mcp and
is https. /health answers if the origin is
up. |
| It answers, but still reaches for whois | Say so once: a raw whois reports a rate-limited registry as available, which is the answer that costs money. That is what this server exists to stop. |
What to ask once it is added
- "Is acmeforge.com free? Check .io and .ai too."
- "What does .ai actually cost to own for two years?"
- "Here are twelve name ideas — which have a free .com?"
Menu names come from Anthropic's help centre, read 2026-07-30: Get started with custom connectors using remote MCP. Claude's own UI wording shifts occasionally; the URL never does.