DNSMint is listed as active in the registry but did not answer our last check. 37 installs a week from npm. It exposes 8 tools.
Mint a secure HTTPS endpoint for your agents. Each on its own dedicated domain.
Installs per day
peak 21 · avg 5 · +45% w/w
a month agotoday
Uptime history
62 days of history · worst day 0%
62 days agonow
6.6%
Uptime 24h
6 of 91 checks
8
Tools
read from the server
369 ms
Response time
average over 24h
37
Installs / week
npm and PyPI
DNSMint does not always answer
Over the last week it answered 2.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.
run in your terminal
claude mcp add mcp --transport http https://dnsmint.com/mcpSettings → Connectors → Add custom connector, then paste this address
https://dnsmint.com/mcp~/.codex/config.toml
[mcp_servers.mcp]
url = "https://dnsmint.com/mcp".cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://dnsmint.com/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "http",
"url": "https://dnsmint.com/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.
diagnose
diagnose_hostname
Why a hostname is or is not working: what the nameservers answer, what public resolvers see, and whether a certificate has been issued. Use this before assuming something is broken; a name minted moments ago may simply not have propagated.
hostname
get_hostname
One hostname's status and certificate mode. Does not say where it points: DNS is the authoritative answer for that, so use diagnose_hostname or resolve the name.
hostnames
list_hostnames
Every hostname this credential can see, with how many are active and the plan's cap. Check the cap before minting: a hostname is the unit the plan counts.
mint
mint_hostname
Register an address and get back a stable hostname that survives the address changing. This is the tool to use when a machine or agent needs a name.
The address class is fixed for the life of the name: mint with a public address and it stays public, mint with a private one and it stays private. Crossing later is refused, so pass the address the machine will actually serve on. A target fixes the class the same way, from whatever it resolves to.
A hostname is one label above a domain. Names below a hostname are not hostnames and cannot be minted.
Newly minted names report status 'pending' and go 'live' within about a minute.
plan
get_plan
What this account's plan allows and how much of it is used: hostnames, dedicated domains, and whether a plan is active at all. Also says whether a checkout is outstanding, which is how you find out a payment link you were given has not been completed yet.
Call this after handing someone a checkout URL, instead of retrying a mint to see if it worked. It costs nothing and changes nothing.
release
release_hostname
PERMANENTLY give up a hostname. Read this before calling it.
A released hostname is tombstoned and is never issued again, to anyone, including this account. There is no undo and it cannot be re-minted. This is not like deleting a DNS record.
Only call this when the name is genuinely finished with and a human has asked for it. If the goal is to stop serving, repoint it or stop the machine instead.
Pass the hostname in `confirm` exactly as it appears, so a name cannot be released by guessing an id.
repoint
repoint_hostname
Point an existing hostname at a new address. This is what makes the name worth having: the machine moves, the name does not, and everything holding the URL keeps working.
Repointing within an address class is free, including between IPv4 and IPv6. Crossing between public and private is refused, because one name resolving public then private is how DNS rebinding works.
start
start_checkout
Get a payment link the account owner opens to raise this account's limits. Call this when minting fails because the account is at its hostname cap or has no plan.
This charges nothing and buys nothing. It returns a URL, and the purchase only happens if a person opens it and enters card details. Give the URL to the human you are working with and say what it costs; do not try to complete it yourself, and do not call this repeatedly hoping the limit lifts. Nothing changes until somebody pays.
Only for an account with no plan yet. If one already exists you get the billing page back instead, because changing a running plan charges a card on file and is a person's decision.
Both numbers default to what the account already holds, so asking for hostnames alone keeps the domains. A plan smaller than what is in use is refused.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://dnsmint.com/mcp | streamable-http | answering | 101 ms | 10 min ago |
Alternatives to DNSMint
same job, measured the same wayAdminKit
by netbasecorp
Network, DNS, mail-auth and MCP endpoint security checks for AI agents, backed by adminkit.net.
Recon Kit MCP
by nan786521
Read-only network & security recon tools (DNS, TLS, headers, CORS) for AI agents, each graded.
PO6 Mailbox
by po6
Give AI agents secure access to your email via private aliases with dedicated mailbox storage.
Domainintel MCP
by bishop81
Domain intelligence for agents: WHOIS, DNS, SSL/TLS, security headers, reputation, subdomains.
Dep
by rog0x
License check, outdated deps, security for AI agents
Golem Security
by golem
Threat-intelligence verdicts on a URL, domain or IP before a coding agent connects to it.
Trustsource
by surfether
x402-paid domain verification for AI agents — trustscore, SSL, security headers, robots.
McpHub
by soflution
One MCP endpoint for all your servers: a few meta-tools, Keychain secrets, sandbox, audit, OAuth.
DNSMint — questions
Answers built from our own checks of this server.
What can DNSMint do?
It exposes 8 tools, read directly from the server on our last check. Among them: diagnose_hostname, get_hostname, get_plan, list_hostnames, mint_hostname, release_hostname 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 DNSMint working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 6 of 91 checks got a reply (6.6%), average response time 369 ms. The bar chart above shows every period we have measured.
The registry lists DNSMint as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect DNSMint?
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 DNSMint need an API key?
No. DNSMint 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 DNSMint?
It answers our handshake in 369 ms on average, which is faster than 35% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use DNSMint?
The npm package dnsmint-mcp-server was installed 37 times in the last week. Week over week that is +45%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.