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/OrtaMarco/domain-security-mcp-serverWrote 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/ortamarco/domain-security-mcp-server/domain-security)<a href="https://agentmods.dev/mcp/ortamarco/domain-security-mcp-server/domain-security"><img src="https://agentmods.dev/badge/mcp/ortamarco/domain-security-mcp-server/domain-security/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/ortamarco/domain-security-mcp-server/domain-security"><img src="https://agentmods.dev/badge/mcp/ortamarco/domain-security-mcp-server/domain-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
domain-security 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 1mo 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
{
"domain-security": {
"command": "npx",
"args": [
"-y",
"domain-security-mcp-server"
]
}
}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.
- 1mo ago Changed · +1 lines b37da584b09b
- 1mo ago First seen · 8 lines scan A 8d3e655e646b
domain-security is an MCP server published in the GitHub repository OrtaMarco/domain-security-mcp-server (1 stars, last pushed 8d 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
dns-doctor
MCP server "dns-doctor", hosted remotely at dnsdoctor.dev, as configured in dnsdoctor/claude-plugin.
palisade
Monitor and manage email authentication (SPF, DKIM, DMARC, MTA-STS, BIMI) for your domains. Runs locally from the @palisadeemail/mcp npm package. Needs 1 environment variable to run.
mcp
DMARC analytics for AI assistants: SPF/DKIM, compliance, anomalies, p=reject readiness, onboarding. Remote server at mcp.dmarkoff.com.
dns-mcp
MCP server "dns-mcp" as configured in mclose/dns-mcp. Runs in Docker (docker.io/mclose/dns-mcp:1.3.4).
dns-aid
DNS-based Agent Identification and Discovery - Reference Implementation. Runs locally from the dns-aid Python package. Needs 1 environment variable to run.
porkbun
MCP server "porkbun", hosted remotely at mcp.porkbun.com, as configured in oborseth/Porkbun-MCP.