SimpleACME DNS-01 setup MCP server
com.simpleacme/dns-setupsimpleacme.comstreamable-httpv1.0.0Scanned
Read-only DNS-01 setup guides and templates for Traefik, win-acme, Certbot and custom hooks.
4 tools: 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the SimpleACME DNS-01 setup MCP server can do
The SimpleACME DNS-01 setup MCP server is published by simpleacme.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: generate_update_script and build_client_config), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 2 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 8, 2026, version 1.0.0.
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.
4 tools
Changes things 2Claude Code: ask
build_client_configBuild placeholder-only client configuration for a public hostname; never supply credentials1 finding
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.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...ion for a public hostname; never supply credentials"
Description, as the server wrote it Build placeholder-only client configuration for a public hostname; never supply credentials
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
generate_update_scriptGenerate a placeholder-only Bash or PowerShell DNS update starter; does not run it1 finding
Why it is in this group
- The name "generate_update_script" says "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "generate_update_script" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_update_script" says "generate": a word for a change.
Description, as the server wrote it Generate a placeholder-only Bash or PowerShell DNS update starter; does not run it
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
get_service_infoGet public SimpleACME service facts and limitationsNo findings
Why it is in this group
- The name "get_service_info" says "get": a word for reading.
Description, as the server wrote it Get public SimpleACME service facts and limitations
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_setup_guideGet public integration guidance for a supported ACME clientNo findings
Why it is in this group
- The name "get_setup_guide" says "get": a word for reading.
Description, as the server wrote it Get public integration guidance for a supported ACME client
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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 untrusted-input or outbound.
- Reads private data0
- 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 16, 2026, 14:20 UTC, unchanged since Nov 9, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://simpleacme.com/mcp: tools/list returned 4 tools to an anonymous client, including generate_update_script (write), build_client_config (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "generate_update_script" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_update_script" says "generate": a word for a change.
The description mentions "credentials".
What this check looks forMatched text
description: "...ion for a public hostname; never supply credentials"
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http dns-setup https://simpleacme.com/mcpclaude mcp add --transport http dns-setup https://simpleacme.com/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__dns-setup__get_service_info",
"mcp__dns-setup__get_setup_guide"
],
"ask": [
"mcp__dns-setup__generate_update_script",
"mcp__dns-setup__build_client_config"
],
"deny": []
}
}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 dns-setup. Review it before you use it.
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/com.simpleacme/dns-setup/verify?hash=4bef5f2a0dfc167ed68b027375ca44e8870240d17de53df4e18baea4b8778f24" | jq -e '.changed == false'Pinned hash 4bef5f2a0dfc, from Nov 8, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.simpleacme/dns-setup/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.simpleacme/dns-setup)Source: MCP Registry. Synced Nov 8, 2026, 15:17 UTC.
SimpleACME DNS-01 setup MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SimpleACME DNS-01 setup MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 2 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 SimpleACME DNS-01 setup MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the SimpleACME DNS-01 setup MCP server 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 SimpleACME DNS-01 setup MCP server have?
- 4 tools: 2 write, 2 read. generate_update_script, build_client_config, get_service_info and get_setup_guide.
Does the SimpleACME DNS-01 setup MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the SimpleACME DNS-01 setup MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the SimpleACME DNS-01 setup MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.