Eurodns MCP server
io.github.JigSawFr/eurodns-mcp·v0.11.0·1 starsModel Context Protocol server for the EuroDNS User API — domains, DNS zones, subscriptions and SSL.
1 stars37 downloads/wk
Reviews
Write oneNobody has reviewed Eurodns yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Eurodns tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
eurodns_dns_diff_zoneAdds one DNS record to the zone domainName, or updates the existing record with the same
Public scan report
scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it
- Code scan87 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Eurodns compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 68% of 4,461 AI and agents servers
- Tools
- 1
- the typical AI and agents server has 6
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 1
- more than 50% of 2,713 AI and agents servers
- Downloads a week
- 37
- more than 27% of 1,554 AI and agents servers with a package
What its tools let an agent do: 1 read
Install Eurodns in Claude Code, Cursor or VS Code
Runs npx -y @jigsawfr/eurodns-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add eurodns-mcp -- npx -y @jigsawfr/eurodns-mcp
What the publisher says
From the Eurodns repository's README, as published. We do not edit it. Read it on GitHub
eurodns-mcp
Manage your domains, DNS zones and subscriptions by asking for it.
A Model Context Protocol server for the EuroDNS User API — domains, DNS zones, contacts, subscriptions, SSL, invoices and orders.
Documentation · Tools · Guardrails · Deploying
This is an independent open-source project. It is **not affiliated with, endorsed by, or
supported by EuroDNS**. "EuroDNS" is used only to identify the API this server talks to.
Written by a professional engineer with AI assistance. Every line was reviewed before it
was committed, and the responsibility for what it does is human.
What you get
pair, profile create/update pair, on/off toggle and per-product read folded into one tool; 55 tools once billing and irreversible operations are enabled.
- Full API coverage in 36 tools — every one of the 79 API operations, with each list/get
returns, when to prefer its neighbour and when not to, what it does that the annotations cannot say, where an id comes from. A test holds the whole surface to it, and a workflow runs the registries' own linter over it.
- Every tool and argument described for the model that reads them: what it does and
browsable, and one that says what this deployment allows — including why a tool you expected is not in the list.
- Three DNS workflow tools that make record edits safe, because saving a zone replaces it.
- Guardrails so a deployment can refuse operations that spend money or destroy things.
- Four prompts for the workflows worth naming, and two resources: the portfolio,
still serves 2025-era clients, which is most of them today.
- Two transports — stdio for a local client, streamable HTTP for a shared deployment.
- Both protocol eras on one endpoint — speaks the 2026-07-28 revision natively and
- OAuth 2.1 or a shared token on HTTP, with an audit line per call.
- Queryable history — ask the server what has been done, and by whom.
- 1Password Connect as an optional source for any secret it reads.
How it works
flowchart TD
client(["MCP client"])
client -->|stdio| registry
client -->|streamable HTTP| origin
subgraph http ["HTTP transport only"]
origin["Origin check"] --> bearer["Bearer token<br/>OAuth 2.1 or shared secret"]
bearer --> scopes["Scope gate"]
end
scopes --> registry["Tool registry"]
registry --> guard{"Guardrails<br/>read-only, billing, destructive"}
guard -->|refused| deny["Error naming the setting to change"]
guard -->|allowed| api[("EuroDNS User API")]
op[("1Password Connect")] -.->|"op:// refs, at startup"| creds["Credentials"]
creds -.-> api
registry -.-> log[("Audit log")]
guard -.-> log
log -.->|eurodns_audit_query| clientShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Eurodns: common questions
- Is Eurodns MCP server safe?
- Mostly: it is graded B (83/100). Read the Eurodns safety report
- How do I install Eurodns?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Eurodns need an API key?
- Yes. The registry entry asks for
EURODNS_APP_ID,EURODNS_API_KEY. - Is Eurodns maintained?
- The last commit was 22 days ago (2026-10-14). The latest release is v0.11.0.
- How does Eurodns compare with other AI and agents MCP servers?
- safety score 83/100 (higher than 68% of 4,461 AI and agents servers); tools 1 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.