Skip to content

deSEC MCP by usefulapi

io.usefulapi/desecusefulapi.iostreamable-httpv1.27.4Scanned

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.

Tools: 2 delete, 0 irreversible, 1 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 7
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

3 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 deSEC MCP by usefulapi can do

The deSEC MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 7 tools. It can delete or cancel things (2 tools: desec_create_rrset and desec_replace_rrset) and create or change data (1 tool: desec_export_zonefile). 4 tools only read.

7 tools bring in text other people can write (desec_list_domains, desec_get_domain, desec_export_zonefile and 4 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.27.4.

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.

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.Reads text others writeNo 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).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.Reads text others writeNo 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).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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).Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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 4Show 4 read-only tools
  • 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.Reads text others writeNo findings

    Why it is in this group

    • The name "desec_get_domain" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.Reads text others writeNo findings

    Why it is in this group

    • The name "desec_get_rrset" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.Reads text others writeNo findings

    Why it is in this group

    • The name "desec_list_domains" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.Reads text others writeNo findings

    Why it is in this group

    • The name "desec_list_rrsets" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.

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 private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write7
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.

The remote endpoint did not answer the last look

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

  1. 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: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://desec.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://desec.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.

  1. 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: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://desec.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://desec.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.27.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http desec https://desec.usefulapi.io/mcp
claude mcp add --transport http desec https://desec.usefulapi.io/mcp

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

.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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as desec. Review it before you use it.

Capability tags behind 7 rules
  • mcp__desec__desec_list_domains untrusted-input
  • mcp__desec__desec_get_domain untrusted-input
  • mcp__desec__desec_export_zonefile untrusted-input
  • mcp__desec__desec_list_rrsets untrusted-input
  • mcp__desec__desec_get_rrset untrusted-input
  • mcp__desec__desec_create_rrset untrusted-input
  • mcp__desec__desec_replace_rrset untrusted-input

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/desec/verify?hash=62f75bf3fe15fe72d40462fa1f073cce389b10311a72441050762db5ea4d84ab" | jq -e '.changed == false'

Pinned hash 62f75bf3fe15, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/desec/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/desec
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/desec.svg)](https://radar.anlyon.com/servers/io.usefulapi/desec)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

deSEC MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the deSEC MCP by usefulapi safe?

No scan can promise that. What its definitions show: 7 tools, 3 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 deSEC MCP by usefulapi delete data?

Yes. 2 tools can delete, cancel or revoke something: desec_create_rrset and desec_replace_rrset.

Can the deSEC 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 deSEC MCP by usefulapi have?

7 tools: 2 destructive, 1 write, 4 read. desec_create_rrset, desec_replace_rrset, desec_export_zonefile, desec_list_domains, desec_get_domain, desec_list_rrsets and desec_get_rrset.

Does the deSEC MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the deSEC 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 deSEC MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.