Skip to main content
Glama
datalayer-sh

DataLayer MCP

by datalayer-sh

Related Servers

Alternatives to DataLayer MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Argorant MCP Server — give your AI agent direct access to 614M verified B2B contacts. Query by industry, role, geography, and 100+ filters, then export emails verified by a live SMTP probe at request time (catch-alls flagged, invalids free). OAuth-secured. Works with Claude, ChatGPT, Cursor, and any MCP client. Endpoint: https://mcp.argorant.com/mcp
      1
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides MCP clients with 60+ APIs for B2B data enrichment, lead generation, email verification, company intelligence, and agentic GTM workflows.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables B2B lead intelligence through seven tools for company lookup, domain enrichment, person search, email finding, and startup discovery, accessible via MCP for AI agents.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Allows searching and enriching companies, people, job postings, and social posts via the DataForB2B API, bringing lead generation and market intelligence into MCP-compatible clients like Cursor and Claude.
      6
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      Enables AI tools to search and enrich B2B leads, including finding professional emails, company profiles, and filtering people and companies by various criteria.
      5
      343 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no significant overlap: company-focused tools (employees, headcount, jobs, technographics, enrich, lookup, search) and person-focused tools (enrich, lookup, search) are well-separated, and even within categories (e.g., company_employees vs. company_headcount vs. company_jobs) target different data aspects. The descriptions reinforce these distinctions, making misselection unlikely.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, using snake_case uniformly: company_employees, company_headcount, company_jobs, company_technographics, enrich_company, enrich_person, find_intent_signals, lookup_company, lookup_person, search_companies, search_people. This predictability aids agent navigation and understanding.

    Tool Count5/5

    With 11 tools, the count is well-scoped for a data layer server covering company and person enrichment, search, and intent signals. Each tool earns its place by addressing a specific need (e.g., detailed profiles, filtered searches, headcount breakdowns), avoiding bloat while providing comprehensive coverage for the domain.

    Completeness5/5

    The toolset offers complete CRUD-like coverage for the data domain: lookup and search for discovery, enrich for detailed profiles, and specialized tools for headcount, jobs, technographics, and intent signals. There are no obvious gaps; agents can perform end-to-end workflows from finding entities to analyzing their attributes and signals.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues