io.github.inkog-io/inkog
NPM · @INKOG-IO/MCP
Security co-pilot for AI agents. Scan for vulnerabilities, audit MCP servers, verify governance.
Available components
Last scanned (9 hours ago)
Scores higher than 61% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 49 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 921 tokens (~131/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 31 Oct 26 0
- CVE-2026-118764 affects this package: high ▼ security
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@inkog-io/mcp@1.0.20
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-g3hv-75wg-m249 | CVE-2026-118764 | medium | yes | |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
inkog_audit_a2a ~134
Audit Agent-to-Agent (A2A) communications in multi-agent systems. Detects infinite delegation loops, privilege escalation, data leakage between agents, and unauthorized handoffs. Supports Google A2A protocol, CrewAI, LangGraph, and AutoGen. Use this when building or reviewing multi-agent systems to detect delegation vulnerabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| check_delegation_chains | boolean | – | Check for infinite delegation loops and unauthorized handoffs |
| path | string | yes | Path to multi-agent system codebase |
| protocol | string | – | Multi-agent protocol hint (optional, will auto-detect if not specified) |
No output schema declared.
No examples provided.
inkog_audit_mcp_server ~97
Security audit any MCP server from the registry or GitHub. Analyzes tool permissions, data flow risks, input validation, and potential vulnerabilities. Use this before installing any new MCP server to verify it is safe.
| Name | Type | Req | Description |
|---|---|---|---|
| repository_url | string | – | Direct GitHub repository URL to audit |
| server_name | string | – | MCP server name from registry (e.g., "github", "slack", "postgres") |
No output schema declared.
No examples provided.
inkog_compliance_report ~134
Generate a compliance report for EU AI Act, NIST AI RMF, ISO 42001, or OWASP LLM Top 10. Analyzes agent code and maps findings to regulatory requirements. Use this when preparing AI agents for regulatory compliance or audit.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format: markdown (default), json, or pdf |
| framework | string | – | Compliance framework: eu-ai-act (default), nist-ai-rmf, iso-42001, owasp-llm-top-10, or all |
| path | string | yes | Path to scan for compliance analysis |
No output schema declared.
No examples provided.
inkog_explain_finding ~127
Get detailed explanation and remediation guidance for a security finding or pattern. Includes what the issue is, why it's dangerous, step-by-step fixes, and code examples. Use this after scanning to understand how to fix security findings.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | – | Finding ID from scan results (e.g., "f8a3b2c1") |
| pattern | string | – | Pattern name: prompt-injection, infinite-loop, sql-injection-llm, token-bombing, hardcoded-credentials, missing-rate-limits, recursive-delegation, etc. |
No output schema declared.
No examples provided.
inkog_generate_mlbom ~113
Generate a Machine Learning Bill of Materials (MLBOM) for AI agents. Lists all models, tools, data sources, frameworks, and dependencies. Supports CycloneDX and SPDX formats. Use this when documenting AI agent dependencies for supply chain compliance.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format: cyclonedx (recommended), spdx, or json |
| include_vulnerabilities | boolean | – | Include known vulnerabilities for detected components |
| path | string | yes | Path to agent codebase to analyze |
No output schema declared.
No examples provided.
inkog_scan ~217
Security co-pilot for AI agent development. Scans for prompt injection, infinite loops, token bombing, SQL injection via LLM, and missing guardrails. Supports LangChain, CrewAI, LangGraph, AutoGen, n8n, and 20+ agent frameworks. Use this whenever building, reviewing, or deploying AI agents to catch security issues before they reach production.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | Agent name for dashboard identification (auto-detected from path if not provided) |
| filter | string | – | File filtering: auto (detect agent repos, adapt filtering), agent-only (aggressive filtering), all (no filtering) |
| output | string | – | Output format: summary (default), detailed (full findings), sarif (for CI/CD) |
| path | string | yes | File or directory path to scan |
| policy | string | – | Security policy: low-noise (proven vulnerabilities only), balanced (default), comprehensive (all findings), governance (Article 14 focused), eu-ai-act (compliance mode) |
No output schema declared.
No examples provided.
inkog_verify_governance ~99
Validate that AGENTS.md declarations match actual code behavior. Detects governance mismatches like 'read-only declared but code writes data' or 'human approval required but no approval gates in code'. Essential for EU AI Act Article 14 compliance. Use this whenever an AI agent project has an AGENTS.md file, or to verify governance compliance before deployment.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to directory containing AGENTS.md and agent code |
No output schema declared.
No examples provided.
How do I install the io.github.inkog-io/inkog MCP server?
io.github.inkog-io/inkog runs locally as an npm package, launched with npx -y @inkog-io/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @inkog-io/mcp
claude mcp add inkog-io-inkog -- npx -y @inkog-io/mcp
What is the io.github.inkog-io/inkog MCP server?
io.github.inkog-io/inkog is an MCP server listed in the public MCP registry as io.github.inkog-io/inkog. Security co-pilot for AI agents. Scan for vulnerabilities, audit MCP servers, verify governance. This page covers its npm package (@inkog-io/mcp).
Is the io.github.inkog-io/inkog MCP server safe to use?
io.github.inkog-io/inkog scores 79 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.inkog-io/inkog MCP server expose?
io.github.inkog-io/inkog exposes 7 tools: inkog_scan, inkog_verify_governance, inkog_compliance_report, inkog_explain_finding, inkog_audit_mcp_server, and 2 more. Their descriptions and schemas cost roughly 921 tokens of context every time the server is loaded.
Is the io.github.inkog-io/inkog MCP server still maintained?
io.github.inkog-io/inkog is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.inkog-io/inkog MCP server under?
io.github.inkog-io/inkog declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.