Dxe Mcp

io.github.qso-graphPublished by GitHub account qso-graphv0.2.0Updated Nov 3, 2026

DXpedition tracking MCP server: active and announced expeditions, QSL routes

VerifiedSTDIODesktop only

Overview

AI-generated overview

Placeholder MCP server for planned DXpedition tracking; it currently exposes only a version-info tool and answers no amateur-radio questions.

What you can do
  • Report the server's version, development status and where the work is tracked
  • No other tools are registered; the package is published only to hold the name while the project is planned
  • Planned, not yet available: listing active and announced DXpeditions with bands, modes and QSL routes, plus online log lookup where a published source allows it
When to use it
Not useful yet for real work. Only worth adding if you want to confirm the package exists or follow the planned DXpedition tracking server; for actual DXpedition questions it will not help.
Requirements
Runs locally over stdio, typically launched with uvx, so a Python/uv environment is needed. No credentials, environment variables or headers are required.
Before you install
The server states it has no working tools yet, so installing it expecting DXpedition answers will disappoint; it only reports version and development status.

Installation

In SourceWeft

  1. Open Dxe Mcp in the dashboard and add it to a workspace.
  2. 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

dxe-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 DXpeditions are on the air now, which are announced, their bands, modes and QSL routes, and online log lookup where a published source allows it.

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

Part of the qso-graph project.

Install

bash
uvx dxe-mcp            # run it; nothing to install

Tools

ToolDescription
get_version_infoService version, development status, and where the work is tracked

Quick Start

No credentials needed — install and configure your MCP client.

Configure your MCP client

dxe-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": {    "dxe": {      "command": "uvx",      "args": ["dxe-mcp"]    }  }}
Claude Code

Add to .claude/settings.json:

json
{  "mcpServers": {    "dxe": {      "command": "uvx",      "args": ["dxe-mcp"]    }  }}
ChatGPT Desktop

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

json
{  "mcpServers": {    "dxe": {      "command": "uvx",      "args": ["dxe-mcp"]    }  }}

Questions it will answer

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

"Which DXpeditions are active right now?"

"What is announced for the next three months, and on which bands?"

"How do I QSL for this expedition?"

Licence

GPL-3.0-or-later. See LICENSE.

Source: README.md at commit c1a3490

Tools

1

get_version_info

Get Version Info

Get this server's version and development status.

Takes no parameters.

Version history

6
  1. v0.2.0LatestOct 29, 2026
  2. v0.1.0Oct 26, 2026
  3. v0.0.5Oct 26, 2026
  4. v0.0.3Oct 26, 2026
  5. v0.0.2Oct 25, 2026
  6. 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