Skip to main content
Glama
jamalofski

MailProbe

by jamalofski
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to MailProbe

No user-submitted related servers found.

    Related Servers

    • Email Verifier MCP

      PanStories
      A
      license
      A
      quality
      B
      maintenance
      Enables agents to validate email addresses through RFC 5321 syntax checks, MX record lookups, a 182,000-domain disposable blacklist, role-account detection, and an optional SMTP handshake. Runs locally via npx or as a hosted HTTP endpoint, returning explainable per-check scores at zero per-lookup API cost.
      4
      MIT

    • email-validator-api

      lazymac2x
      F
      license
      Not graded
      quality
      D
      maintenance
      Comprehensive email validation MCP server that checks syntax, MX records, disposable domains, role-based accounts, SPF/DKIM, typo suggestions, and risk scoring.
      -

    • mailverdict

      mailverdict
      A
      license
      Not graded
      quality
      B
      maintenance
      Keyless email validation: disposable/burner, role-account, and free-provider detection, MX checks, and typo suggestions. Tools: check_email, check_domain.
      MIT

    • tvram-backend-mcp

      amoghar29
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes an email verification tool, returning verdicts of valid, invalid, or risky with reasons.
      -

    • InboxValid MCP Server

      siddreddy07
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides email verification as an MCP tool, checking format, disposable domains, and mail server availability with structured results.
      -
    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.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools target entirely different concerns: verifying addresses versus reading the account credit balance. There is no plausible way to confuse one with the other, and the descriptions make the boundary explicit ('Reading the balance uses no credit').

    Naming Consistency5/5

    Both names follow a clean verb_noun snake_case pattern (verify_emails, get_credits) with the noun reflecting the resource being acted on. No mixing of conventions.

    Tool Count3/5

    Two tools is thin for a standalone server, even a narrowly scoped one. The surface is arguably complete for a pure verification API, but a status/account or batch-history tool would round it out.

    Completeness4/5

    verify_emails is a fully-featured core operation (batch limits, per-status semantics, scoring, typo suggestions) and get_credits covers the account concern. Minor gaps remain, such as account details or a past-verification history/results lookup.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources