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/yacb2/domaintomeWrote 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/yacb2/domaintome/domaintome-dt)<a href="https://agentmods.dev/mcp/yacb2/domaintome/domaintome-dt"><img src="https://agentmods.dev/badge/mcp/yacb2/domaintome/domaintome-dt/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/yacb2/domaintome/domaintome-dt"><img src="https://agentmods.dev/badge/mcp/yacb2/domaintome/domaintome-dt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dt 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
{
"dt": {
"command": "uvx",
"args": [
"--from",
"domaintome",
"dt",
"mcp"
]
}
}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 First seen · 11 lines scan A 0a96f92aa1c4
dt is an MCP server published in the GitHub repository yacb2/domaintome (0 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
wenlan
MCP server "wenlan" as configured in wenlan-app/wenlan. Launched with ./bin/wenlan-mcp-runner.sh.
kiagent
Your mail, chats and documents indexed into a local SQLite corpus, served to AI clients over MCP. Remote server at {subdomain}.localkiagent.com.
cortex
MCP server "cortex" as configured in tools-for-agents/cortex. Runs locally from the @tools-for-agents/cortex npm package.
world-model
Event-sourced world model for multi-LLM agents: propose, validate, and read a shared state. Remote server at insidedcpulse.com.
better-memory-mcp
MCP server "better-memory-mcp" as configured in guinacio/better-memory-mcp. Runs locally from the @guinacio/better-memory-mcp npm package.
lain
High-performance knowledge graph MCP server for AI coding agents with semantic search. Runs locally from the @spuentesp/lain-mcp npm package.