Skip to main content
Glama
ready-check-mcp

ready-check-mcp

Related Servers

Alternatives to ready-check-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to run read-only email deliverability checks and record generators, including SPF, DKIM, DMARC, MX, BIMI, MTA-STS, blacklist lookups, header analysis, cold-email and subject-line scoring, and SPF/DMARC/DKIM record creation.
      19 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an agent that reads a person's inbox to check a raw or .eml message and receive a 0-100 cold-outreach score with the reasons behind it. The agent can then avoid replying on the person's behalf to a cold message, or surface a likely cold one with its signals for the person to judge.
      11 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Programmatic email deliverability testing for AI agents. Create inbox placement tests across Gmail, Outlook, Yahoo, Mail.ru, Yandex — get per-provider placement (Inbox/Spam/Promotions), SPF/DKIM/DMARC auth, Rspamd & SpamAssassin verdicts, DNS health (MX, PTR, DNSBL), and live SSE results.
      5
      74 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to check an email address for syntax validity, MX records, disposable/role/free-provider flags, and a deliverability score/verdict, with per-call USDC payment on Base.
      MIT

    TDQS

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools cover clearly non-overlapping actions: analyze an email, read credit balance, and start a credit purchase. Descriptions reinforce the boundaries (balance explicitly 'does not run a check and does not charge credit'; buy_credit 'does not charge anything' until checkout). An agent can select the right tool without ambiguity.

    Naming Consistency5/5

    All names are snake_case and share the ready_check_ prefix, with predictable suffixes (_balance, _buy_credit) for the ancillary operations. The convention is uniform across the whole server.

    Tool Count5/5

    Three tools is exactly the lifecycle of a metered single-purpose service: analyze, check balance, and buy credit. Nothing redundant and nothing that feels like it was bolted on for count's sake.

    Completeness4/5

    The core loop (buy credit -> check balance -> run check) is fully covered, including key generation and idempotency guidance for retries. Minor gaps only: no dedicated key registration/validation tool and no way to surface the list of supported kinds or refund status programmatically, though both are workable via docs or support.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues