Skip to main content
Glama
mambalabsdev

mcp-gtm-signals-aggregator

Related Servers

Alternatives to mcp-gtm-signals-aggregator

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      GTM signal intelligence suite for AI agents. Six tools: hiring signals, tech stack detection, company-to-LinkedIn resolution, ICP scoring, job board scanning, and a combined signals aggregator. Built for outbound sales workflows.
      21
      140 npm
      3
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      Delivers comprehensive company intelligence in a single tool call, aggregating profiles, tech stacks, key people, news, and corporate data from any domain or company name. Sources data from Wikipedia, GitHub, OpenCorporates, and web scraping to provide structured business insights using only free public APIs.
      6
      52 npm
      4
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Scans job boards for keyword patterns that indicate buying intent, technology adoption, or team expansion. Returns structured signal data for outbound targeting.
      1
      86 npm
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables enrichment of company domains with verified firmographic signals including tech stack, hiring activity, email infrastructure, and SOC 2 compliance, returning compact typed JSON for AI agents.
      3
      7 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool in the set, there is no possibility of an agent confusing it with another tool. Its purpose—producing a composite GTM score plus recommended action—is stated unambiguously.

    Naming Consistency4/5

    The single name aggregate_gtm_signals follows a clean verb_noun snake_case convention that would scale predictably. Consistency cannot be fully demonstrated across a set of one, so it falls just short of a 5.

    Tool Count3/5

    A single tool is borderline thin for a server branded as a 'signals aggregator'; the composite design is defensible, but there is no surface for retrieving individual signals, batching companies, or inspecting components.

    Completeness3/5

    The one-tool surface covers the headline aggregation use case end-to-end, but it is read-only and monolithic, leaving no way to access raw hiring/tech-stack signals, batch multiple companies, or tune scoring inputs.

    Maintenance

    ActivityActive
    ResponsivenessResponsive