Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
DARC DOKs and special DOKs as DARC publishes them, with validity windows
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"darc-dok": {
"command": "uvx",
"args": [
"darc-dok-mcp"
]
}
}
}Run this in your terminal
claude mcp add darc-dok -- uvx darc-dok-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"darc-dok": {
"command": "uvx",
"args": [
"darc-dok-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"darc-dok": {
"type": "stdio",
"command": "uvx",
"args": [
"darc-dok-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account qso-graph, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.3.0) reached the registry 12 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Date Math
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Exact date/time math for agents: business days, holidays, time zones, cron, RRULE, SLA. x402 paid.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
uvx darc-dok-mcp # run it; nothing to install
| 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) | — |
No credentials needed — just install and configure your MCP client.
darc-dok-mcp works with any MCP-compatible client. Add the server config and restart — tools appear automatically.
Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows):
{
"mcpServers": { "darc-dok": { "command": "uvx", "args": ["darc-dok-mcp"] } } }
Add to .claude/settings.json:
{
"mcpServers": { "darc-dok": { "command": "uvx", "args": ["darc-dok-mcp"] } } }
{
"mcpServers": { "darc-dok": { "command": "uvx", "args": ["darc-dok-mcp"] } } }
Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):
{
"mcpServers": { "darc-dok": { "command": "uvx", "args": ["darc-dok-mcp"] } } }
Add to .vscode/mcp.json in your workspace:
{
"servers": { "darc-dok": { "command": "uvx", "args": ["darc-dok-mcp"] } } }
Add to ~/.gemini/settings.json (global) or .gemini/settings.json (project):
{
"mcpServers": { "darc-dok": { "command": "uvx", "args": ["darc-dok-mcp"] } } }
"Which club is DOK A01?"
"Was special DOK 01ALT valid on 2004-06-01?"
"Which DOKs are in district Baden?"
darc-dok-mcp --transport streamable-http --port 8018
Then open the MCP Inspector at http://localhost:8018.
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).
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.