io.usefulapi/dnsimple
REMOTE · DNSIMPLE.USEFULAPI.IO · SCANNED SEP 20
MCP server for DNSimple — domains, DNS zone records, availability, pricing and contacts.
Available components
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1151 tokens (~95/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/dnsimple MCP server?
io.usefulapi/dnsimple is a hosted endpoint at https://dnsimple.usefulapi.io/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.
remote · dnsimple.usefulapi.io
claude mcp add --transport http io-usefulapi-dnsimple 'https://dnsimple.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-dnsimple": {
"url": "https://dnsimple.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-dnsimple": {
"type": "http",
"url": "https://dnsimple.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-dnsimple] url = "https://dnsimple.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-dnsimple": {
"type": "remote",
"url": "https://dnsimple.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-dnsimple --url 'https://dnsimple.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-dnsimple:
url: "https://dnsimple.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-dnsimple": {
"Transport": "http",
"Url": "https://dnsimple.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-dnsimple -t streamable-http -u 'https://dnsimple.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-dnsimple": {
"type": "http",
"url": "https://dnsimple.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −2
- Stability: pass → 0.83 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Aug 26 83
- Authorization: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.87 ▲ functional
- 21 Aug 26 0
- Endpoint reachability: behind authorisation → not serving MCP ▼ security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://dnsimple.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 2c4b080b7a5dea3d13302d4520d64468 |
| SANs: usefulapi.io, dnsimple.usefulapi.io, *.dnsimple.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dnsimple.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://dnsimple.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://dnsimple.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://dnsimple.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://dnsimple.usefulapi.io/mcp |
| Authorisation server | https://dnsimple.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dnsimple.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://dnsimple.usefulapi.io/mcp | Inconclusive | 401 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
dnsimple_check_domain Check domain availability ~61
Check whether a domain is available to register. Returns { domain, available, premium }. API: GET /{account}/registrar/domains/{domain}/check.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain name to check, e.g. example.com. |
No output schema declared.
No examples provided.
dnsimple_create_zone_record Create a zone record ~183
Create a new DNS record in a zone. Additive — it adds a record without touching existing ones. API: POST /{account}/zones/{zone}/records.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Record content, e.g. an IP for A, a hostname for CNAME. |
| name | string | yes | Record name = the subdomain part WITHOUT the domain. Use "" (empty string) for the apex/root. |
| priority | integer | – | Priority, for MX/SRV records. |
| regions | array | – | Regions to publish the record in (e.g. ["global"]). |
| ttl | integer | – | Time-to-live in seconds. |
| type | string | yes | Record type, e.g. A, AAAA, CNAME, MX, TXT, NS. |
| zone | string | yes | Zone name, e.g. example.com. |
No output schema declared.
No examples provided.
dnsimple_delete_zone_record Delete a zone record ~77
Delete a DNS record from a zone. WARNING: permanently removes a live DNS record. API: DELETE /{account}/zones/{zone}/records/{record}. Returns 204 (no body).
| Name | Type | Req | Description |
|---|---|---|---|
| record | integer | yes | Numeric record id to delete. |
| zone | string | yes | Zone name, e.g. example.com. |
No output schema declared.
No examples provided.
dnsimple_get_domain Get a domain ~50
Retrieve a single domain by name or id. API: GET /{account}/domains/{domain}.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name (e.g. example.com) or numeric domain id. |
No output schema declared.
No examples provided.
dnsimple_get_domain_prices Get domain prices ~58
Retrieve the registration, renewal, and transfer prices for a domain. API: GET /{account}/registrar/domains/{domain}/prices.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain name to price, e.g. example.com. |
No output schema declared.
No examples provided.
dnsimple_get_zone_record Get a zone record ~64
Retrieve a single DNS record in a zone by its numeric id. API: GET /{account}/zones/{zone}/records/{record}.
| Name | Type | Req | Description |
|---|---|---|---|
| record | integer | yes | Numeric record id. |
| zone | string | yes | Zone name, e.g. example.com. |
No output schema declared.
No examples provided.
dnsimple_list_contacts List contacts ~86
List the contacts in the account (used as domain registrants). API: GET /{account}/contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). |
| per_page | integer | – | Results per page (max 100). |
| sort | string | – | Sort order, e.g. "label:asc", "email:asc", "id:desc". |
No output schema declared.
No examples provided.
dnsimple_list_domains List domains ~122
List the domains in the account, with pagination and optional filters. API: GET /{account}/domains.
| Name | Type | Req | Description |
|---|---|---|---|
| name_like | string | – | Filter to domains whose name contains this substring. |
| page | integer | – | Page number (1-based). |
| per_page | integer | – | Results per page (max 100). |
| registrant_id | integer | – | Filter to domains with this registrant (contact) id. |
| sort | string | – | Sort order, e.g. "name:asc", "expiration:desc", "id:desc". |
No output schema declared.
No examples provided.
dnsimple_list_zone_records List zone records ~162
List the DNS records in a zone, with pagination and optional filters. API: GET /{account}/zones/{zone}/records.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Filter by exact record name (subdomain part). |
| name_like | string | – | Filter by record name substring. |
| page | integer | – | Page number (1-based). |
| per_page | integer | – | Results per page (max 100). |
| sort | string | – | Sort order, e.g. "name:asc", "type:asc", "content:desc". |
| type | string | – | Filter by record type, e.g. A, AAAA, CNAME, MX, TXT. |
| zone | string | yes | Zone name, e.g. example.com. |
No output schema declared.
No examples provided.
dnsimple_list_zones List zones ~99
List the DNS zones in the account, with pagination and optional filters. API: GET /{account}/zones.
| Name | Type | Req | Description |
|---|---|---|---|
| name_like | string | – | Filter to zones whose name contains this substring. |
| page | integer | – | Page number (1-based). |
| per_page | integer | – | Results per page (max 100). |
| sort | string | – | Sort order, e.g. "name:asc", "id:desc". |
No output schema declared.
No examples provided.
dnsimple_update_zone_record Update a zone record ~148
Update an existing DNS record. WARNING: mutates LIVE DNS — changing content/ttl takes effect for real resolution. Only the fields you provide are sent. API: PATCH /{account}/zones/{zone}/records/{record}.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | New record content. |
| name | string | – | New record name (subdomain part; "" for apex). |
| priority | integer | – | New priority, for MX/SRV records. |
| record | integer | yes | Numeric record id to update. |
| regions | array | – | New regions list. |
| ttl | integer | – | New TTL in seconds. |
| zone | string | yes | Zone name, e.g. example.com. |
No output schema declared.
No examples provided.
dnsimple_whoami Who am I ~41
Identify the authenticated account/user for the current API token. Use this to discover your account id (data.account.id). API: GET /whoami.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.usefulapi/dnsimple MCP server?
io.usefulapi/dnsimple is an MCP server listed in the public MCP registry as io.usefulapi/dnsimple. MCP server for DNSimple, domains, DNS zone records, availability, pricing and contacts. This page covers its hosted endpoint (https://dnsimple.usefulapi.io/mcp).
Is the io.usefulapi/dnsimple MCP server safe to use?
io.usefulapi/dnsimple scores 86 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 io.usefulapi/dnsimple MCP server expose?
io.usefulapi/dnsimple exposes 12 tools: dnsimple_whoami, dnsimple_list_domains, dnsimple_get_domain, dnsimple_list_zone_records, dnsimple_get_zone_record, and 7 more. Their descriptions and schemas cost roughly 1,151 tokens of context every time the server is loaded.
Does the io.usefulapi/dnsimple MCP server require authentication?
Yes. io.usefulapi/dnsimple 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 io.usefulapi/dnsimple MCP server still maintained?
io.usefulapi/dnsimple is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.