MCP Security
MCP Server Security Scanner
Audit any MCP server for security vulnerabilities before installation. Detects tool poisoning, confused deputy attacks, and data flow risks.
Why Audit MCP Servers?
Third-party risk
MCP servers from registries can contain malicious tool descriptions that manipulate AI behavior.
Hidden instructions
Tool poisoning attacks embed commands in descriptions that AI agents follow as legitimate guidance.
Missing authorization
Confused deputy vulnerabilities let attackers use the AI to access resources they shouldn't.
What Inkog Detects
Tool Poisoning—Malicious instructions hidden in tool descriptions
Confused Deputy—Missing authorization checks enabling privilege abuse
Data Exfiltration—Patterns that could leak sensitive data to external endpoints
Privilege Escalation—Tool chaining that bypasses permission boundaries
Input Validation—Missing sanitization on tool parameters
How to Audit
Via CLI
inkog audit-mcp githubVia Claude Desktop
# Install the Inkog MCP server, then ask Claude:
"Audit the filesystem MCP server for security issues"Via API
curl -X POST https://api.inkog.io/v1/mcp/audit \
-H "Authorization: Bearer $INKOG_API_KEY" \
-d '{"server_name": "github"}'