com.mambabuilt/mcp-contact-classifier
NPM · @MAMBALABSDEV/MCP-CONTACT-CLASSIFIER
Classify a job title into department and seniority, and optionally verify the position.
Available components
Last scanned (3 hours ago)
Scores higher than 61% of npm servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 19 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 611 tokens (~611/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −4
- Stability: pass → 0.70 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- Package version: 1.1.1 → 1.2.0 functional
- 21 Oct 26 −1
- Stability: pass → 0.97 functional
- 19 Oct 26 0
- Package version: 1.1.1 → 1.2.0 functional
- 17 Oct 26 +14
- Known CVEs: unverified → pass ▲ security
- Stability: 0.80 → pass security
- Dependency health: unverified → 0.85 ▲ functional
- 16 Oct 26 −13
- Known CVEs: pass → unverified ▼ security
- Schema quality: 540 → 611 ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- Stability: pass → 0.80 functional
- Package version: 1.1.1 → 1.2.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@mambalabsdev/mcp-contact-classifier@1.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
classify_contact Classify Contact ~611
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. Reads public data only and writes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| company_domain | string | – | Only needed for position verification. The company's website domain, with or without https. |
| full_name | string | – | Only needed for position verification. Classification works without it. This name is never sent to any language model. |
| job_title | string | yes | The contact's job title, exactly as you hold it. Classified by deterministic rules with no API key needed. |
| llm_model | string | – | Model id passed straight through to the provider. Only read when the LLM fallback is on. Default: "gpt-4o-mini". |
| llm_provider | string | – | Which provider your LLM_API_KEY belongs to. Only read when the LLM fallback is on. Default: "openai". |
| max_charge_usd | number | – | Optional. The run stops before starting an item that could take its charges past this amount, so no row is cut in half. Leave empty to rely only on the maximum cost per run you set in Apify. The run… |
| skipCache | string | – | Set to true to ignore cached results and classify from scratch. Default: "false". |
| use_llm_fallback | boolean | – | Off by default. When on, titles the rules cannot place are sent to your own model using the LLM_API_KEY secret environment variable you set on your copy of this Actor. Only the title is sent, never t… |
| verify_position | boolean | – | Check whether the person is still listed on their employer's own website. Off by default. Adds roughly 3 seconds and 9 requests per contact, and needs both the name and the domain. Default: false. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-contact-classifier server?
com.mambabuilt/mcp-contact-classifier runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-contact-classifier. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-contact-classifier
claude mcp add com-mambabuilt-mcp-contact-classifier -- npx -y @mambalabsdev/mcp-contact-classifier
What is the com.mambabuilt/mcp-contact-classifier server?
com.mambabuilt/mcp-contact-classifier is listed in the public MCP registry as com.mambabuilt/mcp-contact-classifier. Classify a job title into department and seniority, and optionally verify the position. This page covers its npm package (@mambalabsdev/mcp-contact-classifier).
Is the com.mambabuilt/mcp-contact-classifier server safe to use?
com.mambabuilt/mcp-contact-classifier scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mambabuilt/mcp-contact-classifier server expose?
com.mambabuilt/mcp-contact-classifier exposes 1 tool: classify_contact. Their descriptions and schemas cost roughly 611 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-contact-classifier server still maintained?
com.mambabuilt/mcp-contact-classifier is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.mambabuilt/mcp-contact-classifier server under?
com.mambabuilt/mcp-contact-classifier declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.