mcp-contact-classifier
It classifies one contact row from a job title, with optional position verification and LLM fallback.
Classify a
job_titleintodepartment,seniority,seniority_rank(1–12), and the auditableclassification_rule.Optionally verify whether a person is still listed on their employer’s website by providing
full_name,company_domain, andverify_position=true.Optionally route unplaceable titles to your own LLM via
use_llm_fallback,llm_provider, andllm_model, using yourLLM_API_KEY; only the title is sent.Ignore cached results with
skipCache="true".Base classification is deterministic and needs no model/API key, but the tool requires
APIFY_TOKENand consumes Apify credits.It is read-only, idempotent, and does not discover people; name/title must be supplied.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-contact-classifier Classify VP of Sales and verify if Mark Johnson is listed at globex.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Contact Classifier MCP Server
MCP server for the Mamba Labs Contact Classifier actor on Apify.
Give it a job title and it returns the department and the seniority level. Give it a name and a company domain too, and it also checks whether that person is still listed on their employer's own website. The classification is a deterministic rule table, so it needs no API key and returns the same answer for the same title every time.
Install
npx -y @mambalabsdev/mcp-contact-classifierClaude Desktop
{
"mcpServers": {
"mamba-contact-classifier": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-contact-classifier"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}Get an Apify token at console.apify.com/account/integrations.
Related MCP server: mcp-people-finder
Tool
classify_contact
One contact in, one classified row out. Only the job title is required.
Input | Type | Required | Notes |
| string | yes | The contact's job title, exactly as you hold it. Classified by deterministic rules with no API key needed. |
| string | no | Only needed for position verification. Classification works without it. This name is never sent to any language model. |
| string | no | Only needed for position verification. The company's website domain, with or without https. |
| boolean | no | Check whether the person is still listed on their employer's own website. Adds roughly 3 seconds and 9 requests per contact, and needs both the name and the domain. Default |
| boolean | no | Sends titles the rules cannot place to your own model, using the |
| enum | no |
|
| string | no | Model id passed straight through to the provider. Only read when the LLM fallback is on. Default |
| enum | no | Set to |
| number | no | Optional cost cap in USD for this run. The actor stops before an item that could take its charges past this amount. Omit to rely on the maximum cost per run set in Apify. |
Reading the output
21 flat snake_case fields, one row per contact. department is one of 12, seniority one of 12, and seniority_rank is 1 to 12 so a decision maker filter is a comparison rather than a list of strings. classification_rule names the rule that fired, which is what makes the decision auditable.
With no LLM_API_KEY set, titles the rules cannot place come back null. The row is still returned.
Billing
You are charged per contact classified, plus a small actor start fee. The deterministic classification calls no model and no third party API.
Event | Price | Fires when |
| $0.00005 | Once per run, on start, one event per GB of memory (minimum one). Apify's start event. |
| $0.003 (FREE tier), down to $0.00255 on GOLD and above | Once per contact, including a title the rules cannot place. |
Full pricing is on the actor's Apify page. Running this server consumes Apify credits.
The tool starts the actor run and polls it to a finished status, so a run with verify_position on is not cut off at 300 seconds. A run that does not succeed comes back as an error with its run ID and status.
What this server does and does not do
It is a thin client for the Apify actor. It passes your input through and returns the actor's output unchanged. Every behavior described above lives in the actor, not here.
This actor does not discover people. The name and title come from you. It classifies a title and, optionally, checks a name against a page the employer published. To find people in the first place, use People Finder.
Errors are surfaced, never swallowed. An invalid input, an invalid token, an exhausted balance, a timeout, or a run that returns anything other than a dataset all come back as an explicit tool error rather than as an empty result.
Source
The actor is on the Apify Store. This wrapper is MIT licensed.
Built by Mamba Labs
Available Tools
1 toolclassify_contactClassify ContactARead-onlyIdempotent
One contact in, one classified row out. Give it a job title and it returns the department, the seniority level, a seniority_rank from 1 to 12 you can filter with a comparison, and classification_rule, the named rule that fired, so every decision is auditable. The classification is a deterministic rule table: it needs no API key, calls no model, and returns the same answer for the same title every time. Only job_title is required. full_name and company_domain are read only when verify_position is on, which checks whether the person is still listed on their employer's own website and adds roughly 3 seconds and 9 requests per contact. The optional LLM fallback for titles the rules cannot place runs on your own key, set as the LLM_API_KEY secret environment variable on your own copy of the actor, and only the title is ever sent, never the person's name. With no key set those titles come back null rather than failing the row. This actor does not discover people: the name and title come from you. Requires an APIFY_TOKEN and consumes Apify credits. Read only.
Inputs: job_title (required), full_name, llm_model, skipCache, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Lead enrichment, email/phone, hiring, news, new companies, contacts and RSS, via Apify.
Find LinkedIn people by name, title, employer or school. Paid, on Apify's hosted MCP.
Classification service to seamlessly retrieve SOC codes for job titles and descriptions.
People, company, job and LinkedIn post data, plus email finding and verification.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables building targeted company lists from live job boards or SEC filings via the Apify actor, supporting role keywords, locations, and filing phrases.176 npmMIT
- AlicenseAqualityBmaintenanceMCP 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.1121 npmMIT
- AlicenseAqualityBmaintenanceExtracts 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.172 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.159 npmMIT