Skip to main content
Glama

Related Servers

Alternatives to Lead Leak Check

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that lets agents run free, keyless lead-leak audits on UK local service businesses — detecting form platforms and their outreach implications, checking whether phone numbers are tappable tel: links, comparing phone numbers across a site and free directories, screening website hygiene, and locating a business's own site. It also bundles these into a single full audit that returns a prioritised list of fixable issues alongside top local competitors.
      6
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A local-first MCP server for auditing, drafting, and planning updates to your personal LinkedIn profile safely, without automation or scraping.
      10
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An unofficial MCP server for Smartlead that exposes the SmartProspect API and core Smartlead operations, enabling agents to search for leads, manage campaigns, and control credit spending with configurable safety modes.
      39
      18 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that parses Terraform .tfstate files and lets AI agents audit enterprise infrastructure for security misconfigurations without requiring direct cloud credentials.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      SDK-free MCP server framework with self-implemented protocol engine (MCP 2026-07-28 + legacy), 19 built-in plugins, OWASP MCP Top 10 security, and zero external dependencies.
      52 npm
      2
      MIT

    TDQS

    A3.5/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools target distinct input types: structured config, plain-English description, and run-history CSV. However, check_pipeline and check_pipeline_description have nearly identical names and purposes, which could cause misselection when the input format is ambiguous.

    Naming Consistency5/5

    All tools use consistent snake_case verb_noun naming (check_pipeline, check_pipeline_description, analyze_run_history). The longer check_pipeline_description is still predictable within the same convention.

    Tool Count4/5

    Three tools are well-scoped for a focused lead-leak diagnostic server. The count is slightly thin and two tools are input-format variants of the same check, but neither is excessive.

    Completeness4/5

    The surface covers structured pipeline checks, natural-language descriptions, and run-history analysis, which are the main diagnostic inputs. Minor gaps remain: no tool to consolidate findings or recommend fixes, and no direct lead-level audit.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues