MCP MeasureMCP Measure

index observed

deSEC MCP by usefulapi

Read deSEC domains, DNSSEC keys, zone files and RRsets; create or replace one DNS record set.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
99%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~2,089Tokens (tool definitions)
~2.0 KBTypical response size
Moderate attention impact (1.63% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "desec": {
      "url": "https://desec.usefulapi.io/mcp"
    }
  }
}

Remote endpoints

https://desec.usefulapi.io/mcpstreamable-http

What it can do

Tool inventory

Tools (7)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢desec_list_domains(owns_qname, cursor)

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/.

Input Schema

{
  "type": "object",
  "properties": {
    "owns_qname": {
      "description": "Only the domain that is authoritative for this DNS name (the longest matching zone you own).",
      "type": "string",
      "minLength": 1,
      "maxLength": 253
    },
    "cursor": {
      "description": "Opaque cursor from a previous reply's next_cursor. Omit for the first page.",
      "type": "string",
      "maxLength": 500
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢desec_get_domain(domain)

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}/.

Input Schema

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Domain name in this deSEC account, e.g. example.com (see desec_list_domains)."
    }
  },
  "required": [
    "domain"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢desec_export_zonefile(domain)

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/.

Input Schema

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Domain name in this deSEC account, e.g. example.com (see desec_list_domains)."
    }
  },
  "required": [
    "domain"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢desec_list_rrsets(domain, type, subname, cursor)

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/.

Input Schema

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Domain name in this deSEC account, e.g. example.com (see desec_list_domains)."
    },
    "type": {
      "description": "Only RRsets of this type, e.g. A, MX, TXT.",
      "type": "string",
      "pattern": "^[A-Za-z0-9]{1,20}$"
    },
    "subname": {
      "description": "Only RRsets at this subname (\"\" or \"@\" = the zone apex). Omit to include every subname.",
      "type": "string",
      "maxLength": 178
    },
    "cursor": {
      "description": "Opaque cursor from a previous reply's next_cursor. Omit for the first page.",
      "type": "string",
      "maxLength": 500
    }
  },
  "required": [
    "domain"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢desec_get_rrset(domain, subname, type)

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}/.

Input Schema

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Domain name in this deSEC account, e.g. example.com (see desec_list_domains)."
    },
    "subname": {
      "description": "Subname relative to the domain: \"www\", \"_443._tcp.www\", \"*\" for a wildcard. Empty or \"@\" = the zone apex. Never the full name.",
      "type": "string",
      "maxLength": 178
    },
    "type": {
      "type": "string",
      "pattern": "^[A-Za-z0-9]{1,20}$",
      "description": "Record type, e.g. A, AAAA, CNAME, MX, TXT, CAA, SRV, TLSA."
    }
  },
  "required": [
    "domain",
    "type"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴desec_create_rrset(domain, subname, type, ttl, records)

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/.

Input Schema

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Domain name in this deSEC account, e.g. example.com (see desec_list_domains)."
    },
    "subname": {
      "description": "Subname relative to the domain: \"www\", \"_443._tcp.www\", \"*\" for a wildcard. Empty or \"@\" = the zone apex. Never the full name.",
      "type": "string",
      "maxLength": 178
    },
    "type": {
      "type": "string",
      "enum": [
        "A",
        "AAAA",
        "CAA",
        "CNAME",
        "HTTPS",
        "LOC",
        "MX",
        "NAPTR",
        "NS",
        "OPENPGPKEY",
        "PTR",
        "SMIMEA",
        "SPF",
        "SRV",
        "SSHFP",
        "SVCB",
        "TLSA",
        "TXT",
        "URI"
      ],
      "description": "Record type (uppercase). DNSSEC types and SOA are managed by deSEC and cannot be written."
    },
    "ttl": {
      "type": "integer",
      "minimum": 1,
      "maximum": 86400,
      "description": "TTL in seconds, at most 86400. Not below the domain's minimum_ttl (usually 3600): deSEC rejects lower values."
    },
    "records": {
      "minItems": 1,
      "maxItems": 100,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 4000
      },
      "description": "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\\\"\")."
    }
  },
  "required": [
    "domain",
    "type",
    "ttl",
    "records"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴desec_replace_rrset(domain, subname, type, ttl, records)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Domain name in this deSEC account, e.g. example.com (see desec_list_domains)."
    },
    "subname": {
      "description": "Subname relative to the domain: \"www\", \"_443._tcp.www\", \"*\" for a wildcard. Empty or \"@\" = the zone apex. Never the full name.",
      "type": "string",
      "maxLength": 178
    },
    "type": {
      "type": "string",
      "enum": [
        "A",
        "AAAA",
        "CAA",
        "CNAME",
        "HTTPS",
        "LOC",
        "MX",
        "NAPTR",
        "NS",
        "OPENPGPKEY",
        "PTR",
        "SMIMEA",
        "SPF",
        "SRV",
        "SSHFP",
        "SVCB",
        "TLSA",
        "TXT",
        "URI"
      ],
      "description": "Record type (uppercase). DNSSEC types and SOA are managed by deSEC and cannot be written."
    },
    "ttl": {
      "type": "integer",
      "minimum": 1,
      "maximum": 86400,
      "description": "TTL in seconds, at most 86400. Not below the domain's minimum_ttl (usually 3600): deSEC rejects lower values."
    },
    "records": {
      "minItems": 1,
      "maxItems": 100,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 4000
      },
      "description": "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\\\"\")."
    }
  },
  "required": [
    "domain",
    "type",
    "ttl",
    "records"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded7 tools