Darc Dok Mcp

io.github.qso-graphv0.1.0Updated Oct 7, 2026

DARC DOKs and special DOKs as DARC publishes them, with validity windows

VerifiedSTDIODesktop onlyLocation & LifestyleKnowledge & Memory

Overview

AI-generated overview

Lets an assistant look up DARC DOK and special-DOK codes, their districts, clubs, and validity windows, with each answer citing its source.

What it does
Serves DARC's published DOK-Liste and special-DOK list as local facts. Tools include darc_dok_lookup for one code's district, club, purpose, callsign, window and sponsoring club; darc_dok_valid_on to check whether a code was valid on a QSO date; darc_dok_search to find codes by club, town, district or purpose; darc_dok_source_info for owner, editions, terms and file checksums; and get_version_info for service and edition identity. darc_dok_codes_for is kept for the shared tool set but maps DOKs to no ADIF subdivision.
When to use it
Useful for amateur-radio work involving DARC DOKs, such as the DLD award, DOK best-lists, the WAG contest, or ADIF DARC_DOK fields, when you want code lookups and validity checks without leaving the assistant.
Requirements
Runs locally as a stdio process, typically started with uvx darc-dok-mcp, so a Python/uv runtime is needed. No network access, authentication, environment variables or headers are required; the data ships with the package.
Before you install
Read-only lookups; no credentials, payments or writes are involved. The data is DARC's, not the package's, and the package's GPL-3.0 licence does not cover it; answers cite the source and link to DARC's files rather than copying them.

Installation

In SourceWeft

  1. Open Darc Dok 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

darc-dok-mcp

[PyPI] [MCP Registry]

Source: the Deutscher Amateur-Radio-Club e.V. (DARC): the DOK-Liste (DARC DX-Referat, by Karsten Radwan, DL2ABM, 26.12.2016) and the special-DOK list (DARC SDOK-Referat). DOKs are DARC's: this package serves the lists' rows as facts, each citing its page or row, and links to DARC's files rather than copying them. Our GPL-3.0 licence covers our code, not DARC's data.

MCP server for DARC DOKs and special DOKs as DARC publishes them: the local-club codes of DARC's DOK-Liste (2016-12-26) and the event codes of DARC's special-DOK list, with each special DOK's validity window. DOKs are used for DARC's DLD award, the DOK best-lists and the WAG contest, and in ADIF's DARC_DOK field.

Part of the qso-graph project. No network, no authentication: the facts from the owner's list ship with the package, and every answer names its source.

Install

bash
uvx darc-dok-mcp            # run it; nothing to install

Tools

ToolDescriptionKey Parameters
darc_dok_lookupOne DOK or special DOK: district and club, or purpose, callsign, window and sponsoring clubcode
darc_dok_valid_onWhether a DOK or special DOK was valid on a QSO's datecode, on_date
darc_dok_searchFind DOKs by club, town, district or purposetext, limit
darc_dok_codes_forKept for the shared tool set; DOKs map to no ADIF subdivisiondxcc, subdivision
darc_dok_source_infoOwner, editions, terms, and the owner's files' URLs and SHA-256s—
get_version_infoService version + the owner's edition served (fleet identity attestation)—

Quick Start

No credentials needed — just install and configure your MCP client.

Configure your MCP client

darc-dok-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": {    "darc-dok": {      "command": "uvx",      "args": ["darc-dok-mcp"]    }  }}
Claude Code

Add to .claude/settings.json:

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

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

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

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

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

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

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

Ask questions

"Which club is DOK A01?"

"Was special DOK 01ALT valid on 2004-06-01?"

"Which DOKs are in district Baden?"

MCP Inspector

bash
darc-dok-mcp --transport streamable-http --port 8018

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

Development

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

scripts/fetch_published.py fetches the owner's document(s) into published/ (not committed) and checks their SHA-256s; uv run pytest --live runs the tests that need them. scripts/build.py regenerates derived/ and load.sql, a PostgreSQL load for QSO Graph's reference data (load QG ADIF's adif schema first).

License

darc-dok-mcp's own code is GPL-3.0-or-later. See LICENSE. The data it serves is the owner's, credited at the top of this page: our licence doesn't cover it, and we claim no rights in it. The owner's document itself is not included; data/SOURCE.json records its URL and SHA-256 so anyone can check the facts against it. Files we built from the facts (data/derived/) are ours and labelled as ours. How the owner's text was read is recorded in docs/TRANSCRIPTION.md. See NOTICE.

Source: README.md at commit 65feaf8

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.0LatestOct 7, 2026