Skip to main content
Glama
mailpal-com

mailpal-mcp-server

Official
by mailpal-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to mailpal-mcp-server

No user-submitted related servers found.

    Related Servers

    • mailpal-mcp by mailpal-com

      mailpal-mcpofficial

      mailpal-com
      A
      license
      C
      quality
      C
      maintenance
      Free email for AI agents with hardware attestation, real SMTP/IMAP/JMAP, and real-time notifications.
      2
      108 PyPI
      Apache 2.0

    • mcp-email-sender

      AMEOBIUS-space
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to validate email addresses and send emails via SMTP with zero external dependencies.
      MIT
    • InboxAPI CLI by inboxapi

      InboxAPI CLIofficial

      inboxapi
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides an AI agent with its own email address to send, receive, and manage emails via MCP. No email server setup required.
      45 npm
      13
      MIT

    • smails

      pexni
      A
      license
      Not graded
      quality
      D
      maintenance
      Disposable email for humans and AI agents. Enables AI agents to create mailboxes and receive verification emails through an MCP server.
      39
      MIT

    • OutreachEmailMCP

      BreazyLabs
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that acts as an email gateway for Gmail and Microsoft 365, enabling AI agents to send and read emails via MCP tools, with SMTP/IMAP and REST APIs for email sequencing and automation.
      1
      AGPL 3.0
    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

    C2.8/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools target clearly different domains (email vs. hardware identity), so an agent can pick between them without confusion. However, both use an identical generic 'operation' gateway pattern, so the actual sub-operations are not visible as distinct entities and require a readme call to disambiguate.

    Naming Consistency4/5

    Both tools use the same single-word, lowercase product-name convention (mailpal, oneid), which is internally consistent. They do not follow a verb_noun pattern, but they are consistently named gateways rather than mixed styles.

    Tool Count2/5

    Only two tools are exposed for what appears to be a broad email and identity ecosystem, which is thin for the apparent scope. Each tool is a mega-gateway hiding an unknown number of operations behind an 'operation' parameter, making the surface feel under-specified.

    Completeness2/5

    The visible surface only provides two generic dispatcher tools that require a 'readme' call before any real operation can be discovered. There are no explicit create/read/update/delete operations for email or identity, so coverage is opaque and requires exploration rather than being evident from the tool list.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources