dxe-mcp
<!-- mcp-name: io.github.qso-graph/dxe-mcp -->
# dxe-mcp
[](https://pypi.org/project/dxe-mcp/)
> ### 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](https://github.com/qso-graph/qso-graph-devel/issues/50).
Part of the [qso-graph](https://qso-graph.io/) project.
## Install
```bash
uvx dxe-mcp # run it; nothing to install
```
## 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
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?"
## License
GPL-3.0-or-later. See [LICENSE](LICENSE).
TDQS
Scored across 1 tool
With only a single tool exposed, there is no possibility of overlap or misselection. The one tool's purpose (returning version and development status) is unambiguous.
get_version_info follows a clean verb_noun snake_case convention, but with only one tool there is no repeated pattern to confirm consistency. It is readable and predictable, so it earns a solid but not maximal score.
A single trivial informational tool is an extremely thin surface for a server named dxe-mcp, whose apparent domain is unclear. It is hard to see this as a well-scoped toolset rather than a stub.
The surface offers only version/status introspection with no other operations, so any real workflow would hit a dead end. Without a discernible domain, coverage cannot be meaningfully satisfied beyond a health-check.