mcp-contact-classifier
Related Servers
Alternatives to mcp-contact-classifier
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceExtracts people (names and titles) from a company's team, leadership, or about page given a domain. Uses Apify to crawl and return structured data, with optional filters for seniority and email inclusion.165 npmMIT
- AlicenseAqualityBmaintenanceEnables checking CRM contacts to learn their current employer, title, start month, role history, and whether they left, landed elsewhere, or were promoted, returning one flat row per person with match method, source, and source age. It accepts single contacts or bulk lists, works with your own search, enrichment, and email-verification keys, and runs on Apify.1113 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs People Finder & Email Verifier actor on Apify. Give it a company domain, name or LinkedIn URL and it returns the people at that company who match your role, seniority and department filters, each as a structured contact record with an optional verified business email.165 npmMIT
- AlicenseAqualityAmaintenanceEnables building targeted company lists from live job boards or SEC filings via the Apify actor, supporting role keywords, locations, and filing phrases.164 npmMIT
- AlicenseAqualityBmaintenanceClassifies company sites as B2B or B2C and as SaaS, online store, agency, manufacturer, wholesaler, distributor, or marketplace, while matching your own buyer phrases and returning the quoted text and page as evidence. Runs deterministically on Apify, giving one row per domain with grace-free status rows for unreachable, blocked, or empty sites.1162 npmMIT
- AlicenseAqualityAmaintenanceEnables B2B lead generation through Apify's Prospect Engine actor, supporting company enrichment, job discovery, contact finding, and full ICP-gated outreach workflows.176 npmMIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap. Every call is unambiguously directed to classify_contact, making misselection impossible.
The single tool name 'classify_contact' follows a clear verb_noun pattern and is descriptive. Consistency is trivially maintained when there is only one tool.
The server is narrowly scoped to contact classification, and one tool covers the entire purpose. While below the typical 3-15 range, the focused design justifies the count, though it feels slightly thin.
The tool fully covers the classification operation: input a title, output department, seniority, rank, and classification rule. Optional verification and LLM fallback are integrated. No critical gaps or dead ends exist for the stated purpose.