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/jacobsd32-cpu/djd-agent-score-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/jacobsd32-cpu/djd-agent-score-mcp/djd-agent-score)<a href="https://agentmods.dev/mcp/jacobsd32-cpu/djd-agent-score-mcp/djd-agent-score"><img src="https://agentmods.dev/badge/mcp/jacobsd32-cpu/djd-agent-score-mcp/djd-agent-score/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/jacobsd32-cpu/djd-agent-score-mcp/djd-agent-score"><img src="https://agentmods.dev/badge/mcp/jacobsd32-cpu/djd-agent-score-mcp/djd-agent-score.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
djd-agent-score 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 2mo 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
{
"djd-agent-score": {
"command": "npx",
"args": [
"-y",
"djd-agent-score-mcp"
],
"env": {
"DJD_BASE_URL": "",
"DJD_TIMEOUT_MS": ""
}
}
}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.
- 2mo ago First seen · 13 lines scan A 78371b8eecb1
djd-agent-score is an MCP server published in the GitHub repository jacobsd32-cpu/djd-agent-score-mcp (1 stars, last pushed 8mo 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
chainstack
Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds. Remote server at mcp.chainstack.com.
whale-data-mcp
Signed settled outcomes (Polymarket, sports) + whale signals as agent tools, paid via x402. Runs locally from the @predge/whale-data-mcp npm package. Needs 7 environment variables to run.
agent-trust
Trustless XRPL escrow oracle for AI agents. Create jobs, verify work, release XRP/RLUSD payments. Runs locally from the @eamwhite1/agenttrust-sdk npm package.
xrpl-referee
XRPL escrow for agent-to-agent payments: hire, prove, AI-audit, auto-pay on PASS. Remote server at mcp.cryptovault.co.uk.
chainweb
MCP server "chainweb" as configured in Pact-Community-Organization/pact-mcp. Runs ./packages/mcp-chainweb/dist/bin.js with node. Needs 5 environment variables to run.
chainweb
Chainweb HTTP API: local sim, pre-signed send, poll, table reads, SPV proofs, module deploys. Runs locally from the @pact-community/mcp-chainweb npm package. Needs 5 environment variables to run.