A side-by-side look at the Call4me and Hookwarden — Webhook Integrity MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Call4me for communication work over a hosted endpoint; choose Hookwarden — Webhook Integrity for communication as a local process. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 79/100 · Great | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 12 | 1 |
| Directory activity | 5 views 1 installs 2 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Call4me | View Hookwarden — Webhook Integrity |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"call4me": {
"url": "https://call4.me/mcp"
}
}
}
{
"mcpServers": {
"hookwarden-webhook-integrity": {
"command": "npx",
"args": [
"-y",
"hookwarden"
]
}
}
}