GhidraMCP vs Mobb Vibe Shield MCP
A side-by-side look at the GhidraMCP and Mobb Vibe Shield MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GhidraMCP for security work over a hosted endpoint; choose Mobb Vibe Shield MCP for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose GhidraMCP when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Choose Mobb Vibe Shield MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
API_KEY, API_URL, MVS_AUTO_FIX. - You want tools like
Parameter, Returns.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 60/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | None listed | API_KEYAPI_URLMVS_AUTO_FIX |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11,584 | 68 |
| Directory activity | 13 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View GhidraMCP | View Mobb Vibe Shield MCP |
Tools & capabilities
GhidraMCP tools
No tool names declared yet. Check the project README from the listing page.
Mobb Vibe Shield MCP tools 2
Parameter`path` (string) - The path to the local git repositoryReturnsDetailed vulnerability fixes with code patches and explanations
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
GhidraMCP
{
"mcpServers": {
"lauriewired-ghidramcp": {
"url": "http://127.0.0.1:8081/sse"
}
}
}
Mobb Vibe Shield MCP
{
"mcpServers": {
"mobb-dev-mobb-vibe-shield-mcp": {
"command": "npx",
"args": [
"-y",
"mobbdev"
],
"env": {
"API_KEY": "YOUR_API_KEY_HERE",
"API_URL": "YOUR_API_URL_HERE",
"MVS_AUTO_FIX": "YOUR_MVS_AUTO_FIX_HERE"
}
}
}
}
Frequently asked questions
GhidraMCP is categorized under Security and uses a remote HTTP/SSE transport. Mobb Vibe Shield MCP belongs to Security and uses a local stdio subprocess. Pick GhidraMCP for security work and Mobb Vibe Shield MCP for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
GhidraMCP is listed as free. Auth: no auth required. Mobb Vibe Shield MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add lauriewired-ghidramcp and mobb-dev-mobb-vibe-shield-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GhidraMCP has a quality signal of 60/100 (Good) with 13 views, 0 installs and 11,584 GitHub stars. Mobb Vibe Shield MCP has 63/100 (Good) with 2 views, 0 installs and 68 GitHub stars.