In-depth architectural comparison of the MCP Server Iaptic and MCP Icp Fit Scorer MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Server Iaptic
Customer Data Platforms · Local stdio
Quality: 51/100 (Good) | Auth: API Key required
MCP Icp Fit Scorer
Customer Data Platforms · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Verdict Summary: Choose MCP Server Iaptic if you need specialized Customer Data Platforms tools running via a local process. Choose MCP Icp Fit Scorer if your workspace requires Customer Data Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Server Iaptic when:
You need dedicated capabilities in the Customer Data Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
MCP Server Iaptic is categorized under Customer Data Platforms and uses a local stdio subprocess. In contrast, MCP Icp Fit Scorer belongs to Customer Data Platforms using local stdio subprocess. Select MCP Server Iaptic when you need capabilities focused on customer data platforms and MCP Icp Fit Scorer when you require tools for customer data platforms.
Filter purchases after this date (ISO format, e.g. 2024-01-01)
enddate
Filter purchases before this date (ISO format, e.g. 2024-12-31)
customerId
Filter by customer ID
purchase_get
Get purchase details by ID
transaction_list
List transactions with pagination and date filtering
+17 more tools listed on main page
MCP Icp Fit Scorer Tools (1)
score_icp_fit
Score 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.