com.mambabuilt/mcp-company-identity-resolver
NPM · @MAMBALABSDEV/MCP-COMPANY-IDENTITY-RESOLVER
Resolve company name, domain, or LinkedIn into one canonical identity with confidence scores.
Available components
Last scanned (58 minutes ago)
Scores higher than 35% 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 Security48
- Malware scan not yet available for this package.Unverified
- 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 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 407 tokens (~407/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 1.2.0 → 1.2.1 functional
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 0
- Stability: 0.93 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 346 → 407 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 1.1.1 → 1.2.0 functional
- 15 Oct 26 +44
- Injection markers: unverified → pass ▲ security
- Schema quality: 221 → 346 ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.93 ▲ functional
- 14 Oct 26 0
- Package version: 1.0.1 → 1.1.1 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-company-identity-resolver@1.2.1
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 →
resolve_company_identity Resolve Company Identity ~407
Resolve any combination of company name, domain, or LinkedIn URL into one canonical company identity: the name, primary domain, and LinkedIn company URL, each with a 0-100 confidence score plus an overall score and a match method. Cross-checks the inputs you give it, resolves the ones you do not, and flags conflicts (a domain and a LinkedIn slug that disagree) instead of merging them. Login-free and public-data only. Takes one company or a list (company_names or domains), one row per company. Returns flat Clay-ready JSON. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
| Name | Type | Req | Description |
|---|---|---|---|
| batchSize | integer | – | How many companies from the lists are resolved at once. 1 to 10. Default: 2. |
| company_name | string | – | Company name, e.g. Stripe. Provide at least one of company_name, domain, or linkedin_url. |
| company_names | array | – | A list of company names to resolve in one run, one row per company. Use instead of company_name for a batch. |
| domain | string | – | Bare company domain, e.g. stripe.com. The strongest canonical key when provided. |
| domains | array | – | A list of bare company domains to resolve in one run, one row per domain. Use instead of domain for a batch. |
| linkedin_url | string | – | LinkedIn company URL (https://www.linkedin.com/company/stripe) or bare slug (stripe). |
| max_charge_usd | number | – | Optional. The run stops before any charge that would take this run's total past this amount in USD, and every row already charged is kept. Leave it empty to rely only on the maximum cost per run set… |
| skipCache | boolean | – | Force a fresh resolution and ignore the 7 day result cache. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-company-identity-resolver server?
com.mambabuilt/mcp-company-identity-resolver runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-company-identity-resolver. 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-company-identity-resolver
claude mcp add com-mambabuilt-mcp-company-identity-resolver -- npx -y @mambalabsdev/mcp-company-identity-resolver
What is the com.mambabuilt/mcp-company-identity-resolver server?
com.mambabuilt/mcp-company-identity-resolver is listed in the public MCP registry as com.mambabuilt/mcp-company-identity-resolver. Resolve company name, domain, or LinkedIn into one canonical identity with confidence scores. This page covers its npm package (@mambalabsdev/mcp-company-identity-resolver).
Is the com.mambabuilt/mcp-company-identity-resolver server safe to use?
com.mambabuilt/mcp-company-identity-resolver scores 68 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-company-identity-resolver server expose?
com.mambabuilt/mcp-company-identity-resolver exposes 1 tool: resolve_company_identity. Their descriptions and schemas cost roughly 407 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-company-identity-resolver server still maintained?
com.mambabuilt/mcp-company-identity-resolver 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-company-identity-resolver server under?
com.mambabuilt/mcp-company-identity-resolver declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.