Bounceban vs Deliveriq MCP
A side-by-side look at the Bounceban and Deliveriq MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
B
BouncebanCommunication · Local subprocess (stdio)BounceBan MCP — wraps the BounceBan email-verification API (bounceban.com)52GoodAuth: api key requiredVerdict: choose Bounceban for communication work as a local process; choose Deliveriq MCP for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
BChoose Bounceban when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
catch_all.
Choose Deliveriq MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
DELIVERIQ_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | B Bounceban | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 52/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | Freemium |
| Required env vars | None listed | DELIVERIQ_API_KEY |
| Verified owner |
Tools & capabilities
Bounceban tools 1
catch_all
Deliveriq 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.
Bounceban
{
"mcpServers": {
"bounceban": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-bounceban"
]
}
}
}
Deliveriq MCP
{
"mcpServers": {
"deliveriq-mcp": {
"command": "npx",
"args": [
"-y",
"@deliveriq/mcp"
],
"env": {
"DELIVERIQ_API_KEY": "YOUR_DELIVERIQ_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Bounceban is categorized under Communication and uses a local stdio subprocess. Deliveriq MCP belongs to Communication and uses a local stdio subprocess. Pick Bounceban for communication work and Deliveriq MCP for communication.
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.
Bounceban is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Deliveriq MCP is listed as freemium — a free tier with paid plans. 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 bounceban and deliveriq-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Bounceban has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Deliveriq MCP has 41/100 (Fair) with 2 views, 0 installs and 1 GitHub stars.