darc-dok-mcp
<!-- mcp-name: io.github.qso-graph/darc-dok-mcp -->
# darc-dok-mcp
[](https://pypi.org/project/darc-dok-mcp/)
[](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.qso-graph/darc-dok-mcp&version=latest)
> **Source: the Deutscher Amateur-Radio-Club e.V. (DARC):** the [DOK-Liste](https://www.darc.de/fileadmin/filemounts/referate/dx/DOK-Liste.pdf) (DARC DX-Referat, by Karsten Radwan, DL2ABM, 26.12.2016) and the [special-DOK list](https://www.darc.de/fileadmin/filemounts/referate/sdok/SDOK_List.csv) (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](https://www.darc.de/fileadmin/filemounts/referate/dx/DOK-Liste.pdf) (2016-12-26) and the event codes of DARC's [special-DOK list](https://www.darc.de/fileadmin/filemounts/referate/sdok/SDOK_List.csv), 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](https://qso-graph.io/) 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
| Tool | Description | Key Parameters |
|------|-------------|----------------|
| `darc_dok_lookup` | One DOK or special DOK: district and club, or purpose, callsign, window and sponsoring club | code |
| `darc_dok_valid_on` | Whether a DOK or special DOK was valid on a QSO's date | code, on_date |
| `darc_dok_search` | Find DOKs by club, town, district or purpose | text, limit |
| `darc_dok_codes_for` | Kept for the shared tool set; DOKs map to no ADIF subdivision | dxcc, subdivision |
| `darc_dok_source_info` | Owner, editions, terms, and the owner's files' URLs and SHA-256s | — |
| `get_version_info` | Service 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.git
cd darc-dok-mcp
uv sync --group dev
uv 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](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](docs/TRANSCRIPTION.md). See [NOTICE](NOTICE).
TDQS
Scored across 6 tools
Several pairs have unclear boundaries: get_version_info and darc_dok_source_info both report the served edition, and darc_dok_lookup overlaps with both darc_dok_valid_on (validity window) and darc_dok_codes_for, since lookup already returns validity windows for special DOKs. The descriptions are rich enough to mostly sort it out, but an agent must read carefully to choose between lookup, search, and codes_for.
Five tools follow a clean darc_dok_<verb/preposition> snake_case pattern (lookup, search, valid_on, codes_for, source_info). get_version_info breaks the prefix convention, a minor but noticeable deviation.
Six tools is well-scoped for a read-only reference lookup server. The only redundancy is the version/source-info pair, which could arguably be one tool.
The surface covers point lookup, free-text search, date-validity, entity-level code listing, provenance/citation, and version info, which is solid for a static reference dataset. A reverse listing of all DOKs within a district is only indirectly available via search, a minor gap.