No user-submitted related servers found.
Scored across 1 tool
Only one tool exists, so there is no possibility of confusing it with another tool. The name and description clearly communicate its single, focused purpose.
The single tool uses a clear verb_noun pattern (score_icp_fit). There are no other naming conventions to create inconsistency or ambiguity.
One tool is at the low end of the typical range. For a narrow, single-purpose ICP scorer this is defensible, but the surface feels thin compared with more comprehensive MCP servers.
The tool covers the core scoring workflow well, with flexible ICP definition via template, JSON config, or plain-English description, and returns a per-signal breakdown. Minor gaps exist around managing stored ICP templates or estimating Apify credit usage before making a call.