Skip to main content
Glama

Inkog MCP Server

Security companion for AI agent development in Claude, Cursor, and Claude Code.

Ask your AI pair-programmer to build an agent. Inkog checks it as you code — scanning for vulnerabilities, explaining findings in plain English, verifying AGENTS.md governance, and auditing agent-to-agent delegation. All inside the same conversation, no context switch.

Available in Claude Desktop, Cursor, Claude Code, ChatGPT, and any MCP-compatible client.

npm version License MCP Compatible

The Dev-Flow Loop

Inkog is designed to live inside the conversation where you build the agent — not as a post-hoc gate:

  1. Ask Claude to build a piece of agent logic.

  2. Ask Claude to scan it with Inkog — "Scan this with Inkog and show me any CRITICAL or HIGH findings."

  3. Ask Claude to explain each finding in plain English — "Explain the top finding. What's the risk, and how do I fix it?"

  4. Ask Claude to apply the fixes. Review the diff, approve, re-scan.

  5. Before shipping, verify governance — "Verify my AGENTS.md against the code" and "Audit the agent-to-agent delegation".

Read the full walkthrough: Building Secure AI Agents with Claude Code and the Inkog MCP.

  • "Scan the current directory with Inkog and show me any CRITICAL or HIGH findings."

  • "Explain the top finding in plain English. What's the risk, and how do I fix it?"

  • "Verify my AGENTS.md against the code."

  • "Audit the agent-to-agent delegation in this crew."

  • "Run a compliance report and map the findings to EU AI Act Articles 12, 14, and 15."

  • "Audit the MCP servers I'm integrating with."

Related MCP server: AgentAudit

When to Use Inkog

  • Building an AI agent — Scan during development to catch infinite loops, prompt injection, and missing guardrails before they ship

  • Adding security to CI/CD — Add inkog-io/inkog@v1 to GitHub Actions for automated security gates on every PR

  • Preparing for EU AI Act — Generate compliance reports mapping your agent to Article 14, NIST AI RMF, OWASP LLM Top 10

  • Reviewing agent code — Use from Claude Code, Cursor, or any MCP client to get security analysis while you code

  • Auditing MCP servers — Check any MCP server for tool poisoning, privilege escalation, or data exfiltration before installing

  • Verifying AGENTS.md — Validate that governance declarations match actual code behavior

  • Building multi-agent systems — Detect delegation loops, privilege escalation, and unauthorized handoffs between agents

What Inkog Does

  • Logic Flaw Detection: Find infinite loops, recursion risks, and missing exit conditions

  • Security Analysis: Detect prompt injection paths, unconstrained tools, and data leakage risks

  • AGENTS.md Governance: Validate that code behavior matches governance declarations

  • Compliance Reporting: Generate reports for EU AI Act, NIST AI RMF, OWASP LLM Top 10

  • MCP Server Auditing: Audit any MCP server before installation

  • Multi-Agent Analysis: Audit Agent-to-Agent communications for logic and security issues

Installation

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "inkog": {
      "command": "npx",
      "args": ["-y", "@inkog-io/mcp"],
      "env": {
        "INKOG_API_KEY": "sk_live_your_api_key"
      }
    }
  }
}

Cursor

Add to your Cursor MCP settings:

{
  "mcpServers": {
    "inkog": {
      "command": "npx",
      "args": ["-y", "@inkog-io/mcp"],
      "env": {
        "INKOG_API_KEY": "sk_live_your_api_key"
      }
    }
  }
}

Global Installation

npm install -g @inkog-io/mcp

Getting Your API Key

  1. Sign up for free at app.inkog.io

  2. Copy your API key from the dashboard

  3. Set it as INKOG_API_KEY environment variable

Available Tools

P0 - Core Analysis (Essential)

Tool

Description

inkog_scan

Static analysis for logic flaws and security risks

inkog_verify_governance

Validate AGENTS.md declarations match actual code behavior

P1 - Enterprise Features

Tool

Description

inkog_compliance_report

Generate EU AI Act, NIST, OWASP compliance reports

inkog_explain_finding

Get detailed remediation guidance for findings

inkog_audit_mcp_server

Audit any MCP server before installation

inkog_generate_mlbom

Generate ML Bill of Materials (CycloneDX, SPDX)

P2 - Multi-Agent Analysis

Tool

Description

inkog_audit_a2a

Audit Agent-to-Agent communications

Tool Details

inkog_scan

Static analysis for AI agent code - finds logic flaws and security risks.

Arguments:
  path     (required) File or directory path to scan
  policy   (optional) Analysis policy: low-noise, balanced, comprehensive, governance, eu-ai-act
  output   (optional) Output format: summary, detailed, sarif

Example: "Scan my LangChain agent for logic flaws"

inkog_verify_governance

Validate that AGENTS.md declarations match actual code behavior. This is Inkog's unique differentiator - no other tool does governance verification.

Arguments:
  path     (required) Path to directory containing AGENTS.md and agent code

Example: "Verify my agent's governance declarations"

inkog_compliance_report

Generate compliance reports for regulatory frameworks.

Arguments:
  path      (required) Path to scan
  framework (optional) eu-ai-act, nist-ai-rmf, iso-42001, owasp-llm-top-10, all
  format    (optional) markdown, json, pdf

Example: "Generate an EU AI Act compliance report for my agent"

inkog_explain_finding

Get detailed explanation and remediation guidance for a security finding.

Arguments:
  finding_id (optional) Finding ID from scan results
  pattern    (optional) Pattern name (e.g., prompt-injection, infinite-loop)

Example: "Explain how to fix prompt injection vulnerabilities"

