A side-by-side look at the RocketReach and Forage — Web Intelligence & Knowledge Graph MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose RocketReach for developer tools work over a hosted endpoint; choose Forage — Web Intelligence & Knowledge Graph for developer tools 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 | Developer Tools | Developer Tools |
| Quality signal | 33/100 · Emerging | 35/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View RocketReach | View Forage — Web Intelligence & Knowledge Graph |
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": {
"rocketreach": {
"url": "https://mcp.rocketreach.co/mcp"
}
}
}
{
"mcpServers": {
"forage-web-intelligence-knowledge-graph": {
"command": "npx",
"args": [
"-y",
"@anthropic/mcp-proxy"
]
}
}
}