Company Firmographic Enricher
@mambalabsdev
Enrich a company domain into structured firmographics: employee band, industry, HQ location, founded year, revenue estimate, logo, and description. Extracts data from schema.org JSON-LD and HTML meta tags with per-field source provenance. Flat JSON output, Clay ready.
Overview
What is Company Firmographic Enricher?
Company Firmographic Enricher is an MCP server that takes a company domain and returns structured firmographic data with source provenance. It is designed for developers and sales intelligence workflows that need automated company research.
How to use Company Firmographic Enricher?
Install by adding the server configuration to your MCP client, specifying the command npx and argument @mambalabsdev/mcp-company-firmographic-enricher. Set the APIFY_TOKEN environment variable with a valid Apify API token, then call the tool enrich_company_firmographics with a company domain.
Key features of Company Firmographic Enricher
- Enriches a company domain into structured firmographic data
- Returns employee band, industry, HQ location, and founded year
- Includes revenue estimate, logo URL, and description
- Provides source signals and a data completeness score
Use cases of Company Firmographic Enricher
- Automate lead enrichment for sales prospecting
- Validate firmographic data during CRM imports
- Quickly research companies for market analysis
- Enhance account scoring with structured firmographics
FAQ from Company Firmographic Enricher
What data does the enrichment return?
It returns employee band, industry, HQ location, founded year, revenue estimate, logo URL, description, source signals, and a data completeness score.
What runtime or API key is required?
The server requires an Apify API token set as the APIFY_TOKEN environment variable.
How do I invoke the tool?
Call the tool enrich_company_firmographics with a company domain (e.g., stripe.com).
Is this server part of a larger suite?
Yes, it is part of the Mamba Labs GTM intelligence suite.
What transport does the server use?
The README does not specify transport details.
