Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/mikusnuz/dynadot-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/mikusnuz/dynadot-mcp/dynadot)<a href="https://agentmods.dev/mcp/mikusnuz/dynadot-mcp/dynadot"><img src="https://agentmods.dev/badge/mcp/mikusnuz/dynadot-mcp/dynadot/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/mikusnuz/dynadot-mcp/dynadot"><img src="https://agentmods.dev/badge/mcp/mikusnuz/dynadot-mcp/dynadot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dynadot scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"dynadot": {
"command": "npx",
"args": [
"-y",
"dynadot-mcp"
],
"env": {
"DYNADOT_API_KEY": "",
"DYNADOT_SANDBOX": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 13 lines scan A f13065763416
dynadot is an MCP server published in the GitHub repository mikusnuz/dynadot-mcp (1 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
whois-mcp-server
Domain registration, availability, DNS records, and IP/ASN resolution via RDAP and DNS-over-HTTPS. Runs locally from the @cyanheads/whois-mcp-server npm package. Needs 5 environment variables to run.
domain-whois
MCP server "domain-whois" as configured in kemalabuteliyte/domain-whois-mcp. Runs locally from the github:kemalabuteliyte/domain-whois-mcp npm package.
kubeview
Read-only Model Context Protocol MCP server enabling code-driven AI analysis of Kubernetes clusters. Runs locally from the kubeview-mcp npm package. Needs 24 environment variables to run.
pihole-mcp
MCP server for Pi-hole v6 API — manage multiple instances: queries, lists, groups, stats. Runs locally from the @ranklancer/pihole-mcp npm package. Needs 3 environment variables to run.
cloudflare
MCP server to manage Cloudflare Workers, KV, R2, Pages, DNS, and cache from your IDE. Runs locally from the mcp-server-cloudflare-dns npm package.
infomaniak-mcp-agent
Unofficial MCP server for Infomaniak (web hosting, mail, DNS, kDrive, SSL, AI). 54 tools. Runs locally from the infomaniak-mcp-agent npm package. Needs 4 environment variables to run.