Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.mikusnuz/dynadot

NPM · DYNADOT-MCP

MCP server for Dynadot domain registrar — domain search, registration, DNS, and transfers

Available components

0 this week 79 Trust /100

Last scanned (14 hours ago)

Scores higher than 63% of npm servers

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 4642 tokens (~66/item across 70 items; 67 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_domain" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 68 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 15 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 14 Nov 26 0
    • Stability: 0.97 → pass security
  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 10 Nov 26 −1
    • Security disclosure: fail → unverified ▼ functional
    • Stability: pass → 0.87 functional
  • 9 Nov 26 +5
    • Source repository: unverified → pass ▲ security
  • 8 Nov 26 −5
    • Provenance: pass → unverified ▼ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/dynadot-mcp@1.5.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 67 exposed · ~4,602 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
set_contact_regional_setting ~94

Set region-specific contact settings required by certain TLD registries (EU, Latvia, Lithuania). Pass the appropriate parameters for the region.

NameTypeReqDescription
contact_idstringyesContact ID to configure
paramsobjectyesRegion-specific parameters as key-value pairs
regionstringyesRegion: 'eu' (European Union), 'lv' (Latvia), 'lt' (Lithuania)

No output schema declared.

No examples provided.

set_dns ~239

Set DNS records for a domain using Dynadot's DNS service. Supports main records and up to 100 subdomain records. Use the records parameter to pass Dynadot API parameters like main_record_type0, main_record0, subdomain0, sub_record_type0, sub_record0, etc. Existing DNS is replaced unless add_dns_to_current_setting is '1'; an empty records object clears records.

NameTypeReqDescription
domainstringyesDomain name to set DNS for
recordsobjectyesDNS record parameters as key-value pairs. Keys follow Dynadot API3 set_dns2 naming: main_record_type0..19 (a/aaaa/cname/forward/txt/mx/stealth/email), main_record0..19 (value), main_recordx0..19 (MX…

No output schema declared.

No examples provided.

set_dnssec ~210

Set or clear DNSSEC for a domain. Provide either a DS record (key_tag, digest_type, digest, algorithm) or a DNSKEY (flags, public_key, algorithm). To disable, set clear to true without key fields.

NameTypeReqDescription
algorithmstring–DNSSEC algorithm number (e.g., '13' for ECDSAP256SHA256)
clearboolean–Set to true to remove DNSSEC from the domain
digeststring–DS digest in hexadecimal
digest_typestring–DS digest type: 1=SHA-1, 2=SHA-256, 3=GOST, 4=SHA-384
domainstringyesDomain name to configure DNSSEC for
flagsstring–DNSSEC flags (e.g., '257' for KSK)
key_tagstring–DS key tag (0-65535)
public_keystring–DNSSEC public key

No output schema declared.

No examples provided.

set_domain_note ~63

Set a note and/or move a domain to a folder for organization.

NameTypeReqDescription
domainstringyesDomain name to update
folderstring–Folder name or ID to move the domain into
notestring–Note to attach to the domain

No output schema declared.

No examples provided.

set_email_forward ~84

Set email forwarding for a domain. Forward emails to existing email addresses or configure MX records.

NameTypeReqDescription
domainstringyesDomain name to configure email forwarding for
paramsobjectyesEmail forwarding parameters. Keys: forward_type ('forward'/'mx'), username0/exist_email0 (for forward type), mx_host0/mx_priority0 (for mx type)

No output schema declared.

No examples provided.

set_folder_settings ~161

Apply default settings to a folder. All domains in the folder will inherit these settings. Supports nameservers, DNS, forwarding, parking, stealth, and renewal options. Pass the appropriate Dynadot API parameters for the setting type.

NameTypeReqDescription
folder_idstringyesFolder ID to configure
paramsobject–Setting parameters as key-value pairs (varies by setting type)
setting_typestringyesType of setting to apply: 'whois' (WHOIS contacts), 'ns' (nameservers), 'dns' (basic DNS), 'dns2' (advanced DNS records), 'forwarding', 'stealth', 'parking', 'hosting', 'email_forward', 'renew_option…

No output schema declared.

No examples provided.

set_for_sale ~73

List a domain for sale on the Dynadot marketplace with a specified price.

NameTypeReqDescription
currencystring–Currency for the price (e.g., 'USD')
domainstringyesDomain name to list for sale
pricestringyesAsking price (e.g., '1000.00')

No output schema declared.

No examples provided.

set_forwarding ~111

Set URL forwarding for a domain. Supports standard forwarding (301/302 redirect) and stealth forwarding (iframe with custom title).

NameTypeReqDescription
domainstringyesDomain name to set forwarding for
is_temporaryboolean–Use 302 (temporary) redirect instead of 301 (permanent)
stealthboolean–Use stealth forwarding (iframe) instead of redirect
stealth_titlestring–Page title for stealth forwarding
urlstringyesTarget URL to forward to

No output schema declared.

No examples provided.

set_hosting ~72

Set website hosting for a domain using Dynadot's built-in hosting service.

NameTypeReqDescription
domainstringyesDomain name to configure hosting for
hosting_typestringyesHosting type: 'advanced' or 'basic'
mobile_viewboolean–Enable mobile-optimized view (advanced hosting only)

No output schema declared.

No examples provided.

set_nameserver_ip ~101

Update IP addresses of a registered nameserver by server_id. The legacy host alias resolves an exact hostname using list_registered_nameservers before updating.

NameTypeReqDescription
hoststring–Legacy hostname alias; use instead of server_id
ipstring–Legacy single-address alias; use instead of ips
ipsarray–Replacement addresses, encoded as ip0..ip9
server_idstring–ID from list_registered_nameservers

No output schema declared.

No examples provided.

set_nameservers ~67

Set nameservers for a domain. Accepts up to 13 nameserver hostnames.

NameTypeReqDescription
domainstringyesDomain name to configure
nameserversarrayyesList of nameserver hostnames (e.g., ['ns1.example.com', 'ns2.example.com'])

No output schema declared.

No examples provided.

set_parking ~49

Enable domain parking for a domain. Parked domains show a placeholder page.

NameTypeReqDescription
domainstringyesDomain name to park
with_adsboolean–Show ads on the parking page

No output schema declared.

No examples provided.

set_privacy ~75

Set WHOIS privacy for a domain. Options: 'full' (hide all info), 'partial' (hide some info), 'off' (show all info).

NameTypeReqDescription
domainstringyesDomain name to set privacy for
optionstringyesPrivacy level: 'full', 'partial', or 'off'

No output schema declared.

No examples provided.

set_renew_option ~66

Set the auto-renewal option for a domain.

NameTypeReqDescription
domainstringyesDomain name to configure
optionstringyesRenewal option: 'auto' (auto-renew), 'donot' (do not renew), 'reset' (reset to default)

No output schema declared.

No examples provided.

set_reseller_verification ~43

Set the WHOIS verification status for a reseller contact.

NameTypeReqDescription
contact_idstringyesContact ID
statusstringyesVerification status to set

No output schema declared.

No examples provided.

set_whois_contacts ~104

Set WHOIS contact information for a domain. Specify contact IDs for registrant, admin, technical, and/or billing contacts.

NameTypeReqDescription
admin_contactstring–Contact ID for the admin contact
billing_contactstring–Contact ID for the billing contact
domainstringyesDomain name to update
registrant_contactstring–Contact ID for the registrant
technical_contactstring–Contact ID for the technical contact

No output schema declared.

No examples provided.

transfer_domain ~96

Initiate a domain transfer into your Dynadot account. Requires the domain name and the authorization/EPP code from the current registrar.

NameTypeReqDescription
auth_codestringyesAuthorization/EPP code from the current registrar
couponstring–Coupon code for discount
domainstringyesDomain name to transfer (e.g., 'example.com')
registrant_contactstring–Contact ID to use as registrant

No output schema declared.

No examples provided.

Install

How do I install the io.github.mikusnuz/dynadot MCP server?

io.github.mikusnuz/dynadot runs locally as an npm package, launched with npx -y dynadot-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · dynadot-mcp

# add to Claude Code
claude mcp add mikusnuz-dynadot -- npx -y dynadot-mcp
Common questions

What is the io.github.mikusnuz/dynadot MCP server?

io.github.mikusnuz/dynadot is an MCP server listed in the public MCP registry as io.github.mikusnuz/dynadot. MCP server for Dynadot domain registrar, domain search, registration, DNS, and transfers. This page covers its npm package (dynadot-mcp).

Is the io.github.mikusnuz/dynadot MCP server safe to use?

io.github.mikusnuz/dynadot scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.mikusnuz/dynadot MCP server expose?

io.github.mikusnuz/dynadot exposes 67 tools: search_domain, register_domain, bulk_register_domains, get_domain_info, list_domains, and 62 more. Their descriptions and schemas cost roughly 4,602 tokens of context every time the server is loaded.

Is the io.github.mikusnuz/dynadot MCP server still maintained?

io.github.mikusnuz/dynadot is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.mikusnuz/dynadot MCP server under?

io.github.mikusnuz/dynadot declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.mikusnuz/dynadot MCP server?

VerifyMCP ran 16 checks on io.github.mikusnuz/dynadot, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.