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/chaoz23/dmcheckWrote 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/chaoz23/dmcheck/dmcheck)<a href="https://agentmods.dev/mcp/chaoz23/dmcheck/dmcheck"><img src="https://agentmods.dev/badge/mcp/chaoz23/dmcheck/dmcheck/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/chaoz23/dmcheck/dmcheck"><img src="https://agentmods.dev/badge/mcp/chaoz23/dmcheck/dmcheck.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dmcheck 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
{
"dmcheck": {
"command": "uvx",
"args": [
"dmcheck",
"dmcheck",
"dmcheck-mcp"
],
"env": {}
}
}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 a489cadf6ed5
dmcheck is an MCP server published in the GitHub repository chaoz23/dmcheck (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
charactercheck
Experimental read-only derivation of selected D&D Beyond character fields with provenance and findings. Runs locally from the charactercheck Python package.
srdcheck
Deterministic rules verdicts for game-running agents — cited, reproducible, honest about jurisdiction. SRD 5.2.1 is adapter #1. Runs locally from the srdcheck Python package.
dart
MCP server "dart" as configured in iamv4g/dndkit. Launched with fvm dart mcp-server.
vault-graph
MCP server "vault-graph" as configured in mm-weber/loremaester. Runs /workspaces/loremaester/mcp-servers/vault-graph/server.py with python3. Needs 1 environment variable to run.
r2r
MCP server "r2r" as configured in mm-weber/loremaester. Runs /workspaces/loremaester/mcp-servers/r2r-wrapper/r2r_mcp_wrapper.py with python3. Needs 1 environment variable to run.
sourcebooks
MCP server "sourcebooks" as configured in mm-weber/loremaester. Runs /workspaces/loremaester/mcp-servers/sourcebooks/server.py with python3. Needs 1 environment variable to run.