Skip to main content
Glama
bitterdev

dropscan-mcp

by bitterdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to dropscan-mcp

No user-submitted related servers found.

    Related Servers

    • mailbox-mcp

      arbengine
      A
      license
      B
      quality
      C
      maintenance
      Official mailbox.bot MCP server for AI agents. Send letters, certified mail and postcards, and give an agent its own street address + postal mailbox number. Agent receiving virtual mailboxes with a real street address are live now at $15/mo in Manhattan Beach, CA. Sandbox keys, approval controls, tracking and webhooks.
      55
      124 npm
      2
      MIT

    • guerrillamail-mcp

      cv3inx
      A
      license
      A
      quality
      C
      maintenance
      MCP server for the Guerrilla Mail temporary/disposable email API. Spin up throwaway inboxes, poll for mail, and read messages from any MCP client.
      6
      5 npm
      1
      MIT

    • mcp-email

      algonacci
      A
      license
      Not graded
      quality
      D
      maintenance
      A minimal MCP server for reading, searching, managing, and sending email over IMAP and SMTP.
      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

    A3.5/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear boundaries between scanboxes, mailings, recipients, forwarding addresses, webhook rules, and shipments. No overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, making the set predictable and easy to navigate.

    Tool Count4/5

    21 tools is slightly high but justified by the multi-entity domain (scanboxes, mailings, recipients, etc.). Each tool serves a specific purpose, though a few could be merged or removed.

    Completeness4/5

    Core CRUD operations are covered for most entities, but missing delete/update for recipients and forwarding addresses. The essential workflows (receive, scan, forward, destroy, manage webhooks) are well-supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources