Skip to main content
Glama
axelfreeman

TAPAC MCP

by axelfreeman

Related Servers

Alternatives to TAPAC MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Lead generation MCP server for AI agents. Find emails, verify contacts, enrich profiles, and search prospects using Hunter.io, Apollo.io, and Abstract API.
      8
      13 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server providing real-time access to comprehensive B2B company and contact data for lead generation and business intelligence. It enables AI tools to search firmographics, discover key contacts, and automate personalized outreach workflows.
      55
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that enables AI agents to discover and qualify B2B leads from Leadbay's knowledge base, with tools for lead research, enrichment, and outreach logging.
      MIT
    • 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
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server giving AI agents real-time web search, page scraping, company intelligence, email discovery, local lead generation, and a persistent knowledge graph. Pay only for what you use, no subscriptions.
      12 npm
      MIT

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools serve completely distinct purposes: one checks server status, the other finds contacts. There is no overlap or ambiguity.

    Naming Consistency5/5

    Both tools follow a consistent snake_case pattern with the prefix 'tapac_', one describing a state (status) and the other an action (find_contacts). The naming is uniform.

    Tool Count3/5

    With only two tools, the server feels thin for a contact-finding service, but each tool is clearly defined and serves a necessary function. It is borderline but not excessive.

    Completeness4/5

    The server covers the core operation of finding and verifying contacts with extensive filtering, plus a status check. Minor gaps like retrieving a specific contact by ID are absent, but the main workflow is complete.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive