Skip to Content
IntegrationsMCP Server

MCP Server Integration

Inkog is available as a Model Context Protocol (MCP) server, enabling AI-powered security analysis directly within your favorite AI assistant.

MCP is a universal protocol for AI-tool integration, supported by Claude, ChatGPT, Cursor, VS Code, and more. Learn more about MCP 

Available Tools

When you install the Inkog MCP server, you get access to 7 security tools:

ToolDescription
inkog_scanScan AI agent code for security vulnerabilities
inkog_verify_governanceValidate AGENTS.md declarations match code behavior
inkog_compliance_reportGenerate EU AI Act, NIST, OWASP compliance reports
inkog_explain_findingGet detailed remediation guidance
inkog_audit_mcp_serverSecurity audit any MCP server
inkog_generate_mlbomGenerate ML Bill of Materials
inkog_audit_a2aAudit Agent-to-Agent communications

Installation

Add to your claude_desktop_config.json:

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

Config file location:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Getting Your API Key

Sign up at app.inkog.io

Go to app.inkog.io  and create a free account.

Copy your API key

Navigate to Settings > API Keys and copy your key (starts with sk_live_).

Configure the MCP server

Add your key to the INKOG_API_KEY environment variable in your MCP configuration.

Tool Reference

inkog_scan

Scan AI agent code for security vulnerabilities.

{ "path": "/path/to/your/agent", "policy": "balanced", "output": "summary" }

Arguments:

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

Example prompts:

  • “Scan my LangChain agent for vulnerabilities”
  • “Check this agent for prompt injection risks”
  • “Run a comprehensive security scan on ./my-agent”

inkog_verify_governance

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

{ "path": "/path/to/your/agent" }

Arguments:

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

Example prompts:

  • “Verify my agent’s governance declarations”
  • “Check if my AGENTS.md matches the code”
  • “Validate governance for ./my-crewai-agent”

inkog_compliance_report

Generate compliance reports for regulatory frameworks.

{ "path": "/path/to/your/agent", "framework": "eu-ai-act", "format": "markdown" }

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 prompts:

  • “Generate an EU AI Act compliance report”
  • “Check OWASP LLM Top 10 compliance for my agent”
  • “Create a NIST AI RMF report”

inkog_explain_finding

Get detailed explanation and remediation guidance for a security finding.

{ "pattern": "prompt-injection" }

Arguments:

  • finding_id (optional): Finding ID from scan results
  • pattern (optional): Pattern name like prompt-injection, infinite-loop, token-bombing

Example prompts:

  • “Explain how to fix prompt injection vulnerabilities”
  • “What is token bombing and how do I prevent it?”
  • “Tell me about the infinite-loop vulnerability”

inkog_audit_mcp_server

Security audit any MCP server from the registry or GitHub.

{ "server_name": "github" }

Arguments:

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

Example prompts:


inkog_generate_mlbom

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

{ "path": "/path/to/your/agent", "format": "cyclonedx" }

Arguments:

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

Example prompts:

  • “Generate an MLBOM for my AI project”
  • “Create a CycloneDX bill of materials”
  • “List all AI components and their vulnerabilities”

inkog_audit_a2a

Audit Agent-to-Agent communications for security risks in multi-agent systems. This is Inkog’s unique capability - no other tool detects multi-agent delegation vulnerabilities.

{ "path": "/path/to/your/multi-agent-system", "protocol": "auto-detect" }

Arguments:

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

What it detects:

  • Infinite delegation loops - Agent A delegates to B, B back to A
  • Privilege escalation - Low-trust agent gains high-trust capabilities
  • Unauthorized handoffs - Agents delegating to unapproved external agents
  • Missing audit trails - No logging of inter-agent communication

Example prompts:

  • “Audit my CrewAI crew for delegation loops”
  • “Check for privilege escalation in my multi-agent system”
  • “Analyze the agent topology in ./my-agents”
  • “How many agents are in my CrewAI project?”

Sample output:

A2A SECURITY AUDIT ══════════════════════════════════════════════════════════════ AGENTS DETECTED (4) ┌─────────────────────────────────────────────────────────────┐ │ Research Specialist │ │ Tools: search_tool, web_scraper │ │ Delegation: ENABLED │ ├─────────────────────────────────────────────────────────────┤ │ Industry Analyst │ │ Tools: analysis_tool │ │ Delegation: ENABLED │ ├─────────────────────────────────────────────────────────────┤ │ Meeting Strategy Advisor │ │ Tools: calendar_tool │ │ Delegation: ENABLED │ ├─────────────────────────────────────────────────────────────┤ │ Briefing Coordinator │ │ Tools: (none) │ │ Delegation: DISABLED (terminal) │ └─────────────────────────────────────────────────────────────┘ FINDINGS: 1 warning (potential delegation chain)

Learn more: See the Multi-Agent Security Tutorial for detailed remediation guidance and framework-specific examples.

Configuration

Environment variables for advanced configuration:

VariableDescriptionDefault
INKOG_API_KEYYour API key (required)-
INKOG_API_URLAPI base URLhttps://api.inkog.io
INKOG_API_VERSIONAPI versionv1
INKOG_API_TIMEOUTRequest timeout (ms)30000
INKOG_LOG_LEVELLog levelinfo

Troubleshooting

Common Issue: API Key Not Found

If you see “API Key Required” errors, ensure your INKOG_API_KEY is correctly set in the MCP configuration. The key should start with sk_live_.

Verify Installation

Test that the MCP server is working by asking your AI assistant:

“Use Inkog to scan this directory for vulnerabilities”

If properly configured, the assistant will use the inkog_scan tool.

Debug Mode

Enable debug logging by setting:

{ "env": { "INKOG_LOG_LEVEL": "debug" } }

Source Code

The Inkog MCP Server is open source (Apache 2.0):

Last updated on