Skip to main content
Glama
digitalsolutionsmagic

Lead Cleanup MCP Lite

by digitalsolutionsmagic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Lead Cleanup MCP Lite

No user-submitted related servers found.

    Related Servers

    • coldforge

      Makeph
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables personalized cold email outreach through research, drafting, template management, and deliverability checks, all locally with no required API keys.
      6
      MIT

    • omniventure-agent-tools

      dalnaspdal
      A
      license
      A
      quality
      C
      maintenance
      Sub-15ms edge intelligence tools for Claude Desktop, Cursor, and LLM agent loops. Provides sub-millisecond LLM JSON repair, web-to-markdown token compression (cuts context tokens up to 90%), PII redaction, and RFC 5322 B2B email deliverability verification at zero marginal token cost.
      6
      MIT

    • precis-mcp

      AirSaiga
      A
      license
      A
      quality
      B
      maintenance
      Local-first data quality validation for Excel/CSV: schema-aware checks with 10 zero-code constraint types (uniqueness, ranges, foreign keys and more) and row-level error reports.
      4
      4 npm
      3
      Apache 2.0

    • LeadDirect-MCP

      netizen4-bit
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous B2B lead generation by discovering companies, scraping websites for contacts, decoding obfuscated emails, generating email permutations, and verifying email deliverability via MX and SMTP checks.
      2
      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

    A3.6/5.0

    Scored across 2 tools

    Disambiguation3/5

    Both tools operate on email validity: clean_leads already drops invalid emails, so validate_email is essentially a single-item subset of the bulk tool. The descriptions do clarify scope (one address vs. a whole list), which keeps an agent from complete confusion, but the boundaries overlap.

    Naming Consistency5/5

    Both names follow the same verb_noun snake_case pattern (clean_leads, validate_email) and the verbs accurately describe the actions.

    Tool Count3/5

    Two tools is thin even for a 'Lite' server; the surface is a bulk operation plus one narrow helper rather than a balanced set. It is not egregiously over- or under-scoped, but it sits at the borderline.

    Completeness4/5

    clean_leads covers the core domain (normalize names, emails, phones, websites, drop invalid, dedupe) and validate_email gives a quick single-address check. Minor gaps exist — no standalone phone/website validation or single-lead normalization, though an agent can pass a one-item list as a workaround.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources