Skip to main content
Glama
shahabazdev

Inxmail MCP

by shahabazdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Inxmail MCP

No user-submitted related servers found.

    Related Servers

    • mailtarget

      yopie-org
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Mailtarget that exposes tools to discover and call management API endpoints and send transactional emails via the Transmission API.
      4 npm
      MIT
    • MailPace MCP Server by mailpace

      MailPace MCP Serverofficial

      mailpace
      A
      license
      D
      quality
      D
      maintenance
      An MCP server implementation that allows sending emails over MailPace's fast transactional email API.
      1
      1
      MIT
    • xmit-mcp by sendwithxmit

      xmit-mcpofficial

      sendwithxmit
      F
      license
      Not graded
      quality
      D
      maintenance
      Remote MCP server for the Transmit email platform, enabling email sending, contact management, template and campaign operations via natural language.
      -
    • lingtai-whatsapp by Lingtai-AI

      lingtai-whatsappofficial

      Lingtai-AI
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for interacting with the official Meta WhatsApp Business Platform/Cloud API, enabling sending messages, managing contacts, templates, and handling webhook callbacks.
      Apache 2.0

    • @invapi/mcp-server

      invapi-org
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the Invapi E-Invoicing API, enabling conversion, validation, and extraction of invoices in UBL, CII, ZUGFeRD, Excel, and more.
      26 npm
      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 29 tools

    Disambiguation4/5

    Tools are clearly distinguished by email pipeline (relay vs. event-triggered) and operation type, with excellent cross-referencing in descriptions (e.g., 'use X instead of Y'). Minor overlap exists between composite checkers (check_email_blocked, check_email_delivery) and granular getters, but descriptions explicitly guide preferred usage.

    Naming Consistency5/5

    Strict adherence to verb_noun snake_case throughout (add_to_blacklist, list_relay_bounces, mark_error_log_read). Vocabulary is consistent across parallel tool sets (relay vs. transactional variants use identical verb patterns), making the 29-tool surface predictable.

    Tool Count3/5

    At 29 tools, the surface exceeds the ideal range and feels dense, though justified by the dual-pipeline domain (event-triggered vs. SMTP relay). The consistent naming patterns help manage the complexity, but the count approaches the threshold where agent selection becomes challenging.

    Completeness4/5

    Excellent lifecycle coverage for blacklists/blocklists and comprehensive monitoring (bounces, complaints, reactions, deliveries, error logs) across both email pipelines. Minor gaps include lack of single-item getters for bounces/complaints and no event type management (create/update), which appear to be admin-only functions.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources