Securitytrails vs Ghidra MCP
A side-by-side look at the Securitytrails and Ghidra MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Securitytrails for security work as a local process; choose Ghidra MCP for security over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Securitytrails when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You want tools like
securitytrails_domain, securitytrails_subdomains, securitytrails_dns_history.
Choose Ghidra MCP 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 | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 53/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 5,877 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Securitytrails | View Ghidra MCP |
Tools & capabilities
Securitytrails tools 4
securitytrails_domainDomain intel (DNS, subdomain count) for <hostname>. Returns current A/MX/NS records, subdomain count, and Alexa rank. Example: securitytrails_domain({ hostname: "github.com", _apiKey: "your-key" })securitytrails_subdomainsEnumerate subdomains of <hostname>. Returns the subdomain labels plus fully-qualified domains. Example: securitytrails_subdomains({ hostname: "github.com", _apiKey: "your-key" })securitytrails_dns_historyHistorical DNS records for <hostname>. Returns past record values with first/last-seen dates for a given record type (a, aaaa, mx, ns, soa, txt). Example: securitytrails_dns_history({ hostname: "github.com", type: "a", _apiKey: "your-key" })securitytrails_whoisWHOIS for <hostname>. Returns registrar, creation/expiration dates, and registration contacts. Example: securitytrails_whois({ hostname: "github.com", _apiKey: "your-key" })
Ghidra MCP 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.
Securitytrails
{
"mcpServers": {
"securitytrails": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-securitytrails"
]
}
}
}
Ghidra MCP
{
"mcpServers": {
"ghidra-mcp": {
"url": "http://127.0.0.1:8081/mcp"
}
}
}
Frequently asked questions
Securitytrails is categorized under Security and uses a local stdio subprocess. Ghidra MCP belongs to Security and uses a remote HTTP/SSE transport. Pick Securitytrails for security work and Ghidra 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.
Securitytrails has no declared pricing — check the project's own site. Ghidra MCP 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 securitytrails and ghidra-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Securitytrails has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Ghidra MCP has 59/100 (Good) with 1 views, 0 installs and 5,877 GitHub stars.