DNSMint MCP server
com.dnsmint/mcpdnsmint.comstreamable-httpv1.0.1Scanned
Mint a secure HTTPS endpoint for your agents. Each on its own dedicated domain.
8 tools: 1 can delete or cancel things, 4 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Sign-in required, no OAuth metadata. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the DNSMint MCP server can do
The DNSMint MCP server is published by dnsmint.com, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (1 tool: release_hostname) and create or change data (4 tools: diagnose_hostname, mint_hostname, repoint_hostname and start_checkout). 3 tools only read.
1 tool reads private data (list_hostnames); 1 tool brings in text other people can write (start_checkout).
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Last scanned Nov 13, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Deletes or cancels 1Claude Code: deny
release_hostnamePERMANENTLY give up a hostname.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
Changes things 4Claude Code: ask
diagnose_hostnameWhy a hostname is or is not working: what the nameservers answer, what public resolvers see, and whether a certificate has been issued.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
mint_hostnameRegister an address and get back a stable hostname that survives the address changing.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: false
repoint_hostnamePoint an existing hostname at a new address.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: true
start_checkoutGet a payment link the account owner opens to raise this account's limits.Reads text others writeNo findings
Why it is in this group
- The name "start_checkout" says "start": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 3Show 3 read-only tools
get_hostnameOne hostname's status and certificate mode.No findings
Why it is in this group
- The name "get_hostname" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
get_planWhat this account's plan allows and how much of it is used: hostnames, dedicated domains, and whether a plan is active at all.No findings
Why it is in this group
- The name "get_plan" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
list_hostnamesEvery hostname this credential can see, with how many are active and the plan's cap.Reads private data1 finding
Why it is in this group
- The name "list_hostnames" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "credential": it reads secrets.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "Every hostname this credential can see, with how many are active and t..."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:37 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 404
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 404.
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://dnsmint.com/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://dnsmint.com to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
- Infolist_hostnames
The description mentions "credential".
What this check looks forMatched text
description: "Every hostname this credential can see, with how many are active and t..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 5 -> 0 (and 5 more).View diff
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://dnsmint.com/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://dnsmint.com to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http dnsmint https://dnsmint.com/mcpclaude mcp add --transport http dnsmint https://dnsmint.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__dnsmint__list_hostnames",
"mcp__dnsmint__get_plan",
"mcp__dnsmint__get_hostname"
],
"ask": [
"mcp__dnsmint__diagnose_hostname",
"mcp__dnsmint__mint_hostname",
"mcp__dnsmint__repoint_hostname",
"mcp__dnsmint__start_checkout"
],
"deny": [
"mcp__dnsmint__release_hostname"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dnsmint. Review it before you use it.
Capability tags behind 2 rules
- mcp__dnsmint__list_hostnames private-data
- mcp__dnsmint__start_checkout untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.dnsmint/mcp/verify?hash=355d63fb6d4637ee9c67f0577ef519cf197787a04630d8ca8db8b48375ef541d" | jq -e '.changed == false'Pinned hash 355d63fb6d46, from Nov 13, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.dnsmint/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.dnsmint/mcp)Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.
DNSMint MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the DNSMint MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the DNSMint MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: release_hostname.
Can the DNSMint MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the DNSMint MCP server have?
- 8 tools: 1 destructive, 4 write, 3 read. release_hostname, diagnose_hostname, mint_hostname, repoint_hostname, start_checkout, list_hostnames, get_plan and get_hostname.
Does the DNSMint MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the DNSMint MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the DNSMint MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.