Server providing Argo CD integration for MCP clients.
Nothing to run from here
OnlyDNS is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
100/100
trust score
17
tools declared
local
runs on your machine
—
downloads a day
What it does
Model Context Protocol server for OnlyDNS to manage DNS zones, records, DNSSEC, and TSIG keys.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'ONLYDNS_API_TOKEN=${ONLYDNS_API_TOKEN}' --transport stdio onlydns-mcp '--' npx -y @onlydns/mcp
# 2 — ask your agent for something these tools do
# get_dnssec, enable_dnssec, disable_dnssec and 14 more
It needs ONLYDNS_API_TOKEN: this reads it from your environment, so export it first.
OnlyDNS costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ONAll 1 server
Onlydns1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts OnlyDNS as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads ONLYDNS_API_TOKEN (OnlyDNS API Bearer token for authentication) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx ONLYDNS_API_TOKEN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'ONLYDNS_API_TOKEN=${ONLYDNS_API_TOKEN}' --transport stdio onlydns-mcp '--' npx -y @onlydns/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: ONLYDNS_API_TOKEN — OnlyDNS API Bearer token for authentication. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Get DNSSEC configuration status, NSEC3 parameters, and DS / DNSKEY keys for a domain.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domainName | string | yes | Domain name (e.g. example.com) |
Enable DNSSEC signing for a domain in OnlyDNS.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domainName | string | yes | Domain name (e.g. example.com) |
Disable DNSSEC signing and remove DNSSEC keys for a domain in OnlyDNS.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domainName | string | yes | Domain name (e.g. example.com) |
List all DNS domains managed in the OnlyDNS account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | number | no | Maximum number of domains to return (default: 200, max: 1000) |
| offset | number | no | Pagination offset (default: 0) |
Create/add a new DNS zone/domain under the OnlyDNS account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domainName | string | yes | Domain name to create (e.g. example.com) |
List all DNS records for a domain, with optional filtering by record type (A, AAAA, CNAME, MX, TXT, etc.) or hostname.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domainName | string | yes | The domain name to list records for (e.g. example.com) |
| type | string | no | Filter by record type (e.g. A, AAAA, CNAME, MX, TXT, SRV, CAA, NS) |
| name | string | no | Filter by record name/hostname. Accepts relative subdomain (e.g. "testing", "@", "www"), domain-qualified name (e.g. "testing.example.com"), or full canonical FQDN (e.g. "testing.example.com."). |
Add a DNS record to a domain. Accepts relative hostnames (e.g. "testing"), domain-qualified names (e.g. "testing.example.com"), or canonical FQDNs (e.g. "testing.example.com."). If a record with the same name and type already exists, the new value is appended to the record set.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domainName | string | yes | Domain name (e.g. example.com) |
| name | string | yes | Record name/subdomain. Accepts relative name (e.g. "testing", "www", "@"), domain-qualified name (e.g. "testing.example.com"), or full canonical FQDN (e.g. "testing.example.com."). Canonicalization is |
| type | string | yes | DNS record type (e.g. A, AAAA, CNAME, MX, TXT, SRV, CAA, NS, URL, PROXY) |
| value | yes | Record content/value (e.g. "1.2.3.4", "v=spf1 include:... ~all", "10 mail.example.com"). Can be a single string or array of strings. | |
| ttl | number | no | Time to live in seconds (default: 300) |
Update an existing DNS record set for a given name and type, completely replacing its values and/or TTL. Accepts relative names (e.g. "testing"), domain-qualified names (e.g. "testing.example.com"), or canonical FQDNs (e.g. "testing.example.com.").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domainName | string | yes | Domain name (e.g. example.com) |
| name | string | yes | Record name/subdomain to update. Accepts relative name (e.g. "testing", "www", "@"), domain-qualified name (e.g. "testing.example.com"), or full canonical FQDN (e.g. "testing.example.com."). Canonical |
| type | string | yes | DNS record type to update (e.g. A, CNAME, TXT) |
| value | yes | New value(s) for the record. Overwrites existing values for this name and type. | |
| ttl | number | no | Optional new TTL in seconds (keeps existing TTL if not specified) |
Delete a DNS record or specific value from a domain. Accepts relative names (e.g. "testing"), domain-qualified names (e.g. "testing.example.com"), or canonical FQDNs (e.g. "testing.example.com.").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domainName | string | yes | Domain name (e.g. example.com) |
| name | string | yes | Record name/subdomain to delete. Accepts relative name (e.g. "testing", "www", "@"), domain-qualified name (e.g. "testing.example.com"), or full canonical FQDN (e.g. "testing.example.com."). Canonical |
| type | string | yes | Record type to delete (e.g. A, CNAME, TXT) |
| value | string | no | Specific record value to delete. If omitted, all values for this name and type are deleted. |
Completely replace ALL DNS records in a zone with a new list of records. Warning: destructive if omitted records are intended to be preserved.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domainName | string | yes | Domain name (e.g. example.com) |
| records | array | yes | Complete list of replacement DNS records |
List all TSIG keys configured for the OnlyDNS account.
No parameter schema on file.
Get details for a specific TSIG key by name.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyName | string | yes | TSIG key name (e.g. key-12345) |
Generate a new TSIG key for secondary DNS transfers (AXFR) or dynamic DNS updates.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| algorithm | string | no | TSIG algorithm (default: hmac-sha256) |
Get TSIG keys and permissions (AXFR transfers, dynamic DNS updates, subdomain restrictions) configured for a domain.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domainName | string | yes | Domain name (e.g. example.com) |
Attach and configure TSIG permissions (AXFR transfer / dynamic DNS updates / subdomain restrictions) for a domain.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domainName | string | yes | Domain name (e.g. example.com) |
| keyName | string | yes | TSIG key name |
| allowAxfr | boolean | yes | Whether to allow AXFR zone transfers for this domain using this key |
| allowDnsUpdate | boolean | yes | Whether to allow RFC 2136 DNS updates for this domain using this key |
| subdomains | array | no | Optional list of allowed subdomains (e.g. ["_acme_challenge"]). If specified, dynamic DNS updates are restricted to these subdomains. |
Remove all TSIG keys associated with a domain.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domainName | string | yes | Domain name (e.g. example.com) |
Delete a TSIG key by name
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install OnlyDNS or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 100 / 100
Release 1.0.6 · scanned 31 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest3a65af9123c0e7406545d064471eee9676bea9d52df6a1e8e207fa015c5ca275
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (16 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_dnssec | no tags | |
| enable_dnssec | no tags | |
| disable_dnssec | no tags | |
| list_domains | no tags | |
| create_domain | no tags | |
| list_records | no tags | |
| add_record | no tags | |
| update_record | no tags | |
| delete_record | no tags | |
| set_records | no tags | |
| list_tsig_keys | no tags | |
| get_tsig_key | no tags | |
| create_tsig_key | no tags | |
| get_domain_tsig | no tags | |
| configure_domain_tsig | no tags | |
| remove_domain_tsig | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest3a65af9123c0e740
Scanned2026-10-31
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.6. Pin a release below and the command asks for exactly that one.
1.0.6
30 Oct 2026
latestNo release note was published with this version.
1.0.5
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish OnlyDNS can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.