Crimson Crawler vs GhidraMCP
A side-by-side look at the Crimson Crawler and GhidraMCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
Crimson CrawlerSecurity · Remote HTTP/SSEEnrich, search, assess, and manage threat intelligence through 80+ typed MCP tools.43FairAuth: oauth 2.0Verdict: choose Crimson Crawler for security work over a hosted endpoint; choose GhidraMCP for security over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
CChoose Crimson Crawler when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Crimson Crawler | |
|---|---|---|
| Category | Security | Security |
| Quality signal | 43/100 · Fair | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | OAuth 2.0 | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 11,518 |
| Directory activity | 0 views 0 installs 0 upvotes | 13 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Crimson Crawler | View GhidraMCP |
Tools & capabilities
Crimson Crawler tools
No tool names declared yet. Check the project README from the listing page.
GhidraMCP tools
No tool names declared yet. Check the project README from the listing page.
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.
Crimson Crawler
{
"mcpServers": {
"crimson-crawler": {
"command": "npx",
"args": [
"-y",
"crimson-crawler"
]
}
}
}
GhidraMCP
{
"mcpServers": {
"lauriewired-ghidramcp": {
"url": "http://127.0.0.1:8081/sse"
}
}
}
Frequently asked questions
Crimson Crawler is categorized under Security and uses a remote HTTP/SSE transport. GhidraMCP belongs to Security and uses a remote HTTP/SSE transport. Pick Crimson Crawler for security work and GhidraMCP 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.
Crimson Crawler has no declared pricing — check the project's own site. Auth: oauth 2.0. GhidraMCP is listed as free. Auth: no auth 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 crimson-crawler and lauriewired-ghidramcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Crimson Crawler has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. GhidraMCP has 60/100 (Good) with 13 views, 0 installs and 11,518 GitHub stars.