Skip to main content
Glama
Sign In
Cold Leads MCP server

Cold Leads MCP server

by anttka4cz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Cold Leads MCP server

No user-submitted related servers found.

    Related Servers

    • mxprobe

      andrewchmr
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to verify email addresses and receive a 'send', 'hold', or 'kill' verdict with the reason, while also managing signup and credits programmatically.
      5
      2
      MIT

    • Email Verifier MCP Server

      iguha0
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to verify email addresses in real-time, checking syntax, DNS, MX records, and SMTP handshake, returning verdicts and deliverability scores without sending actual emails.
      -

    • sabit-mcp

      ruwadgroup
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to verify email addresses through a multi-signal probabilistic pipeline, returning confidence scores and honest statuses (safe/risky/invalid/unknown) with evidence.
      Apache 2.0
    • Mailveri MCP Server

      Mailveri MCP Serverofficial

      mailveri
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to verify email deliverability and check mailbox existence, manage bulk verification batches, and monitor verification credit balances directly from chat.
      6
      1
      MIT
    • FindLeadEmails MCP server

      FindLeadEmails MCP serverofficial

      findleademails
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to find and verify B2B work emails for individuals or bulk lists, with deliverability checks, background job processing, and paginated result retrieval.
      MIT
    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.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct action: search_leads reads the local CRM, verify_email validates an address, and the two provisioning tools handle account creation versus status/API-key retrieval. The onboarding pair shares a domain but their descriptions clearly separate their roles, so an agent can pick correctly.

    Naming Consistency4/5

    Names are consistently snake_case and predominantly verb_noun (search_leads, verify_email, check_provisioning_status). Only provision_account_and_get_payment_link is an unusually long compound, a minor deviation but still verb-led and readable.

    Tool Count4/5

    Four tools is lean but each earns its place: one read, one verification, and a two-step account onboarding flow. Slightly thin for a CRM-style server but well-scoped rather than padded.

    Completeness3/5

    The domain spans leads, verification, and onboarding, but the lead surface only offers search — there is no create/update/delete or tag/stage management, so agents cannot populate or mutate the CRM. Core read+verify workflows work, but lifecycle coverage for leads has notable gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources