com.mambabuilt/mcp-partner-member-directory-extractor
NPM · @MAMBALABSDEV/MCP-PARTNER-MEMBER-DIRECTORY-EXTRACTOR
One company row per listing from partner directories and member lists, with domain and tier.
Available components
Last scanned (12 hours ago)
Scores higher than 39% of npm servers
Category Marketing and SEO
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 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 374 tokens (~374/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 Management3
- Stability observed for 1 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.
- 22 Oct 26 69
First indexed and scored.
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 23 Oct 2026 · Analysed npm/@mambalabsdev/mcp-partner-member-directory-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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| 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 →
extract_directory_companies Extract companies from a partner or member directory ~374
Turn a vendor partner directory or a trade body member list into one company row per listing. Give directory_url or directory_urls (up to 20). Reads directories built on PartnerPage (for example https://www.clay.com/en/experts or the Zapier partner directory) through PartnerPage's public listing API, the Shopify Partner Directory (any https://www.shopify.com/partners/directory/... page), and member lists that link to one profile page per member. Each row: listing_name, company_domain, website, listing_url, tier, tags, location, rating, review_count, partner_since, and the email and phone the directory itself publishes. robots.txt is checked before every request. A directory that cannot be read (it builds its list in the browser) returns one free row with row_status unsupported. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per company row.
| Name | Type | Req | Description |
|---|---|---|---|
| dedupe_domains | string | – | Return a company listed more than once only once; skipped repeats are free. Default true. |
| directory_url | string | – | One directory page URL. |
| directory_urls | array | – | Up to 20 directory page URLs. |
| include_details | string | – | PartnerPage directories: true adds tags, location, and the listed email with one more request per listing. Default true. |
| max_charge_usd | string | – | Optional. The run stops before any row that would take its charges over this amount. |
| max_listings | string | – | Listings per directory, 1 to 5000. Each company row is billed. Default 100. |
| max_pages | string | – | Shopify and member list directories: listing pages to read, 1 to 100. Default 10. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-partner-member-directory-extractor server?
com.mambabuilt/mcp-partner-member-directory-extractor runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-partner-member-directory-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-partner-member-directory-extractor
claude mcp add com-mambabuilt-mcp-partner-member-directory-extr -- npx -y @mambalabsdev/mcp-partner-member-directory-extractor
What is the com.mambabuilt/mcp-partner-member-directory-extractor server?
com.mambabuilt/mcp-partner-member-directory-extractor is listed in the public MCP registry as com.mambabuilt/mcp-partner-member-directory-extractor. One company row per listing from partner directories and member lists, with domain and tier. This page covers its npm package (@mambalabsdev/mcp-partner-member-directory-extractor).
Is the com.mambabuilt/mcp-partner-member-directory-extractor server safe to use?
com.mambabuilt/mcp-partner-member-directory-extractor scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 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-partner-member-directory-extractor server expose?
com.mambabuilt/mcp-partner-member-directory-extractor exposes 1 tool: extract_directory_companies. Their descriptions and schemas cost roughly 374 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-partner-member-directory-extractor server still maintained?
com.mambabuilt/mcp-partner-member-directory-extractor is still listed as active in the MCP registry. We last reached this channel on 23 October 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-partner-member-directory-extractor server under?
com.mambabuilt/mcp-partner-member-directory-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.