deSEC MCP by usefulapi
Server Details
Read deSEC domains, DNSSEC keys, zone files and RRsets; create or replace one DNS record set.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
TDQS
Score is being calculated.
Available Tools
7 toolsdesec_create_rrsetCreate RRsetDestructiveInspect
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/.
| Name | Required | Description | Default |
|---|---|---|---|
| ttl | Yes | TTL in seconds, at most 86400. Not below the domain's minimum_ttl (usually 3600): deSEC rejects lower values. | |
| type | Yes | Record type (uppercase). DNSSEC types and SOA are managed by deSEC and cannot be written. | |
| domain | Yes | Domain name in this deSEC account, e.g. example.com (see desec_list_domains). | |
| records | Yes | Record contents in zone-file format, at least one (an empty list would delete the RRset and is refused). Names need a trailing dot ("10 mx.example.com."), TXT needs quotes ("\"v=spf1 -all\""). | |
| subname | No | Subname relative to the domain: "www", "_443._tcp.www", "*" for a wildcard. Empty or "@" = the zone apex. Never the full name. |
desec_export_zonefileExport zonefileRead-onlyInspect
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/.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name in this deSEC account, e.g. example.com (see desec_list_domains). |
desec_get_domainGet domainRead-onlyInspect
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}/.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name in this deSEC account, e.g. example.com (see desec_list_domains). |
desec_get_rrsetGet RRsetRead-onlyInspect
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}/.
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | Record type, e.g. A, AAAA, CNAME, MX, TXT, CAA, SRV, TLSA. | |
| domain | Yes | Domain name in this deSEC account, e.g. example.com (see desec_list_domains). | |
| subname | No | Subname relative to the domain: "www", "_443._tcp.www", "*" for a wildcard. Empty or "@" = the zone apex. Never the full name. |
desec_list_domainsList domainsRead-onlyInspect
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/.
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | Opaque cursor from a previous reply's next_cursor. Omit for the first page. | |
| owns_qname | No | Only the domain that is authoritative for this DNS name (the longest matching zone you own). |
desec_list_rrsetsList RRsetsRead-onlyInspect
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/.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Only RRsets of this type, e.g. A, MX, TXT. | |
| cursor | No | Opaque cursor from a previous reply's next_cursor. Omit for the first page. | |
| domain | Yes | Domain name in this deSEC account, e.g. example.com (see desec_list_domains). | |
| subname | No | Only RRsets at this subname ("" or "@" = the zone apex). Omit to include every subname. |
desec_replace_rrsetReplace RRsetDestructiveIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| ttl | Yes | TTL in seconds, at most 86400. Not below the domain's minimum_ttl (usually 3600): deSEC rejects lower values. | |
| type | Yes | Record type (uppercase). DNSSEC types and SOA are managed by deSEC and cannot be written. | |
| domain | Yes | Domain name in this deSEC account, e.g. example.com (see desec_list_domains). | |
| records | Yes | Record contents in zone-file format, at least one (an empty list would delete the RRset and is refused). Names need a trailing dot ("10 mx.example.com."), TXT needs quotes ("\"v=spf1 -all\""). | |
| subname | No | Subname relative to the domain: "www", "_443._tcp.www", "*" for a wildcard. Empty or "@" = the zone apex. Never the full name. |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
7 tool updates
- First observed
desec_create_rrset - First observed
desec_export_zonefile - First observed
desec_get_domain - First observed
desec_get_rrset - First observed
desec_list_domains - First observed
desec_list_rrsets - First observed
desec_replace_rrset
Related MCP Connectors
Read NS1 zones, records, monitors, data feeds and usage; create or update one DNS record.
1Read devices, users, keys, ACLs and DNS for a tailnet; manage devices, routes and auth keys.
Read apps and environments, and create them, on the fortrabbit PHP hosting platform.
Signed internet telemetry, read-only: DNS, TLS, WHOIS, reachability. Every record Ed25519-signed.
Related MCP Servers
- AlicenseBqualityBmaintenanceEnables users to inspect and manage domains, DNS records (including A, AAAA, CNAME, MX, TXT and more), HTTP forwards, invoices and dynamic DNS through a hosting provider's API, with previewed change plans, conflict detection, backups and independent readback before writes. Offers DNS shortcuts such as website setup, verification records, bulk IP replacement, zone import/export and backup restore, exposed via local stdio or authenticated Streamable HTTP for a central gateway.27MIT
- FlicenseNot gradedqualityBmaintenanceManages DNS records and Cloudflare Tunnels for a Cloudflare zone via the Cloudflare API. Supports listing, creating, updating, and deleting DNS records, as well as tunnel lifecycle operations.6 npm-
- AlicenseBqualityCmaintenanceProvides typed tools for DNS, zone, and cache management plus a universal passthrough to any Cloudflare API v4 endpoint, with confirmation required for destructive operations.8MIT
- AlicenseAqualityAmaintenanceAn MCP server for managing Hetzner DNS zones and RRSets via the Hetzner Cloud API. It enables listing, creating, updating, deleting, importing/exporting zone files, and managing protection and TTLs from MCP clients.2268 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.