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/inkog-io/inkog-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/inkog-io/inkog-mcp/inkog)<a href="https://agentmods.dev/mcp/inkog-io/inkog-mcp/inkog"><img src="https://agentmods.dev/badge/mcp/inkog-io/inkog-mcp/inkog/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/inkog-io/inkog-mcp/inkog"><img src="https://agentmods.dev/badge/mcp/inkog-io/inkog-mcp/inkog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
inkog 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
{
"inkog": {
"command": "npx",
"args": [
"-y",
"@inkog-io/mcp"
],
"env": {
"INKOG_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.
- 2mo ago First seen · 12 lines scan A 772572974667
inkog is an MCP server published in the GitHub repository inkog-io/inkog-mcp (3 stars, last pushed 1mo 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
zyrax-guard
Audit AI agent configs for prompt injection & rogue MCP servers; vet packages. Runs locally from the zyrax-guard npm package.
pinner-mcp-stdio-server
MCP server "pinner-mcp-stdio-server" as configured in safedep/vet. Runs in Docker (ghcr.io/safedep/pinner-mcp:latest).
mcp-server-vibes-coded
Agent supply-chain security, scanner consensus, x402 reliability, and commerce MCP tools. Remote server at vibes-coded-mcp-production.up.railway.app.
kernel
Open proof-required execution kernel for consequential actions. Runs locally from the actenon-kernel Python package.
matrixscroll
MCP server for signed machine-action records, offline tool-surface checks, with device-agnostic custody and CNSA 2.0 Category 5 crypto (ML-DSA-87, ML-KEM-1024). Runs locally from the matrixscroll Python package.
skill-audit-mcp
Scan agent skills and MCP servers for malicious patterns before you load them. Remote server at eltociear-skill-audit.hf.space.