Skip to main content
Glama
qso-graph

omiss-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to omiss-mcp

No user-submitted related servers found.

    Related Servers

    • iota-mcp

      qso-graph
      A
      license
      A
      quality
      C
      maintenance
      Enables IOTA group lookup, island search, DXCC mapping, nearby groups, and programme statistics through any MCP-compatible AI assistant.
      7
      GPL 3.0

    • wspr-mcp

      qso-graph
      A
      license
      A
      quality
      C
      maintenance
      Enables querying WSPR beacon data including live spots, band activity, top beacons, propagation paths, and SNR trends through any MCP-compatible AI assistant.
      9
      22 PyPI
      GPL 3.0

    • hamqth-mcp

      qso-graph
      A
      license
      A
      quality
      D
      maintenance
      MCP server for HamQTH.com — callsign lookup, DX cluster spots, Reverse Beacon Network, DXCC resolution, and more through any MCP-compatible AI assistant.
      8
      25 PyPI
      GPL 3.0

    • peering-mcp

      LeonardMichalas
      A
      license
      A
      quality
      B
      maintenance
      Gives AI agents access to public internet interconnection data, letting them look up which networks connect to each other, at which internet exchanges and facilities they are present, under what peering policy, and who a given IP range or AS number is registered to. Responses are compact, sourced and aged, and it distinguishes missing records from genuinely absent networks rather than guessing.
      1
      64 PyPI
      MIT

    • qrz-mcp

      qso-graph
      A
      license
      A
      quality
      D
      maintenance
      MCP server for QRZ.com — callsign lookups, DXCC entity resolution, and logbook queries through any MCP-compatible AI assistant.
      6
      3
      GPL 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

    A3.7/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target clearly different OMISS concepts: schedule vs. live nets, member lookup vs. awards, officers vs. statistics. However, omiss_checkin_history and omiss_net_checkins both deal with past net check-ins, and omiss_awards overlaps slightly with omiss_award_rules when called without an award_id. These overlaps are mild but could cause occasional misselection.

    Naming Consistency3/5

    Most tools use an omiss_ prefix followed by a noun phrase (e.g., omiss_net_schedule, omiss_member_lookup, omiss_awards), which is fairly consistent. But a few deviate: get_version_info lacks the prefix and uses get_, while omiss_set_callsign mixes a verb into the pattern. The overall convention is readable but not uniform.

    Tool Count5/5

    13 tools is well within the ideal 3-15 range for this domain. Each tool covers a distinct OMISS reference area (schedule, live nets, check-ins, awards, officers, statistics) and none appear redundant or excessive.

    Completeness4/5

    The surface covers major OMISS reference needs: schedules, live nets, member lookup, check-in history and detail, statehood schedule, officers, awards, and net statistics. Minor gaps exist, such as no explicit tool to browse upcoming nets beyond the schedule or to create/update user-specific data beyond setting a callsign, but these are unlikely to block common agent workflows.

    Maintenance

    ActivityNo data
    ResponsivenessUnresponsive

    Resources