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

qso-graph-contest-mcp

by qso-graph

qso-graph-contest-mcp

PyPI

In development

This package is published so the name is held while the work is planned in the open. It registers one tool, get_version_info, and does nothing else yet. If you install it expecting a working server, that is what you will find—which is why it says so here, in the server's own instructions, and in the one tool it has.

PyPI does not reserve a name for a pending trusted publisher, so a name is only held once something is actually published. Given that, a package that says what it is beats an empty one that does not.

Which contests are running now, what is coming, and the rules, exchange and multipliers for each—with every contest citing the sponsor that published its rules. Named for this project rather than any sponsor: a server covering many sponsors' contests cannot take one sponsor's name.

Planned work, including the data sources it would use and whether each is actually available, is tracked in qso-graph-devel#49.

Part of the qso-graph project.

Install

uvx qso-graph-contest-mcp            # run it; nothing to install

Related MCP server: Agent Workstation

Tools

Tool

Description

get_version_info

Service version, development status, and where the work is tracked

Quick Start

No credentials needed—install and configure your MCP client.

Configure your MCP client

qso-graph-contest-mcp works with any MCP-compatible client. Add the server config and restart.

Claude Desktop

Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows):

{
  "mcpServers": {
    "qso-graph-contest": {
      "command": "uvx",
      "args": ["qso-graph-contest-mcp"]
    }
  }
}

Claude Code

Add to .claude/settings.json:

{
  "mcpServers": {
    "qso-graph-contest": {
      "command": "uvx",
      "args": ["qso-graph-contest-mcp"]
    }
  }
}

ChatGPT Desktop

Configure via Settings > Apps & Connectors, or in your agent definition:

{
  "mcpServers": {
    "qso-graph-contest": {
      "command": "uvx",
      "args": ["qso-graph-contest-mcp"]
    }
  }
}

Questions it will answer

Not yet—these are what the finished server is for:

"What contests are running this weekend?"

"What is the exchange for this contest, and who sponsors it?"

"Which upcoming contests are CW only on 40m?"

License

GPL-3.0-or-later. See LICENSE.

Available Tools

1 tool
get_version_infoGet Version InfoA
Read-onlyIdempotent

Get this server's version and development status.

Inputs: no named parameters. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    Related MCP Connectors

    Related MCP Servers

    • 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
    • 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
    • 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.
      -