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/tetracoralla/deterministic-dependency-engineInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/tetracoralla/deterministic-dependency-engine/dependency_engine)<a href="https://agentmods.dev/mcp/tetracoralla/deterministic-dependency-engine/dependency_engine"><img src="https://agentmods.dev/badge/mcp/tetracoralla/deterministic-dependency-engine/dependency_engine/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/tetracoralla/deterministic-dependency-engine/dependency_engine"><img src="https://agentmods.dev/badge/mcp/tetracoralla/deterministic-dependency-engine/dependency_engine.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dependency_engine 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
{
"dependency_engine": {
"command": "node",
"args": [
"./dist/adapters/mcp.js"
],
"cwd": "."
}
}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 · 9 lines scan A 5ae0e4cfe21b
dependency_engine is an MCP server published in the GitHub repository tetracoralla/deterministic-dependency-engine (0 stars, last pushed 11d ago), licensed Apache-2.0. 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
gsheets
Model Context Protocol (MCP) server for Google Sheets API integration. Runs locally from the mcp-gsheets npm package.
dependency_checker
Check for outdated, incorrect, and unused dependencies. Runs locally from the npm-check npm package. Needs 1 environment variable to run.
ideal-harness-guard
MCP server "ideal-harness-guard" as configured in bharat3645/The-Ideal-Harness. Runs dist/guard/cli/index.js with node.
publishready
PublishReady: Deterministic writing control with local-first metrics and AI prose audits. Runs locally from the @veldica/publishready-mcp npm package.
storybook-mcp
MCP server "storybook-mcp", hosted remotely at localhost, as configured in yannbf/mealdrop.
woven
MCP server "woven" as configured in Ducksss/LifeHack-2026. Runs ./node_modules/tsx/dist/cli.mjs with node. Needs 2 environment variables to run.