DNSimple MCP by usefulapi
io.usefulapi/dnsimpleusefulapi.iostreamable-httpv1.41.5Scanned
MCP server for DNSimple — domains, DNS zone records, availability, pricing and contacts.
12 tools: 2 can delete or cancel things, 2 change things and 8 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
4 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the DNSimple MCP by usefulapi can do
The DNSimple MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (2 tools: dnsimple_update_zone_record and dnsimple_delete_zone_record) and create or change data (2 tools: dnsimple_check_domain and dnsimple_create_zone_record). 8 tools only read.
1 tool reads private data (dnsimple_list_contacts).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.41.5.
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.
12 tools
Deletes or cancels 2Claude Code: deny
dnsimple_delete_zone_recordDelete a DNS record from a zone.No findings
Why it is in this group
- The name "dnsimple_delete_zone_record" says "delete": a word for removing or ending something.
- The description says "permanently removes".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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).
Annotations the server declares
- title: Delete a zone record
- readOnlyHint: false
- destructiveHint: true
dnsimple_update_zone_recordUpdate an existing DNS record.No findings
Why it is in this group
- The name "dnsimple_update_zone_record" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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}.
Annotations the server declares
- title: Update a zone record
- readOnlyHint: false
- destructiveHint: true
Changes things 2Claude Code: ask
dnsimple_check_domainCheck whether a domain is available to register.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 Check whether a domain is available to register. Returns { domain, available, premium }. API: GET /{account}/registrar/domains/{domain}/check.
Annotations the server declares
- title: Check domain availability
- readOnlyHint: true
dnsimple_create_zone_recordCreate a new DNS record in a zone.No findings
Why it is in this group
- The name "dnsimple_create_zone_record" says "create": a word for a change.
Description, as the server wrote it Create a new DNS record in a zone. Additive — it adds a record without touching existing ones. API: POST /{account}/zones/{zone}/records.
Annotations the server declares
- title: Create a zone record
- readOnlyHint: false
- destructiveHint: false
Only reads 8Show 8 read-only tools
dnsimple_get_domainRetrieve a single domain by name or id.No findings
Why it is in this group
- The name "dnsimple_get_domain" says "get": a word for reading.
Description, as the server wrote it Retrieve a single domain by name or id. API: GET /{account}/domains/{domain}.
Annotations the server declares
- title: Get a domain
- readOnlyHint: true
dnsimple_get_domain_pricesRetrieve the registration, renewal, and transfer prices for a domain.No findings
Why it is in this group
- The name "dnsimple_get_domain_prices" says "get": a word for reading.
Description, as the server wrote it Retrieve the registration, renewal, and transfer prices for a domain. API: GET /{account}/registrar/domains/{domain}/prices.
Annotations the server declares
- title: Get domain prices
- readOnlyHint: true
dnsimple_get_zone_recordRetrieve a single DNS record in a zone by its numeric id.No findings
Why it is in this group
- The name "dnsimple_get_zone_record" says "get": a word for reading.
Description, as the server wrote it Retrieve a single DNS record in a zone by its numeric id. API: GET /{account}/zones/{zone}/records/{record}.
Annotations the server declares
- title: Get a zone record
- readOnlyHint: true
dnsimple_list_contactsList the contacts in the account (used as domain registrants).Reads private dataNo findings
Why it is in this group
- The name "dnsimple_list_contacts" says "list": a word for reading.
What it can reach
- private-dataThe name "dnsimple_list_contacts" says "list" and "contact": it reads contacts.
- private-dataThe description's first sentence says "list" and "contact": it reads contacts.
Description, as the server wrote it List the contacts in the account (used as domain registrants). API: GET /{account}/contacts.
Annotations the server declares
- title: List contacts
- readOnlyHint: true
dnsimple_list_domainsList the domains in the account, with pagination and optional filters.No findings
Why it is in this group
- The name "dnsimple_list_domains" says "list": a word for reading.
Description, as the server wrote it List the domains in the account, with pagination and optional filters. API: GET /{account}/domains.
Annotations the server declares
- title: List domains
- readOnlyHint: true
dnsimple_list_zone_recordsList the DNS records in a zone, with pagination and optional filters.No findings
Why it is in this group
- The name "dnsimple_list_zone_records" says "list": a word for reading.
Description, as the server wrote it List the DNS records in a zone, with pagination and optional filters. API: GET /{account}/zones/{zone}/records.
Annotations the server declares
- title: List zone records
- readOnlyHint: true
dnsimple_list_zonesList the DNS zones in the account, with pagination and optional filters.No findings
Why it is in this group
- The name "dnsimple_list_zones" says "list": a word for reading.
Description, as the server wrote it List the DNS zones in the account, with pagination and optional filters. API: GET /{account}/zones.
Annotations the server declares
- title: List zones
- readOnlyHint: true
dnsimple_whoamiIdentify the authenticated account/user for the current API token.No findings
Why it is in this group
- The name "dnsimple_whoami" says "whoami": a word for reading.
Description, as the server wrote it Identify the authenticated account/user for the current API token. Use this to discover your account id (data.account.id). API: GET /whoami.
Annotations the server declares
- title: Who am I
- 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 untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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, 19:35 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- 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: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://dnsimple.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://dnsimple.usefulapi.io 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.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://dnsimple.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://dnsimple.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.41.5. Values in angle brackets are yours to fill in.
claude mcp add --transport http dnsimple https://dnsimple.usefulapi.io/mcpclaude mcp add --transport http dnsimple https://dnsimple.usefulapi.io/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__dnsimple__dnsimple_whoami",
"mcp__dnsimple__dnsimple_list_domains",
"mcp__dnsimple__dnsimple_get_domain",
"mcp__dnsimple__dnsimple_list_zone_records",
"mcp__dnsimple__dnsimple_get_zone_record",
"mcp__dnsimple__dnsimple_get_domain_prices",
"mcp__dnsimple__dnsimple_list_zones",
"mcp__dnsimple__dnsimple_list_contacts"
],
"ask": [
"mcp__dnsimple__dnsimple_check_domain",
"mcp__dnsimple__dnsimple_create_zone_record"
],
"deny": [
"mcp__dnsimple__dnsimple_update_zone_record",
"mcp__dnsimple__dnsimple_delete_zone_record"
]
}
}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 dnsimple. Review it before you use it.
Capability tags behind 1 rule
- mcp__dnsimple__dnsimple_list_contacts private-data
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/io.usefulapi/dnsimple/verify?hash=a04d74f98a979a3defb8ff7e2c2411b21a1a6e3c5addbfba4a9c997ee456e531" | jq -e '.changed == false'Pinned hash a04d74f98a97, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/dnsimple/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/dnsimple)Source: MCP Registry · repository. Synced Nov 20, 2026, 20:18 UTC.
DNSimple MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the DNSimple MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 12 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the DNSimple MCP by usefulapi delete data?
- Yes. 2 tools can delete, cancel or revoke something: dnsimple_update_zone_record and dnsimple_delete_zone_record.
Can the DNSimple MCP by usefulapi 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 DNSimple MCP by usefulapi have?
- 12 tools: 2 destructive, 2 write, 8 read. dnsimple_update_zone_record, dnsimple_delete_zone_record, dnsimple_check_domain, dnsimple_create_zone_record, dnsimple_whoami, dnsimple_list_domains, dnsimple_get_domain, dnsimple_list_zone_records and 4 more.
Does the DNSimple MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the DNSimple MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the DNSimple MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.