Shellward vs Osv Ui — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Shellward vs Osv Ui
In-depth architectural comparison of the Shellward and Osv Ui 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
Shellward
Security · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Osv Ui
Security · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Shellward if you need specialized Security tools running via a local process. Choose Osv Ui 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 Shellward 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).
You have access to required keys: SHELLWARD_MODE, SHELLWARD_LOCALE, SHELLWARD_THRESHOLD, SHELLWARD_BASELINE_PATH.
Primary tools included: Stdio MCP server with local execution, Prompt injection detection for Chinese and English text, PII, credential, and sensitive-data scanning.
AI Agent Security Middleware & MCP Server with 8-layer defense including prompt injection detection, DLP data flow tracking, command blocking, and PII detection. 7 MCP tools, zero dependencies.
Visual CVE audit dashboard for npm, Python, Go, and Rust. Scan from Claude/Cursor, opens a browser UI for human review (human-in-the-loop), applies fixes with explicit confirmation. Powered by OSV.dev.
Category & Scope
Tools & Capabilities Breakdown
Shellward Tools (6)
Stdio MCP server with local execution
Prompt injection detection for Chinese and English text
PII, credential, and sensitive-data scanning
Command, path, tool, and outbound-action checks
MCP tool-poisoning and rug-pull detection
China-focused project compliance scanning
Osv Ui Tools (4)
scan_project
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).
Shellward is categorized under Security and uses a local stdio subprocess. In contrast, Osv Ui belongs to Security using local stdio subprocess. Select Shellward when you need capabilities focused on security and Osv Ui when you require tools for security.
Scan a project directory for CVE vulnerabilities. Automatically detects npm, Python, Go, Rust, Java/Maven, PHP/Composer, and Ruby/Bundler manifests. Queries live CVE data from OSV.dev. Returns structured vulnerability report with severity counts, risk score, and fix recommendations. Use this as the first step before open_dashboard or apply_fixes.
open_dashboard
Launch the osv-ui visual dashboard in the browser for human review. This is the HUMAN-IN-THE-LOOP step — always offer this before applying fixes. The dashboard shows full CVE details, severity charts, and the upgrade guide. Returns the dashboard URL. If already running for this path, returns existing URL.
get_fix_commands
Get the safe upgrade commands for vulnerable packages WITHOUT executing them. Use this to show the user what will be changed before calling apply_fixes. Returns a list of commands grouped by ecosystem (npm, pip, go, cargo, Maven, Composer, Bundler).
apply_fixes
Execute package upgrade commands to fix CVEs. IMPORTANT: This is a DESTRUCTIVE action that modifies package files. ALWAYS call get_fix_commands first and confirm with the user before calling this. Returns the command output for each fix applied.