Qso Graph Contest Mcp

io.github.qso-graphPublished by GitHub account qso-graphv0.1.0Updated Oct 29, 2026

Contest calendar and rules MCP server: what is running, what is coming, and the rules

VerifiedSTDIODesktop only

Server details

Identifier: io.github.qso-graph/qso-graph-contest-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Oct 11, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account qso-graph for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.qso-graph%2Fqso-graph-contest-mcp.svg)](https://sourceweft.com/mcp/io.github.qso-graph%2Fqso-graph-contest-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A placeholder MCP server for an amateur radio contest calendar and rules service; it currently exposes only a version-info tool and answers no contest…

What you can do: Report the server's version, development status and where the work is tracked
No contest data tools exist yet: the calendar, rules, exchange and multiplier lookups are only planned
No other capabilities are available in this release
When to use it: Only if you want to check the project's status or hold the package name; it is not useful for answering questions about amateur radio contests, their schedules, exchanges or rules yet.
Requirements: Runs locally over stdio via uvx (Python package qso-graph-contest-mcp). No credentials, environment variables or headers are needed. Desktop MCP clients only; not executable on the web.

Before you install

Installing it expecting a working contest server will disappoint: it registers one tool and does nothing else yet. No data is read or written and no credentials are requested.

Installation

In SourceWeft

Open Qso Graph Contest Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

Tools

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):

json

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

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

Claude Code

Add to .claude/settings.json:

json

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

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

ChatGPT Desktop

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

json

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

{  "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?"

Licence

GPL-3.0-or-later. See LICENSE.

Source: README.md at commit 144e168

Tools

get_version_info

Get Version Info

Get this server's version and development status.

Takes no parameters.

Version history

v0.1.0LatestOct 26, 2026
v0.0.5Oct 26, 2026
v0.0.3Oct 26, 2026
v0.0.2Oct 25, 2026
v0.0.1Oct 11, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts