Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mambabuilt/mcp-company-contact-details-extractor

NPM · @MAMBALABSDEV/MCP-COMPANY-CONTACT-DETAILS-EXTRACTOR · SCANNED SEP 20

Find a company contact page and extract role emails, a phone number and a postal address.

+3 this week 81 Trust /100
Trust breakdown (7 categories)

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
  • 31 of 96 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 28 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 581 tokens (~581/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 Management90
  • Stability observed for 27 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
Install

How do I install the com.mambabuilt/mcp-company-contact-details-extractor server?

com.mambabuilt/mcp-company-contact-details-extractor runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-company-contact-details-extractor. 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-contact-details-extractor

# add to Claude Code
claude mcp add com-mambabuilt-mcp-company-contact-details-extra -- npx -y @mambalabsdev/mcp-company-contact-details-extractor
// .cursor/mcp.json
{
  "mcpServers": {
    "com-mambabuilt-mcp-company-contact-details-extra": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-company-contact-details-extractor"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-mambabuilt-mcp-company-contact-details-extra": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-company-contact-details-extractor"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-mambabuilt-mcp-company-contact-details-extra -- npx -y @mambalabsdev/mcp-company-contact-details-extractor
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mambabuilt-mcp-company-contact-details-extra": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mambalabsdev/mcp-company-contact-details-extractor"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-mambabuilt-mcp-company-contact-details-extra --command npx --arg -y --arg @mambalabsdev/mcp-company-contact-details-extractor
# ~/.hermes/config.yaml
mcp_servers:
  com-mambabuilt-mcp-company-contact-details-extra:
    command: "npx"
    args: ["-y", "@mambalabsdev/mcp-company-contact-details-extractor"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-mambabuilt-mcp-company-contact-details-extra": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@mambalabsdev/mcp-company-contact-details-extractor"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-mambabuilt-mcp-company-contact-details-extra -t stdio -c npx -a -y @mambalabsdev/mcp-company-contact-details-extractor
// mcp.json
{
  "mcpServers": {
    "com-mambabuilt-mcp-company-contact-details-extra": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-company-contact-details-extractor"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 20 Sept 2026 · Analysed npm/@mambalabsdev/mcp-company-contact-details-extractor@1.0.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 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~581 tokens

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 →

Tool Tokens
extract_company_contact_details ~581

Find a company's contact page from its domain and extract classified ROLE email addresses (general, support, sales, privacy), a main phone number in E.164 where the country resolves, and a postal address. Returns one flat Clay ready row. Named individuals are NEVER returned: an address is kept only when its domain belongs to the company and its local part is in the role vocabulary, so a person's address is dropped by an allow list rather than by a name detector. The row reports how many addresses were found and how many were rejected and why, so a thin result is never mistaken for a site that publishes nothing. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.

NameTypeReqDescription
allowFreeMailboxesbooleanWhen "false" (default) an address at gmail, outlook or another free provider is rejected, because it cannot be checked against the company domain. Set "true" for small business and local company list…
company_domainstringBare company domain, for example stripe.com. This is the only required input and it is the join key for every other actor in the fleet.
company_namestringOptional. Used in the row and in logging. This actor gates addresses on the email DOMAIN rather than on the company name, so supplying a name does not change which addresses are kept.
crawlDepthstringHow many pages to read after the homepage. "1" (default) reads the contact page. "2" also reads a support or legal page when the contact page yielded nothing. This is a cost and thoroughness dial, no…
emailTypesstringWhich classes of role address to return. "all" (default) returns general, support, sales and privacy. The narrower settings return only what they name and leave the other columns null, which is a dif…
includeAddressbooleanWhen "true" (default) a postal address is read from JSON-LD first and from the footer second. Set "false" to skip it. Sent as a string for Clay compatibility.
includePhonesbooleanWhen "true" (default) the contact page is scanned for a main phone number. Set "false" to skip phone extraction entirely, which leaves the phone columns null. Sent as a string for Clay compatibility.
skipCachebooleanWhen "false" (default) a successful lookup is cached for seven days and reused, which costs you nothing on a repeated run. Set "true" to force a fresh fetch. Sent as a string for Clay compatibility.

No output schema declared.

No examples provided.

Common questions

What is the com.mambabuilt/mcp-company-contact-details-extractor server?

com.mambabuilt/mcp-company-contact-details-extractor is listed in the public MCP registry as com.mambabuilt/mcp-company-contact-details-extractor. Find a company contact page and extract role emails, a phone number and a postal address. This page covers its npm package (@mambalabsdev/mcp-company-contact-details-extractor).

Is the com.mambabuilt/mcp-company-contact-details-extractor server safe to use?

com.mambabuilt/mcp-company-contact-details-extractor scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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-contact-details-extractor server expose?

com.mambabuilt/mcp-company-contact-details-extractor exposes 1 tool: extract_company_contact_details. Their descriptions and schemas cost roughly 581 tokens of context every time the server is loaded.

Is the com.mambabuilt/mcp-company-contact-details-extractor server still maintained?

com.mambabuilt/mcp-company-contact-details-extractor is still listed as active in the MCP registry. We last reached this channel on 20 September 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-contact-details-extractor server under?

com.mambabuilt/mcp-company-contact-details-extractor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.