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.
npx agentmods add mcp/coderifts/api-governance/api-governance-openai-coderiftsgit clone --depth 1 https://github.com/coderifts/api-governanceWrote 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/coderifts/api-governance/api-governance-openai-coderifts)<a href="https://agentmods.dev/mcp/coderifts/api-governance/api-governance-openai-coderifts"><img src="https://agentmods.dev/badge/mcp/coderifts/api-governance/api-governance-openai-coderifts.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
coderifts 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 2d 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
{
"coderifts": {
"type": "http",
"url": "https://app.coderifts.com/mcp",
"headers": {
"Authorization": "Bearer ${CODERIFTS_API_KEY}"
}
}
}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.
- 2d ago First seen · 9 lines scan A 11be9483d161
coderifts is an MCP server published in the GitHub repository coderifts/api-governance (0 stars, last pushed 2d 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
delimit-mcp-server
API governance for AI coding assistants. Breaking changes, policies, cross-model context. Runs locally from the delimit-cli npm package.
driftwatch
What broke between two dependency versions, with a citation for every claim. No API key needed. Runs locally from the driftwatch-mcp npm package. Needs 1 environment variable to run.
semver-checks
Detect breaking changes in your TypeScript library's public API and recommend the SemVer bump. Runs locally from the semver-checks npm package.
specshield-mcp-server
The API-change deploy gate for AI coding agents. Read-only breaking-change detection. Runs locally from the specshield-mcp-server npm package. Needs 4 environment variables to run.
bumpguard
Guard your dependency bumps: an MCP server that tells your AI agent exactly which parts of YOUR code break when you upgrade a dependency, and verifies AI-written code against the API that's actually installed — by static analysis, never by running third-party code. Runs locally from the bumpguard-mcp Python package.
blastradius
Dependency blast-radius analyzer: before you upgrade an npm package, see exactly which of YOUR files and functions touch its changed API surface. Runs locally from the @justfeltlikerunning/blastradius npm package.