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/nach-dakwale/domaincheckr-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/nach-dakwale/domaincheckr-mcp/domaincheckr)<a href="https://agentmods.dev/mcp/nach-dakwale/domaincheckr-mcp/domaincheckr"><img src="https://agentmods.dev/badge/mcp/nach-dakwale/domaincheckr-mcp/domaincheckr/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/nach-dakwale/domaincheckr-mcp/domaincheckr"><img src="https://agentmods.dev/badge/mcp/nach-dakwale/domaincheckr-mcp/domaincheckr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
domaincheckr 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 11d 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
{
"domaincheckr": {
"url": "https://domaincheckr.fly.dev/mcp",
"type": "streamable-http"
}
}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.
- 11d ago First seen · 6 lines scan A 6326fc5dd186
domaincheckr is an MCP server published in the GitHub repository nach-dakwale/domaincheckr-mcp (0 stars, last pushed 6mo 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
domain-search-mcp
Fast domain availability checker with pricing comparison and AI-powered suggestions. Runs locally from the domain-search-mcp npm package. Needs 4 environment variables to run.
rdap
RDAP — Registration Data Access Protocol (domains, IPs, ASNs) via IANA bootstrap. Remote server at gateway.pipeworx.io.
domscan
Domain intelligence for DNS, WHOIS/RDAP, TLS, reputation, valuation, and brand protection. Remote server at domscan.net.
canyougrab
MCP server for confidence-scored domain availability checking via CanYouGrab.it. Runs locally from the mcp-server-canyougrab Python package.
domain-radar
MCP server that checks domain availability in real-time during brand naming. Runs locally from the mcp-domain-radar npm package.
strata
MCP server for progressive tool usage at any scale (see https://klavis.ai). Remote server at strata.klavis.ai.