Skip to main content
Glama
Sign In
qso-graph-contest-mcp

qso-graph-contest-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to qso-graph-contest-mcp

No user-submitted related servers found.

    Related Servers

    • dxe-mcp

      qso-graph
      A
      license
      A
      quality
      A
      maintenance
      Currently enables MCP clients to retrieve service version and development status, with planned support for querying active and announced DXpeditions, their bands, modes, and QSL routes.
      1
      115 PyPI
      GPL 3.0

    • Agent Workstation

      zix-chen
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to drive developer workflows through APIs and CLIs, with explicit workspace or trusted-workstation launch modes, bounded command previews, multi-repository rules discovery, and an on-demand skills/recipes entry point. It lets agents review changes, run commands, and load only the smallest relevant rule or skill while reporting evidence and unverified steps.
      19
      1
      Apache 2.0

    • pea-tracker

      damienSavoldelli
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to initialize, discover registered tools, and invoke the diagnostic ping tool, returning structured service metadata and a UTC timestamp. It currently exposes public diagnostics only, with no portfolio or market-data access.
      MIT

    • MCPHub

      FlameZerg
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables users to aggregate, discover, and route remote MCP tools through a unified endpoint, with category-based access tokens, OAuth authorization, and admin management/analytics for self-hosted infrastructure.
      -

    • yala

      MalekYala
      A
      license
      A
      quality
      D
      maintenance
      MCP server exposing 570 config-driven dev tools across plan, develop, QA, feedback automation, and deploy stages, with meta-tools for searching and running them via natural language.
      4
      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

    B3.3/5.0

    Scored across 1 tool

    Disambiguation4/5

    With only one tool there is no possibility of tool-to-tool confusion, and get_version_info has a clear, distinct meaning. It can't score a 5 since there's no set to differentiate.

    Naming Consistency4/5

    The single tool follows a clean, predictable verb_noun pattern (get_version_info). Consistency is trivially satisfied but the convention itself is clear and readable.

    Tool Count1/5

    A server named qso-graph-contest-mcp implies contest/QSO graph querying functionality, yet offers only one metadata tool. This is an extreme mismatch between the apparent scope and the surface.

    Completeness1/5

    No contest, QSO, or graph operations exist—no query, ingest, or aggregation tools. The only tool returns server version/development status, so agents cannot perform any domain workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Resources