Skip to main content
Glama
mambalabsdev

mcp-outbound-infrastructure-fingerprint

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-outbound-infrastructure-fingerprint

No user-submitted related servers found.

    Related Servers

    • BasicSec MCP Server

      marlinkcyber
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables DNS and email security analysis through passive and active scanning capabilities. Provides comprehensive domain security checks including SPF, DMARC, DNSSEC validation, MX record analysis, and SMTP connectivity testing.
      MIT

    • mcp-deliverability

      jonathanngiroux-star
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables checking email deliverability for domains or IPs, tracking IP reputation over time, and analyzing bounce patterns and issues.
      MIT

    • Sendermap

      marmot7775
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to map every service that sends or receives mail as a domain, listing each vendor with the public DNS, certificate-log and website evidence behind it, how confident the match is, and what is missing or misconfigured. It also exposes a single vendor's patterns, proofs and documented setup for agents to query.
      1,307 PyPI
      1
      MIT

    • email-deliverability-mc

      kryptoscan
      A
      license
      A
      quality
      D
      maintenance
      Checks email deliverability: audits a domain's SPF (including the 10-lookup limit), DKIM, DMARC and MX records with ranked fixes, checks a sending IP's reverse DNS and blocklist listings, and tests email headers against Gmail and Yahoo bulk sender requirements.
      3
      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.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clearly defined and distinct.

    Naming Consistency5/5

    The single tool name follows a clear verb_noun pattern ('fingerprint_outbound_infrastructure'), and with only one tool there is no inconsistency to evaluate.

    Tool Count4/5

    The server contains only one tool, which is slightly below the typical 3-15 range, but the tool is comprehensive and serves a very narrow, specific purpose, making the single-tool count reasonable.

    Completeness5/5

    The tool covers the full scope of outbound infrastructure fingerprinting: detecting sending domains, inbox providers, sending platforms, registration clusters, infrastructure vendors, and deliverability posture. No obvious gaps are apparent for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources