Skip to main content
Glama
mambalabsdev

Company Firmographic Enricher MCP Server

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Company Firmographic Enricher MCP Server

Smithery Glama score MCP Registry npm version npm downloads license mcpservers.org

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-gtm-tech-stack-signal-scraper

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 a source_signals array and a data_completeness score.

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 or domains.

  • 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 over domain.

  • 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.

Full actor documentation

For the complete input and output reference, pricing, and run history, see the Company Firmographic Enricher actor on the Apify Store (canonical immutable Actor ID URL):

https://apify.com/mambalabs/YlUtLWjfPpqykmB8g

Mamba Labs GTM Suite

This server is part of the Mamba Labs GTM Suite, a fleet of twelve specialized MCP servers for go-to-market signal intelligence, each backed by a dedicated Apify actor.

Actor

Immutable Actor ID

GTM Hiring Signal Scraper

D7O1SA2EqwHGsGr1P

GTM Tech Stack Signal Enrichment

qyd7nNyqFPelQViBx

GTM Signals Aggregator

xKdRfnfFNkdMpFuNs

Job Board Keyword Signal Scanner

4DvqpvhMR74NLcDDY

Domain to LinkedIn URL Resolver

3HtnSaqPHOg1Qg5gx

ICP Fit Scorer

W161DT8W4kW55dMFh

Domain Deliverability Checker

0tVgxI7A6o9jMlxmc

Company Firmographic Enricher

YlUtLWjfPpqykmB8g

Company Social Presence Mapper

4k6CCemkgBDz18m2h

Company Identity Resolver

lr8fTRAmZCBZmuwwh

Company Change-Event Feed

oX44rS0fkEJ3rXLWe

Funding & Press Signal Scanner

FS13X6dhQVgX3XOM6

Built by Mamba Labs | npm | Apify Store

License

MIT

Built by Mamba Labs. https://apify.com/mambalabs

Available Tools

1 tool
enrich_company_firmographicsEnrich Company FirmographicsA
Read-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.

ParametersJSON Schema
NameRequiredDescriptionDefault
domainNoBare company domain to enrich, e.g. stripe.com. Provide this or domains.
company_nameNoOptional company name, used as a fallback label when the page does not expose one.
domainsNoList of bare domains for batch processing. Takes precedence over domain.
batchSizeNoDomains enriched concurrently per wave in batch mode. Default 5, maximum 10.
skipCacheNoForce a fresh enrichment and ignore the 7 day result cache.

TDQS

A3.8/5.0
Behavior4/5

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.

Conciseness4/5

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.

Completeness5/5

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.

Parameters3/5

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.

Purpose4/5

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.

Usage Guidelines3/5

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. 1 tool updatev1.0.0
    • First observedenrich_company_firmographics
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no ambiguity or overlap. The single tool has a clear, well-defined purpose.

Naming Consistency5/5

The single tool name 'enrich_company_firmographics' follows a clear verb_noun pattern, which is consistent within the set.

Tool Count4/5

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.

Completeness4/5

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

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers