MCP Security Audit vs Orihime — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
MCP Security Audit vs Orihime
In-depth architectural comparison of the MCP Security Audit and Orihime MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Security Audit
Security · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Orihime
Security · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose MCP Security Audit if you need specialized Security tools running via a local process. Choose Orihime if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Security Audit when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
A powerful MCP (Model Context Protocol) Server that audits npm package dependencies for security vulnerabilities. Built with remote npm registry integration for real-time security checks.
Cross-repository code knowledge graph MCP server for Java, Kotlin, JavaScript, and TypeScript. Indexes source into embedded KuzuDB via tree-sitter; 30+ tools for call-flow tracing, multi-hop taint analysis (OWASP/CWE/PCI/STIG reports), entry-point reachability filtering, performance hotspot detection, and license compliance — without reading source files. 95% fewer tokens vs source-reading baseline. pip install orihime
Tools & Capabilities Breakdown
MCP Security Audit Tools (6)
Remote npm registry security checks
Critical-to-low severity reporting
CVE, CVSS, CWE, and advisory references
Automatic fix recommendations
npm, pnpm, and yarn support
Structured clean-audit responses
Orihime Tools (6)
Cross-repository code knowledge graph
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
MCP Security Audit is categorized under Security and uses a local stdio subprocess. In contrast, Orihime belongs to Security using local stdio subprocess. Select MCP Security Audit when you need capabilities focused on security and Orihime when you require tools for security.