Quiet Failures vs MCP Shodan
A side-by-side look at the Quiet Failures and MCP Shodan MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Q
Quiet FailuresSecurity · Remote HTTP/SSEOpen weekly security base rates (CC BY 4.0), plus live DMARC, takeover and WHOIS checks.37FairAuth: not declaredVerdict: choose Quiet Failures for security work over a hosted endpoint; choose MCP Shodan for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
QChoose Quiet Failures when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
Choose MCP Shodan 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:
SHODAN_API_KEY. - You want tools like
ip_lookup, ip, shodan_search.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Q Quiet Failures | |
|---|---|---|
| Category | Security | Security |
| Quality signal | 37/100 · Fair | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | SHODAN_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 174 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 22 |
| Full listing | View Quiet Failures | View MCP Shodan |
Tools & capabilities
Quiet Failures tools
No tool names declared yet. Check the project README from the listing page.
MCP Shodan tools 22
ip_lookupipshodan_searchquerymax_resultscve_lookupcvedns_lookuphostnamesreverse_dns_lookupipscpe_lookup- +10 more on 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.
Quiet Failures
{
"mcpServers": {
"quiet-failures": {
"url": "https://quietfailures.com/mcp"
}
}
}
MCP Shodan
{
"mcpServers": {
"burtthecoder-mcp-shodan": {
"command": "npx",
"args": [
"-y",
"@burtthecoder/mcp-shodan"
],
"env": {
"SHODAN_API_KEY": "YOUR_SHODAN_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Quiet Failures is categorized under Security and uses a remote HTTP/SSE transport. MCP Shodan belongs to Security and uses a local stdio subprocess. Pick Quiet Failures for security work and MCP Shodan 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.
Quiet Failures has no declared pricing — check the project's own site. MCP Shodan 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 quiet-failures and burtthecoder-mcp-shodan as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Quiet Failures has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCP Shodan has 65/100 (Great) with 4 views, 0 installs and 174 GitHub stars.