deSEC MCP by usefulapi
by usefulapi.io · remote · no sign-in to list tools · v1.3.3 · published by io.usefulapi
Read deSEC domains, DNSSEC keys, zone files and RRsets; create or replace one DNS record set.
7 tools: 2 can delete or cancel things, 1 change things and 4 only read.
Scanned Oct 21, 2026
- Deletes or cancels2Claude Code: deny: see these tools
- Can't be undone0Claude Code: ask
- Changes things1Claude Code: ask: see these tools
- Only reads4Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http desec https://desec.usefulapi.io/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
7 tools
Deletes or cancels 2Claude Code: deny
desec_create_rrsetWRITE: create ONE new RRset (a set of DNS records of one type at one name) in a domain.No findings
Why it is in this group
- The name "desec_create_rrset" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it WRITE: create ONE new RRset (a set of DNS records of one type at one name) in a domain. It goes live in DNS immediately and a wrong record can take a site or mail offline. Fails if an RRset with this subname and type already exists (use desec_replace_rrset for that) or if a CNAME would conflict with other records. Never touches the apex NS or DNSSEC records and cannot delete anything. Subject to deSEC's write limits (15/min, 300/day per domain). POST /domains/{name}/rrsets/.
Annotations the server declares
- title: Create RRset
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
desec_replace_rrsetWRITE (overwrites): set ONE RRset to exactly the given TTL and records, creating it if it does not exist and REPLACING all its current records if it does.No findings
Why it is in this group
- The name "desec_replace_rrset" says "replace": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it WRITE (overwrites): set ONE RRset to exactly the given TTL and records, creating it if it does not exist and REPLACING all its current records if it does. It goes live in DNS immediately; a wrong value can take a site or mail offline. The previous RRset is read first and returned as `previous` so the change can be undone with another call. An empty record list is refused (this tool never deletes), and the apex NS and DNSSEC records cannot be changed. Subject to deSEC's write limits (15/min, 300/day per domain). PUT /domains/{name}/rrsets/ with a one-element array.
Annotations the server declares
- title: Replace RRset
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
Changes things 1Claude Code: ask
desec_export_zonefileThe whole zone as a plain-text BIND-format zonefile (all RRsets except DNSSEC types).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 The whole zone as a plain-text BIND-format zonefile (all RRsets except DNSSEC types). Handy as a backup before changing records. Counts as an expensive deSEC operation (300/min). GET /domains/{name}/zonefile/.
Annotations the server declares
- title: Export zonefile
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
Only reads 4Claude Code: allow
desec_get_domainOne domain with its DNSSEC key material: the DNSKEY and the DS records to publish at the registrar for the chain of trust, plus minimum TTL and publication times.No findings
Why it is in this group
- The name "desec_get_domain" says "get": a word for reading.
Description, as the server wrote it One domain with its DNSSEC key material: the DNSKEY and the DS records to publish at the registrar for the chain of trust, plus minimum TTL and publication times. GET /domains/{name}/.
Annotations the server declares
- title: Get domain
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
desec_get_rrsetOne RRset by subname and type, e.g.No findings
Why it is in this group
- The name "desec_get_rrset" says "get": a word for reading.
Description, as the server wrote it One RRset by subname and type, e.g. the A records of "www" or the MX records of the apex. GET /domains/{name}/rrsets/{subname}/{type}/.
Annotations the server declares
- title: Get RRset
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
desec_list_domainsList the DNS domains (zones) in this deSEC account, newest first, with creation and last-published times and minimum TTL.No findings
Why it is in this group
- The name "desec_list_domains" says "list": a word for reading.
Description, as the server wrote it List the DNS domains (zones) in this deSEC account, newest first, with creation and last-published times and minimum TTL. DNSSEC keys are omitted here (see desec_get_domain). Use owns_qname to find which of your domains is responsible for a DNS name (for example before adding a record for www.dev.example.net). Up to 500 per page. GET /domains/.
Annotations the server declares
- title: List domains
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
desec_list_rrsetsList the DNS records of a domain as RRsets (all records of one name and type, sharing one TTL), newest first.No findings
Why it is in this group
- The name "desec_list_rrsets" says "list": a word for reading.
Description, as the server wrote it List the DNS records of a domain as RRsets (all records of one name and type, sharing one TTL), newest first. Filter by type and/or subname. Up to 500 per page. GET /domains/{name}/rrsets/.
Annotations the server declares
- title: List RRsets
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: 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.
Install
Pinned to version 1.3.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http desec https://desec.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__desec__desec_list_domains",
"mcp__desec__desec_get_domain",
"mcp__desec__desec_list_rrsets",
"mcp__desec__desec_get_rrset"
],
"ask": [
"mcp__desec__desec_export_zonefile"
],
"deny": [
"mcp__desec__desec_create_rrset",
"mcp__desec__desec_replace_rrset"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as desec. Review it before you use it.