# DNSMint (remote · dnsmint.com)

Mint a secure HTTPS endpoint for your agents. Each on its own dedicated domain.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `dnsmint.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/com-dnsmint-mcp/dnsmint.md), [page](https://verifymcp.io/servers/com-dnsmint-mcp/dnsmint)
- npm · `dnsmint-mcp-server`: 33/100, [markdown](https://verifymcp.io/servers/com-dnsmint-mcp/dnsmint-mcp-server.md), [page](https://verifymcp.io/servers/com-dnsmint-mcp/dnsmint-mcp-server)

## Channel facts

- Endpoint: `https://dnsmint.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-22.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1205 tokens (~150/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 DNSMint MCP server?

DNSMint is a hosted endpoint at https://dnsmint.com/mcp, so there is nothing to install locally. 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 --transport http com-dnsmint-mcp 'https://dnsmint.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-dnsmint-mcp": {
      "url": "https://dnsmint.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-dnsmint-mcp": {
      "type": "http",
      "url": "https://dnsmint.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-dnsmint-mcp]
url = "https://dnsmint.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dnsmint-mcp": {
      "type": "remote",
      "url": "https://dnsmint.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-dnsmint-mcp --url 'https://dnsmint.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-dnsmint-mcp:
    url: "https://dnsmint.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-dnsmint-mcp": {
      "Transport": "http",
      "Url": "https://dnsmint.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-dnsmint-mcp -t streamable-http -u 'https://dnsmint.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-dnsmint-mcp": {
      "type": "http",
      "url": "https://dnsmint.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-22 (score 84, +1)

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

### 2026-09-20 (score 83, +1)

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

### 2026-09-18 (score 82, +1)

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

### 2026-09-15 (score 81, +1)

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

### 2026-09-13 (score 80, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Stability: unverified → 0.03

### 2026-09-12 (score 79, +41)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: fail

### 2026-09-08 (score 38)

First indexed and scored.

## MCP tools (8)

### `list_hostnames` (~43 tokens)

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.

### `get_plan` (~91 tokens)

Get the 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.

### `get_hostname` (~56 tokens)

Get a 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.

Input parameters:

- `id` (string, required): The hostname's id, from list_hostnames.

### `diagnose_hostname` (~72 tokens)

Diagnose a 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.

Input parameters:

- `id` (string, required): The hostname's id, from list_hostnames.

### `mint_hostname` (~245 tokens)

Mint a 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.

Input parameters:

- `domain` (string): Which of the account's domains to mint on. Omitted, DNSMint picks when the account holds one.
- `ip` (string): IPv4 or IPv6, public or private.
- `subdomain` (string): The label to use. Omitted, DNSMint picks an opaque one.
- `target` (string): A platform endpoint to mint on instead of an address, when the platform gave you a URL and no IP. Send either ip or target, not both.

### `repoint_hostname` (~147 tokens)

Repoint a 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.

Input parameters:

- `id` (string, required): The hostname's id, from list_hostnames.
- `ip` (string): The new address.
- `target` (string): A platform endpoint to follow instead of a fixed address, when the platform gave you a URL and no IP. Send either ip or target, not both.

### `release_hostname` (~158 tokens)

Release a 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.

Input parameters:

- `confirm` (string, required): The full hostname, exactly. Must match the name behind that id.
- `id` (string, required): The hostname's id, from list_hostnames.

### `start_checkout` (~224 tokens)

Start a 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.

Input parameters:

- `domains` (integer): Dedicated domains the plan should include. Leave unset to keep the current count.
- `hostnames` (integer): Hostnames the plan should include. Ask for the cap you need, not the extra.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-dnsmint-mcp/dnsmint#diagnostics

## Score history

- 2026-09-22: 84
- 2026-09-21: 83
- 2026-09-20: 83
- 2026-09-19: 82
- 2026-09-18: 82
- 2026-09-17: 81
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 38
- 2026-09-10: 38
- 2026-09-09: 38
- 2026-09-08: 38

## Common questions

### What is the DNSMint MCP server?

DNSMint is an MCP server listed in the public MCP registry as com.dnsmint/mcp. Mint a secure HTTPS endpoint for your agents. Each on its own dedicated domain. This page covers its hosted endpoint (https://dnsmint.com/mcp).

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

DNSMint scores 84 out of 100 on VerifyMCP. 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 DNSMint MCP server expose?

DNSMint exposes 8 tools: list_hostnames, get_plan, get_hostname, diagnose_hostname, mint_hostname, and 3 more. Their descriptions and schemas cost roughly 1,036 tokens of context every time the server is loaded.

### Does the DNSMint MCP server require authentication?

Yes. DNSMint asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the DNSMint MCP server still maintained?

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

## Links

- Remote endpoint: https://dnsmint.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-dnsmint-mcp/dnsmint.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dnsmint-mcp/dnsmint.json
- HTML version of this page: https://verifymcp.io/servers/com-dnsmint-mcp/dnsmint