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/icohangar-ops/codesentinelWrote 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/icohangar-ops/codesentinel/codesentinel-mcp)<a href="https://agentmods.dev/mcp/icohangar-ops/codesentinel/codesentinel-mcp"><img src="https://agentmods.dev/badge/mcp/icohangar-ops/codesentinel/codesentinel-mcp/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/icohangar-ops/codesentinel/codesentinel-mcp"><img src="https://agentmods.dev/badge/mcp/icohangar-ops/codesentinel/codesentinel-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
codesentinel-mcp 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
{
"codesentinel-mcp": {
"command": "npx",
"args": [
"-y",
"@cubiczan/codesentinel-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 · 10 lines scan A 8691fa5008eb
codesentinel-mcp is an MCP server published in the GitHub repository icohangar-ops/codesentinel (0 stars, last pushed 18d 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
visualsentinel
Model Context Protocol server for Visual Sentinel website monitoring. Catches pages that look broken even when the site is up: uptime, performance, SSL, DNS, visual regression and content change, from Claude, Cursor, Cline, Continue and any MCP client. Fi. Runs locally from the @visualsentinel/mcp-server npm package.…
rca-mcp
RCA-MCP MCP connector — causal root-cause analysis, 56 tools, works with Claude, Ollama, Groq, OpenAI, Gemini, LangChain and more. Runs locally from the rca-mcp-connector Python package. Needs 2 environment variables to run.
rca-mcp-connector
RCA-MCP MCP connector — causal root-cause analysis, 56 tools, works with Claude, Ollama, Groq, OpenAI, Gemini, LangChain and more. Runs locally from the rca-mcp-connector Python package. Needs 2 environment variables to run.
installed-version-mcp
MCP server that grounds coding agents on the dependency versions ACTUALLY installed in the current project — read from the lockfile and nodemodules — so they stop coding against a blend of every version. Runs locally from the installed-version-mcp npm package.
breaking-changes-mcp
MCP server that gives coding agents accurate, version-to-version breaking-change briefings for any npm package — so migrations stop being hallucinated. Runs locally from the breaking-changes-mcp npm package.
prodlint
Production readiness for vibe-coded apps. 52 checks for security, reliability, and performance. Runs locally from the prodlint npm package.