inkog_audit_mcp_server

Security audit any MCP server from the registry or GitHub.

Arguments:
  server_name    (optional) MCP server name from registry (e.g., "github", "slack")
  repository_url (optional) Direct GitHub repository URL

Example: "Audit the GitHub MCP server for security issues"

inkog_generate_mlbom

Generate a Machine Learning Bill of Materials listing all AI components.

Arguments:
  path                     (required) Path to agent codebase
  format                   (optional) cyclonedx, spdx, json
  include_vulnerabilities  (optional) Include known CVEs (default: true)

Example: "Generate an MLBOM for my AI project"

inkog_audit_a2a

Audit Agent-to-Agent communications for security risks.

Arguments:
  path                    (required) Path to multi-agent codebase
  protocol                (optional) a2a, crewai, langgraph, auto-detect
  check_delegation_chains (optional) Check for infinite loops (default: true)

Example: "Audit my CrewAI multi-agent system for security risks"

Supported Frameworks

Inkog works with all major AI agent frameworks:

  • LangChain / LangGraph

  • CrewAI

  • AutoGen

  • n8n

  • Flowise

  • Dify

  • Microsoft Copilot Studio

  • Custom implementations

Configuration

All configuration is done via environment variables:

Variable

Description

Default

INKOG_API_KEY

Your API key (required)

-

INKOG_API_URL

API base URL

https://api.inkog.io

INKOG_API_VERSION

API version

v1

INKOG_API_TIMEOUT

Request timeout (ms)

30000

INKOG_LOG_LEVEL

Log level

info

INKOG_LOG_FORMAT

Log format (json/text)

json

Development

# Install dependencies
npm install

# Build
npm run build

# Run in development mode
npm run dev

# Run tests
npm test

# Lint
npm run lint

Why Inkog?

Security in the Dev-Flow, Not After It

Most AI agent security tools run after the code is written. Inkog lives inside the conversation where you build the agent — so findings get fixed before they land in a PR, not three weeks later.

The Only Tool with AGENTS.md Verification

Inkog is the only tool that can validate your agent's governance declarations against its actual code behavior. This is essential for:

  • EU AI Act Article 14 compliance (human oversight)

  • Enterprise governance requirements

  • Preventing governance drift as code evolves

Purpose-Built for AI Agents

Unlike traditional code scanners (Snyk, Semgrep, SonarQube), Inkog understands AI-specific issues:

  • Infinite loops and recursion risks

  • Prompt injection paths

  • Unconstrained tool access

  • Missing exit conditions

  • Cross-tenant data leakage

Multi-Framework Support

Inkog's Universal IR (Intermediate Representation) works with any agent framework. Add one integration, get analysis for all frameworks.

License

Apache-2.0 - see LICENSE


Built with security by Inkog.io

Available Tools

10 tools
inkog_audit_a2aA

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.

Inputs: path (required), protocol, check_delegation_chains.

inkog_audit_mcp_serverA

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.

Inputs: server_name, repository_url.

inkog_compliance_reportA

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.

Inputs: path (required), framework, format.

inkog_deep_scanA

Inkog Deep scan for AI agents. Uses advanced analysis to detect complex vulnerabilities, logic flaws, and security issues that pattern-based scanning may miss. Requires the Inkog Deep role. IMPORTANT: Deep scans typically take around 10 minutes — inform the user before starting and let them know the scan is running.

Inputs: path (required), agent_name.

inkog_explain_findingA

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.

Inputs: finding_id, pattern.

inkog_generate_mlbomA

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.

Inputs: path (required), format, include_vulnerabilities.

inkog_mcp_scanA

Scan MCP servers from registry or by repository URL for security vulnerabilities. Detects tool poisoning, command injection, data exfiltration, prompt injection, excessive permissions, obfuscation, supply chain risks, and more. Maps findings to OWASP Agentic Top 10 and OWASP MCP Top 10. Set deep=true for AI-powered deep analysis (~10 min, catches novel threats). For skill package scanning, use inkog_skill_scan instead.

Inputs: server_name, repository_url, deep.

inkog_scanA

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.

Inputs: path (required), agent_name, policy, output, +1 more.

inkog_skill_scanA

Scan SKILL.md packages and agent tool definitions for security vulnerabilities. Detects tool poisoning, command injection, data exfiltration, prompt injection, excessive permissions, obfuscation, supply chain risks, and more. Maps findings to OWASP Agentic Top 10 and OWASP MCP Top 10. Set deep=true for AI-powered deep analysis (~10 min, catches novel threats). For MCP server scanning, use inkog_mcp_scan instead.

Inputs: repository_url, path, deep.

inkog_verify_governanceA

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.

Inputs: path (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some overlap between inkog_audit_mcp_server and inkog_mcp_scan, both auditing MCP servers. Descriptions help differentiate, but an agent might still confuse them.

    Naming Consistency5/5

    All tools consistently follow the 'inkog_' prefix with snake_case and descriptive verb-noun combinations, making the naming pattern predictable and clear.

    Tool Count5/5

    With 10 tools, the server is well-scoped for its domain of AI agent security auditing and compliance, offering enough coverage without being overwhelming.

    Completeness4/5

    The tool surface covers scanning agents, MCP servers, skills, A2A, compliance, MLBOM, and governance, but lacks a dedicated tool for scanning prompts or model vulnerabilities, which are minor gaps.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      C
      quality
      D
      maintenance
      Security scanner and MCP server that catches dangerous patterns in MCP servers and AI agent projects, such as leaked secrets, shell execution, and prompt-injection text. Runs as both a CLI and MCP server with CI-friendly severity gates.
      2
      1
      MIT