Sales Intelligence MCP — CRM integration, lead research, company enrichment, and outreach automation. Works with Claude, Grok, Gemini, GPT, Cursor, Windsurf, and any MCP-compatible client.
Only 1 tool visible in source (company_lookup). Tool has a description and input schema with 3 parameters, but schema quality is poor: parameters lack type definitions in the visible schema object, descriptions are generic, and no output schema is documented. The server claims '12 MCP tools' in package.json but only company_lookup is defined in the provided code snippet. Cannot verify remaining 11 tools.
Look up detailed company information by domain name. Returns company name, description, industry, employee count, revenue estimates, tech stack, social profiles, and logo. Uses Clearbit data enrichment.
Input schema lacks type definitions. Parameters 'domain', 'crm_api_key', 'api_key' are listed but no JSON Schema types (string, number, boolean, etc.) are visible in the schema object.
No output schema documented. Tool description states it 'Returns company name, description, industry, employee count, revenue estimates, tech stack, social profiles, and logo' but no structured output schema is provided. LLMs cannot plan downstream calls or extract fields without knowing the response structure.
API key exposed as tool parameter. 'api_key' and 'crm_api_key' are optional parameters in the tool definition. Per pattern:secret-injection, credentials must never appear as tool parameters, use server-side secret injection via environment variables. Agent traces log all parameters, leaking secrets.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 47 | 2026-07-28+ | v2 |
Mismatch between claimed tool count and visible definitions. package.json claims '12 MCP tools' but only company_lookup is defined in server.js. Remaining 11 tools (contact_finder, email_verification, outreach_templates, etc.) are referenced in comments and constants but not registered as actual MCP tools. Cannot evaluate their quality.
Parameter descriptions are generic and lack actionable constraints. 'Company domain (e.g., stripe.com, hubspot.com)' includes example values, which LLMs tend to reuse literally. No format constraint (regex, length limit) is specified. Description should state: 'Domain name without protocol (e.g., example.com). Must be 3-255 characters, alphanumeric and hyphens only.'