Eqsl Mcp

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

eQSL.cc MCP server. Inbox download, QSO verification, Authenticity Guaranteed status.

Overview

AI-generated overview

Local MCP server for eQSL.cc that lets an assistant download incoming eQSLs, verify QSOs, check AG status and query upload history.

What you can do
  • Download incoming eQSLs with date and confirmation filters, or fetch the whole inbox as raw ADIF text for import into a logger
  • Verify whether a specific QSO exists in eQSL, and check whether a callsign has Authenticity Guaranteed (AG) status
  • Check when a persona last uploaded QSOs to eQSL
  • Report the service version and the upstream eQSL.cc endpoint version in use
When to use it
Useful for amateur radio operators who log contacts and want an assistant to review received eQSL confirmations, confirm a contact exists, or check another station's AG status without opening the eQSL.cc site.
Requirements
Runs locally as a Python package via uvx (Python tooling required). Credentialed tools need qso-graph-auth installed, with a persona created, the eqsl provider enabled and eQSL username and password stored there. The verify and AG tools work without credentials; mock mode is available for testing.
Before you install
The inbox and download tools need your eQSL.cc account credentials, which are stored through qso-graph-auth rather than in this server's own configuration. Downloads return your inbox contents, so treat the ADIF output as personal data. The AG list is cached locally for four hours, so status may lag behind eQSL.

Installation

In SourceWeft

  1. Open Eqsl 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

eqsl-mcp

[PyPI] [MCP Registry]

MCP server for eQSL.cc — download incoming eQSLs, verify QSOs, check AG status, and query upload history through any MCP-compatible AI assistant.

Part of the qso-graph project. Uses qso-graph-auth for credential management.

Install

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

Tools

ToolAuthDescription
eqsl_inboxYesDownload incoming eQSLs with date/confirmation filters
eqsl_verifyNoCheck if a specific QSO exists in eQSL
eqsl_ag_checkNoCheck if a callsign has AG (Authenticity Guaranteed) status
eqsl_downloadYesDownload your eQSL inbox as raw ADIF, to import into your logger
eqsl_last_uploadNoWhen did a persona last upload to eQSL
get_version_infoNoService version + upstream eQSL.cc endpoint version (fleet identity attestation)

Quick Start

1. Set up credentials

eqsl-mcp uses qso-graph-auth personas for credential management:

bash
# Install qso-graph-auth if you haven'tuv tool install qso-graph-auth
# A persona (your callsign and the dates it covers), then eQSL for itqso-graph-auth persona add --name ki7mt --callsign KI7MT --start 2020-01-01qso-graph-auth provider enable ki7mt eqslqso-graph-auth creds set ki7mt eqsl      # asks for your username, then your password (hidden)

All three steps are needed: without provider enable, the server reports that the persona has no eqsl ref.

2. Configure your MCP client

eqsl-mcp works with any MCP-compatible client. Add the server config and restart — tools appear automatically.

Claude Desktop

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

json
{  "mcpServers": {    "eqsl": {      "command": "uvx",      "args": ["eqsl-mcp"]    }  }}
Claude Code

Add to .claude/settings.json:

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

ChatGPT supports MCP via the OpenAI Agents SDK. Add under Settings > Apps & Connectors, or configure in your agent definition:

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

Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):

json
{  "mcpServers": {    "eqsl": {      "command": "uvx",      "args": ["eqsl-mcp"]    }  }}
VS Code / GitHub Copilot

Add to .vscode/mcp.json in your workspace:

json
{  "servers": {    "eqsl": {      "command": "uvx",      "args": ["eqsl-mcp"]    }  }}
Gemini CLI

Add to ~/.gemini/settings.json (global) or .gemini/settings.json (project):

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

3. Ask questions

"Show me all eQSLs received this week"

"How many unconfirmed eQSLs do I have on 20m FT8?"

"Does W1AW have AG status on eQSL?"

"Verify my QSO with KI7MT on 20m on March 1, 2026"

Testing Without Credentials

The two public tools (eqsl_verify and eqsl_ag_check) work without any credentials.

For eqsl_inbox testing, set the mock environment variable:

bash
EQSL_MCP_MOCK=1 eqsl-mcp

Or point to a local ADIF file:

bash
EQSL_MCP_MOCK=1 EQSL_MCP_ADIF=/path/to/test.adi eqsl-mcp

MCP Inspector

bash
eqsl-mcp --transport streamable-http --port 8001

Then open the MCP Inspector at http://localhost:8001.

Development

bash
git clone https://github.com/qso-graph/eqsl-mcp.gitcd eqsl-mcpuv sync --group devuv run pytest

Date Formats

eQSL uses different date formats across endpoints. eqsl-mcp normalizes everything — you always use YYYY-MM-DD:

You provideeqsl-mcp sendsEndpoint
2026-03-01202603010000DownloadInBox (RcvdSince)
2026-03-0103/01/2026VerifyQSO (QSODate)

Mode Matching

eQSL requires exact mode matching. SSB won't match USB/LSB. PSK won't match PSK31. Use the exact mode logged by the other station.

Known Quirks

  • AG list cache: the Authenticity Guaranteed member list is cached for 4 hours (eQSL updates it about six times a day), in ~/.cache/eqsl-mcp/ag_members.txt ($XDG_CACHE_HOME if set; %LOCALAPPDATA%\eqsl-mcp\ on Windows).
  • Inbox download: eQSL returns an HTML page that links to the .adi file, so the inbox is fetched in two steps. If eQSL answers with ADIF directly, that is used as is.

License

GPL-3.0-or-later

Source: README.md at commit 8053c03

Tools

6

get_version_info

Get Version Info

Get eqsl-mcp service version and upstream eQSL.cc endpoint version. Returns the running PyPI version of eqsl-mcp and the eQSL.cc endpoint contract in use. Use this to confirm fleet alignment across MCP deployments — agents can compare service_version and spec_version across servers to detect drift without going outside the MCP protocol.

Takes no parameters.

eqsl_inbox

Eqsl Inbox

Download incoming eQSLs (confirmations others have sent you).

Parameterssincepersonarequiredqth_nicknameconfirmed_onlyunconfirmed_only

eqsl_verify

Eqsl Verify

Check if a specific QSO exists in eQSL (public, no auth required).

Parametersbandrequiredmodeto_callrequiredqso_daterequiredfrom_callrequired

eqsl_ag_check

Eqsl Ag Check

Check if a callsign has Authenticity Guaranteed (AG) status on eQSL. Public, no auth required. Uses a cached copy of the AG member list (refreshed every 4 hours).

Parameterscallsignrequired

eqsl_download

Eqsl Download

Download your complete eQSL inbox as raw ADIF text. Returns the .adi file content — save to disk for import into your logger. Omit 'since' to download your entire inbox history.

Parameterssincepersonarequiredqth_nickname

eqsl_last_upload

Eqsl Last Upload

Check when a persona last uploaded QSOs to eQSL.

Parameterspersonarequired

Version history

11
  1. v0.6.2LatestOct 29, 2026
  2. v0.5.0Oct 26, 2026
  3. v0.4.3Oct 26, 2026
  4. v0.4.1Oct 26, 2026
  5. v0.4.0Oct 12, 2026
  6. v0.3.8Oct 11, 2026
  7. v0.3.7Oct 7, 2026
  8. v0.3.6Oct 6, 2026
  9. v0.3.5Oct 4, 2026
  10. v0.3.4Sep 29, 2026
  11. v0.2.0Sep 16, 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