Skip to main content
Glama
LeonardMichalas

peering-mcp

by LeonardMichalas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to peering-mcp

No user-submitted related servers found.

    Related Servers

    • bgphorizon-mcp by bgphorizon

      bgphorizon-mcpofficial

      bgphorizon
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to query global BGP routing intelligence, including network investigation, origin history, reachability, and health checks, with 15 tools plus resources and prompts for incident triage and reporting.
      18
      MIT

    • PeerGlass

      duksh
      A
      license
      A
      quality
      C
      maintenance
      Provides global internet resource intelligence by querying RIRs for IP and ASN data, routing visibility, and network health. It enables users to perform RPKI validation, BGP inspection, and historical allocation analysis through natural language or a REST API.
      42
      1
      MIT

    • The Aleph MCP

      NU-AquaLab
      A
      license
      A
      quality
      C
      maintenance
      Provides LLMs with network intelligence capabilities including PTR record lookups, ASN analysis, traceroute enrichment, and real-time network monitoring through The Aleph API.
      13
      4 npm
      MIT

    • @ipgeolocationapi/mcp

      thebigasif
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query IP intelligence tools such as geolocation, VPN/security checks, ASN, timezone, astronomy, user-agent parsing, abuse contacts, and bulk lookups via natural language.
      19 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.6/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no risk of confusing it with another tool. The tool's purpose and arguments are clearly stated, and it does not overlap with any other present tool.

    Naming Consistency5/5

    The sole tool uses a clear snake_case verb_noun naming pattern (lookup_network). With only one tool, there is no inconsistency to assess against other tools.

    Tool Count2/5

    The server appears intended for peering/interconnection queries, but offers only one tool. The description itself references other needed tools such as find_common_presence and lookup_registration, making the count too thin for the apparent scope.

    Completeness2/5

    Significant gaps exist: the only tool cannot find where networks meet or look up address registration, yet the description says those are separate tools. Agents would hit dead ends for common interconnection questions beyond basic AS/name lookup.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources