DNSimple MCP by usefulapi
REMOTE · DNSIMPLE.USEFULAPI.IO
MCP server for DNSimple — domains, DNS zone records, availability, pricing and contacts.
Available components
Last scanned (2 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Cloud Infrastructure
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. 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
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 2 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “add_change_or_delete_a_dns_record” functional
- New prompt “check_if_a_domain_can_be_registered_and_its_prices” functional
- New prompt “list_the_contacts_used_as_domain_registrants” functional
- New prompt “list_the_domains_in_your_account” functional
- New prompt “review_all_dns_records_of_a_zone” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.32.0 → 1.34.0 functional
- Server version: 1.31.0 → 1.32.0 functional
- Server version: 1.30.2 → 1.31.0 functional
- 30 Oct 26 0
- Server version: 1.30.1 → 1.30.2 functional
- Server version: 1.30.0 → 1.30.1 functional
- 29 Oct 26 −1
- Server version: 1.29.0 → 1.30.0 functional
- Server version: 1.28.0 → 1.29.0 functional
- 28 Oct 26 +1
- Server version: 1.26.0 → 1.28.0 functional
- 27 Oct 26 0
- Server version: 1.25.0 → 1.26.0 functional
- 25 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.3 → 1.23.0 functional
- Server version: 1.21.0 → 1.22.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 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 5 Nov 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 | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.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. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
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 | Redirected | 302 | https://usefulapi.io/dnsimple/ |
| http (plaintext) | http://dnsimple.usefulapi.io/mcp | Inconclusive | 302 | http://dnsimple.usefulapi.io/mcp |
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.
How do I install the DNSimple MCP by usefulapi server?
DNSimple MCP by usefulapi 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'
What is the DNSimple MCP by usefulapi server?
DNSimple MCP by usefulapi is 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 DNSimple MCP by usefulapi server safe to use?
DNSimple MCP by usefulapi scores 18 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 DNSimple MCP by usefulapi server expose?
DNSimple MCP by usefulapi 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 DNSimple MCP by usefulapi server require authentication?
Its publisher declares no required credentials for DNSimple MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the DNSimple MCP by usefulapi server still maintained?
DNSimple MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the DNSimple MCP by usefulapi server?
VerifyMCP ran 4 checks on DNSimple MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about DNSimple MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.