Skip to main content
Glama
dxe-mcp

dxe-mcp

by qso-graph

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

IN DEVELOPMENT — this server has no working tools yet, and calling it will not answer questions about dxpedition tracking mcp server. Planned: 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. Progress: https://github.com/qso-graph/qso-graph-devel/issues/50

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_version_infoA

Get this server's version and development status.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityMaintained
ResponsivenessLimited data