io.github.mikusnuz/dynadot
NPM · DYNADOT-MCP · SCANNED SEP 22
MCP server for Dynadot domain registrar — domain search, registration, DNS, and transfers
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 47 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 4425 tokens (~63/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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add mikusnuz-dynadot -- npx -y dynadot-mcp
{
"mcpServers": {
"mikusnuz-dynadot": {
"command": "npx",
"args": [
"-y",
"dynadot-mcp"
]
}
}
} {
"servers": {
"mikusnuz-dynadot": {
"command": "npx",
"args": [
"-y",
"dynadot-mcp"
]
}
}
} codex mcp add mikusnuz-dynadot -- npx -y dynadot-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mikusnuz-dynadot": {
"type": "local",
"command": [
"npx",
"-y",
"dynadot-mcp"
],
"enabled": true
}
}
} openclaw mcp add mikusnuz-dynadot --command npx --arg -y --arg dynadot-mcp
mcp_servers:
mikusnuz-dynadot:
command: "npx"
args: ["-y", "dynadot-mcp"] {
"McpServers": {
"mikusnuz-dynadot": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"dynadot-mcp"
]
}
}
} assistant mcp add mikusnuz-dynadot -t stdio -c npx -a -y dynadot-mcp
{
"mcpServers": {
"mikusnuz-dynadot": {
"command": "npx",
"args": [
"-y",
"dynadot-mcp"
]
}
}
} 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
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 22 Sept 2026 · Analysed npm/dynadot-mcp@1.3.1
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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | Contact ID to configure |
| params | object | yes | Region-specific parameters as key-value pairs |
| region | string | yes | Region: 'eu' (European Union), 'lv' (Latvia), 'lt' (Lithuania) |
No output schema declared.
No examples provided.
set_dns ~219
Set DNS records for a domain using Dynadot's DNS service. Supports main records and up to 10 subdomains. Use the records parameter to pass Dynadot API parameters like main_record_type, main_record, subdomain0, sub_record_type0, sub_record0, etc.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to set DNS for |
| records | object | yes | DNS 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 ~126
Set or clear DNSSEC for a domain. To enable, provide flags, algorithm, and public_key. To disable, set clear to true.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | DNSSEC algorithm number (e.g., '13' for ECDSAP256SHA256) |
| clear | boolean | – | Set to true to remove DNSSEC from the domain |
| domain | string | yes | Domain name to configure DNSSEC for |
| flags | string | – | DNSSEC flags (e.g., '257' for KSK) |
| public_key | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to update |
| folder | string | – | Folder name or ID to move the domain into |
| note | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to configure email forwarding for |
| params | object | yes | Email 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.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | string | yes | Folder ID to configure |
| params | object | – | Setting parameters as key-value pairs (varies by setting type) |
| setting_type | string | yes | Type 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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency for the price (e.g., 'USD') |
| domain | string | yes | Domain name to list for sale |
| price | string | yes | Asking 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).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to set forwarding for |
| is_temporary | boolean | – | Use 302 (temporary) redirect instead of 301 (permanent) |
| stealth | boolean | – | Use stealth forwarding (iframe) instead of redirect |
| stealth_title | string | – | Page title for stealth forwarding |
| url | string | yes | Target 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to configure hosting for |
| hosting_type | string | yes | Hosting type: 'advanced' or 'basic' |
| mobile_view | boolean | – | Enable mobile-optimized view (advanced hosting only) |
No output schema declared.
No examples provided.
set_nameserver_ip ~43
Update the IP address of an existing registered nameserver.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Nameserver hostname to update |
| ip | string | yes | New IP address |
No output schema declared.
No examples provided.
set_nameservers ~67
Set nameservers for a domain. Accepts up to 13 nameserver hostnames.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to configure |
| nameservers | array | yes | List 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to park |
| with_ads | boolean | – | 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).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to set privacy for |
| option | string | yes | Privacy level: 'full', 'partial', or 'off' |
No output schema declared.
No examples provided.
set_renew_option ~66
Set the auto-renewal option for a domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to configure |
| option | string | yes | Renewal 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.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | Contact ID |
| status | string | yes | Verification 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.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_contact | string | – | Contact ID for the admin contact |
| billing_contact | string | – | Contact ID for the billing contact |
| domain | string | yes | Domain name to update |
| registrant_contact | string | – | Contact ID for the registrant |
| technical_contact | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_code | string | yes | Authorization/EPP code from the current registrar |
| coupon | string | – | Coupon code for discount |
| domain | string | yes | Domain name to transfer (e.g., 'example.com') |
| registrant_contact | string | – | Contact ID to use as registrant |
No output schema declared.
No examples provided.
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 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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,385 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 22 September 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.