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.3.7

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.3.7
File Size Uploaded
eqsl_mcp-0.3.7.tar.gz 145.4 kB Details

Built distribution (wheel)

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

Total release size: 169.2 kB

Release files / eqsl_mcp-0.3.7.tar.gz

Download URL eqsl_mcp-0.3.7.tar.gz
Size 145.4 kB
Tags Source
SHA-256 checksum
How to use checksums
369b54905264cca88bc2b8999a8b970c01ecae5b048e9b849f6be25707c39f92
BLAKE2b-256 checksum
How to use checksums
f32f6e52dbd088c9fcb8a6df7b2b1530da168b92339121147c9c8cd10c25a1c6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 7, 2026.

Transparency log

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

Download URL eqsl_mcp-0.3.7-py3-none-any.whl
Size 23.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8b4e3c4383ca67f98f9ec27dcd3d1f28876981887c7f0a5aab4936a5c77b4925
BLAKE2b-256 checksum
How to use checksums
cb27ed06229918a5533671ee89ccb897e7383a3f9358c639cc533df54af8e88e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 7, 2026.

Transparency log

Release history Release notifications | RSS feed

0.4.0

2 release files

0.3.8

2 release files

This release

0.3.7 This release

2 release files

0.3.6

2 release files

0.3.5

2 release files

0.3.4

2 release files

0.3.3

2 release files

0.3.2

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

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