Skip to main content

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

uvx eqsl-mcp            # run it; nothing to install

Tools

Tool Auth Description
eqsl_inbox Yes Download incoming eQSLs with date/confirmation filters
eqsl_verify No Check if a specific QSO exists in eQSL
eqsl_ag_check No Check if a callsign has AG (Authenticity Guaranteed) status
eqsl_download Yes Download your eQSL inbox as raw ADIF, to import into your logger
eqsl_last_upload No When did a persona last upload to eQSL
get_version_info No Service 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:

# Install qso-graph-auth if you haven't
uv tool install qso-graph-auth

# A persona (your callsign and the dates it covers), then eQSL for it
qso-auth persona add --name ki7mt --callsign KI7MT --start 2020-01-01
qso-auth provider enable ki7mt eqsl
qso-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):

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

Claude Code

Add to .claude/settings.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:

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

Cursor

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

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

VS Code / GitHub Copilot

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

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

Gemini CLI

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

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

EQSL_MCP_MOCK=1 eqsl-mcp

Or point to a local ADIF file:

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

MCP Inspector

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

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

Development

git clone https://github.com/qso-graph/eqsl-mcp.git
cd eqsl-mcp
uv sync --group dev
uv run pytest

Date Formats

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

You provide eqsl-mcp sends Endpoint
2026-03-01 202603010000 DownloadInBox (RcvdSince)
2026-03-01 03/01/2026 VerifyQSO (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

Metadata

Release files for eqsl-mcp 0.4.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for eqsl-mcp 0.4.3
File Size Uploaded Provenance Actions
eqsl_mcp-0.4.3.tar.gz 198.0 kB With provenance Details for eqsl_mcp-0.4.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for eqsl-mcp 0.4.3
File Interpreter ABI Platform Actions
eqsl_mcp-0.4.3-py3-none-any.whl Python 3 none any Details for eqsl_mcp-0.4.3-py3-none-any.whl

Total release size: 224.6 kB

Release files / eqsl_mcp-0.4.3.tar.gz

Download URL eqsl_mcp-0.4.3.tar.gz
Size 198.0 kB
Tags Source
SHA-256 checksum
How to use checksums
6d945dd381e6f9f281b3c1e11335da64ae3d7ba54896dac8d1c980130c4482f4
BLAKE2b-256 checksum
How to use checksums
52d9f140c7a877220cab53702ad8bbdaa573ae4cd926f67f68ee57fde4cc76c5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.

Transparency log

Release files / eqsl_mcp-0.4.3-py3-none-any.whl

Download URL eqsl_mcp-0.4.3-py3-none-any.whl
Size 26.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
dbda8ac88234ed6fb1617e800c16ab80f19653e8a44f486a9851c2560ec39c8d
BLAKE2b-256 checksum
How to use checksums
f48dd9e223fbe0d0b23e7359dfe99462eeac0ac4fd63b9b874f840c163e22c1a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.

Transparency log

Security for eqsl-mcp 0.4.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for eqsl_mcp-0.4.3.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page