Bounceban vs Scrivener MCP
A side-by-side look at the Bounceban and Scrivener 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 Scrivener MCP for knowledge & memory 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 Scrivener MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | B Bounceban | |
|---|---|---|
| Category | Communication | Knowledge & Memory |
| Quality signal | 52/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | None listed | None listed |
Tools & capabilities
Bounceban tools 1
catch_all
Scrivener 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"
]
}
}
}
Scrivener MCP
{
"mcpServers": {
"writerslogic-scrivener-mcp": {
"command": "npx",
"args": [
"-y",
"scrivener-setup"
]
}
}
}
Frequently asked questions
Bounceban is categorized under Communication and uses a local stdio subprocess. Scrivener MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Bounceban for communication work and Scrivener MCP for knowledge & memory.
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. Scrivener 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 bounceban and writerslogic-scrivener-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. Scrivener MCP has 61/100 (Good) with 18 views, 12 installs and 67 GitHub stars.
