Company Firmographic Enricher MCP Server
This MCP server exposes one tool to enrich company domains into structured firmographics via Mamba Labs' Apify actor.
Enrich a single company domain (e.g. stripe.com) or a batch of domains into employee band, industry, HQ, founded year, revenue estimate, logo, and description.
Parse firmographics from the company's schema.org/Organization JSON-LD and HTML meta tags, returning flat Clay-ready JSON with source_signals and data_completeness.
Accept an optional company_name fallback label; domains takes precedence over domain for batch mode.
Tune batch processing with batchSize (default 5, max 10) and skipCache (ignore the 7-day result cache).
Control failure behavior with failOnMostlyEmpty; by default it errors if more than half the rows are empty, but false returns rows with resolution_status and empty_reason.
Run read-only, requiring APIFY_TOKEN and Apify credits, while polling the Apify actor run to completion (up to 1,800 seconds plus 2 minutes).
Provides access to the Mamba Labs GTM Suite repository and Mamba Labs GitHub organization, where the MCP server's source and license are hosted.
Allows enriching a GitLab company domain into structured firmographics such as employee band, industry, HQ, founded year, and revenue estimate.
Allows enriching a Notion company domain into structured firmographics such as employee band, industry, HQ, founded year, and revenue estimate.
Allows enriching a Stripe company domain into structured firmographics such as employee band, industry, HQ, founded year, and revenue estimate.
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., "@Company Firmographic Enricher MCP ServerEnrich stripe.com: employees, industry, HQ, founded year, and revenue estimate."
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.
Company Firmographic Enricher MCP Server
An MCP server that exposes the Mamba Labs Company Firmographic Enricher as a single tool. Install one package and give your MCP client a way to turn a company domain into structured firmographics, wrapping the Mamba Labs actor on Apify and returning Clay-ready flat JSON with source provenance.
What's Inside
Related MCP server: mcp-job-board-keyword-signal-scanner
What it does
This server gives an AI client one tool:
enrich_company_firmographics: enrich a company domain into employee band, industry, HQ, founded year, revenue estimate, logo, and description, parsed from the company's schema.org/Organization JSON-LD and HTML meta tags. Every record includes asource_signalsarray and adata_completenessscore.
All of the work runs on Apify. This package is a thin client that routes the tool call to the actor and hands back the result.
Quick start
You need Node.js 18 or newer and an Apify account with an API token.
Add this to your Claude Desktop config:
{
"mcpServers": {
"company-firmographic-enricher": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-company-firmographic-enricher"],
"env": {
"APIFY_TOKEN": "your-apify-token"
}
}
}
}Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The tool will be available.
Prerequisites
Node.js 18 or newer
An Apify account with an API token
Example prompts
"Enrich stripe.com: employees, industry, HQ, founded year, and revenue estimate."
"What firmographics can you find for gitlab.com, and how complete is the data?"
"Pull company firmographics for these domains: stripe.com, gitlab.com, notion.so."
"Find the employee band and HQ location for acme.com."
Tool and inputs
enrich_company_firmographics:
domain(string): bare company domain to enrich, e.g. stripe.com. Provide this ordomains.company_name(string): optional company name, used as a fallback label when the page does not expose one.domains(array): list of bare domains for batch processing. Takes precedence overdomain.batchSize(number): domains enriched concurrently per wave in batch mode. Default 5, maximum 10.skipCache(boolean): force a fresh enrichment and ignore the 7 day result cache.failOnMostlyEmpty(boolean): by default the run ends FAILED when more than half the rows resolve no firmographic field, and this tool then returns an error. The rows are still saved, each withresolution_statusandempty_reason. Set false to end the run SUCCEEDED and get the rows back. Default true.
The tool starts the actor run and polls it to a finished status, so a long run is not cut off at 300 seconds. The run is allowed 1,800 seconds. If it is still going two minutes after that, the call stops waiting and returns the run ID with a link to it in the Apify Console, where the results land when it finishes. A run that does not succeed comes back as an error with its run ID and status.
Full actor documentation
For the complete input and output reference, pricing, and run history, see the Company Firmographic Enricher actor on the Apify Store (immutable actor ID YlUtLWjfPpqykmB8g):
https://apify.com/mambalabs/company-firmographic-enricher
Mamba Labs GTM Suite
This server is part of the Mamba Labs GTM Suite, a fleet of 54 MCP servers for go-to-market data, each backed by a dedicated Apify actor. The table lists the actors the suite started with; every server is listed at https://mambabuilt.com.
Actor | Immutable Actor ID |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
|
Built by Mamba Labs | npm | Apify Store
License
MIT
Built by Mamba Labs. https://apify.com/mambalabs
Available Tools
1 toolenrich_company_firmographicsEnrich Company FirmographicsARead-onlyIdempotent
Enrich a company domain into structured firmographics: employee band, industry, HQ, founded year, revenue estimate, logo, and description, with source provenance. Parsed from the company's schema.org/Organization JSON-LD and HTML meta tags and returned as a flat, Clay-ready JSON row with a source_signals array and a data_completeness score. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | No | Bare company domain to enrich, e.g. stripe.com. Provide this or domains. | |
| company_name | No | Optional company name, used as a fallback label when the page does not expose one. | |
| domains | No | List of bare domains for batch processing. Takes precedence over domain. | |
| batchSize | No | Domains enriched concurrently per wave in batch mode. Default 5, maximum 10. | |
| skipCache | No | Force a fresh enrichment and ignore the 7 day result cache. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds value by explaining the data extraction method (schema.org JSON-LD and HTML meta tags) and output structure (source_signals array, data_completeness score), which go beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is relatively concise, with the main purpose front-loaded. It includes necessary details about output format and batch processing without excessive length.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 5 parameters, no output schema, and sibling tools, the description covers input, output structure, extraction method, batching, caching, credit consumption, and token requirement. It is complete for the agent to understand usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all parameters. The description does not add much for most params, but it does clarify the default cache duration (7 days) for skipCache. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'enrich' and the resource 'company domain' and lists the specific firmographics fields (employee band, industry, HQ, etc.). However, it does not explicitly distinguish from siblings like 'resolve_company_identity' or 'get_company_changes', though the output fields are unique.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description mentions the tool is read-only and requires an APIFY_TOKEN and consumes credits, but provides no guidance on when to use this vs. siblings or what prerequisites (beyond token) are needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
enrich_company_firmographics
TDQS
Scored across 1 tool
With only one tool, there is no ambiguity or overlap. The single tool has a clear, well-defined purpose.
The single tool name 'enrich_company_firmographics' follows a clear verb_noun pattern, which is consistent within the set.
One tool is slightly thin but appropriate for a narrow-scope server focused solely on enriching firmographics from a company domain. It covers the core functionality without unnecessary bloat.
For the stated purpose of enriching firmographics from a domain, the single tool covers the primary operation. Minor gaps like batch enrichment or caching are absent but not critical for a read-only enrichment service.
Maintenance
Related MCP Connectors
Enrich any domain into a full company profile with firmographics and buying signals.
Company enrichment for AI agents: firmographics, tech stack, headcount, funding, domain emails.
Company enrichment API: firmographics from a domain or IP address. Identifies website visitors.
Firmfold: company enrichment by domain/email/name: logo, tech, contacts, jobs, firmographics.
Related MCP Servers
- AlicenseAqualityAmaintenanceDetects a company's technology stack from its public web presence. Returns structured tech signals for sales targeting and competitive analysis.195 npm1MIT
- AlicenseAqualityAmaintenanceScans job boards for keyword patterns that indicate buying intent, technology adoption, or team expansion. Returns structured signal data for outbound targeting.175 npm2MIT
- AlicenseAqualityAmaintenanceResolves a company domain to its LinkedIn company page URL. Lightweight enrichment tool for sales and prospecting workflows.152 npm2MIT
- AlicenseAqualityAmaintenanceRuns all GTM signal tools in a single call and returns a unified company intelligence report combining hiring, tech stack, LinkedIn, and job board data.148 npmMIT