MCP Icp Fit Scorer vs Lusha MCP Plugin
A side-by-side look at the MCP Icp Fit Scorer and Lusha MCP Plugin MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Icp Fit Scorer for customer data platforms work as a local process; choose Lusha MCP Plugin for customer data platforms. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Icp Fit Scorer when
- You need dedicated capabilities in the Customer Data Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
APIFY_TOKEN. - You want tools like
score_icp_fit.
Choose Lusha MCP Plugin when
- You need dedicated capabilities in the Customer Data Platforms domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Customer Data Platforms | Customer Data Platforms |
| Quality signal | 63/100 · Good | 33/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | APIFY_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 4 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View MCP Icp Fit Scorer | View Lusha MCP Plugin |
Tools & capabilities
MCP Icp Fit Scorer tools 1
score_icp_fitScore a company against your ideal customer profile (ICP) using weighted signals. Returns a 0 to 100 icp_score, an A to D icp_tier, and a per-signal breakdown as a flat, Clay-ready JSON row. Define your ICP with a prebuilt template, a JSON scoring_config, or a plain-English icp_description (which requires llm_api_key). Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
Lusha MCP Plugin 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.
MCP Icp Fit Scorer
{
"mcpServers": {
"mambalabsdev-mcp-icp-fit-scorer": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-icp-fit-scorer"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN_HERE"
}
}
}
}
Lusha MCP Plugin
No confirmed install command for Lusha MCP Plugin yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
MCP Icp Fit Scorer is categorized under Customer Data Platforms and uses a local stdio subprocess. Lusha MCP Plugin belongs to Customer Data Platforms and uses an install path we have not confirmed yet. Pick MCP Icp Fit Scorer for customer data platforms work and Lusha MCP Plugin for customer data platforms.
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. Lusha MCP Plugin has no confirmed install command yet — follow its own setup instructions.
MCP Icp Fit Scorer is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Lusha MCP Plugin has no declared pricing — check the project's own site. 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 mambalabsdev-mcp-icp-fit-scorer and mcp-110 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Icp Fit Scorer has a quality signal of 63/100 (Good) with 1 views, 0 installs and 3 GitHub stars. Lusha MCP Plugin has 33/100 (Emerging) with 0 views, 0 installs and 4 GitHub stars.