QRZ.com MCP server. Callsign lookup, DXCC resolution, logbook queries via QRZ XML API.
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"qrz": {
"command": "qrz-mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for QRZ.com — callsign lookups, DXCC entity resolution, and logbook queries through any MCP-compatible AI assistant.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'qrz-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked qrz-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
MCP server for letmepost.dev. Publish across 8 social platforms from any agent.
MCP Security Weekly
Get CVE alerts and security updates for io.github.qso-graph/qrz-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP server for QRZ.com — callsign lookups, DXCC entity resolution, and logbook queries through any MCP-compatible AI assistant.
Part of the qso-graph project. Uses qso-graph-auth for credential management.
pip install qrz-mcp
| Tool | API | Auth | Description |
|---|---|---|---|
qrz_lookup | XML | Session key | Callsign lookup (name, grid, DXCC, license class, QSL info, image) |
qrz_dxcc | XML | Session key | DXCC entity resolution from callsign or entity code |
qrz_logbook_status | Logbook | API key | Logbook stats (QSO count, DXCC total, date range) |
qrz_logbook_fetch | Logbook | API key | Query QSOs with filters and transparent pagination |
qrz_download | Logbook | API key | Download full logbook as ADIF |
get_version_info | — | None | Service version + upstream QRZ API version (fleet identity attestation) |
qrz-mcp uses qso-graph-auth personas for credential management. QRZ has two separate auth mechanisms — set up whichever you need:
# Install qso-graph-auth if you haven't
pip install qso-graph-auth
# Create a persona
qso-auth persona create ki7mt --callsign KI7MT
# Enable QRZ provider
qso-auth persona provider ki7mt qrz --username KI7MT
# Set password (for XML API: qrz_lookup, qrz_dxcc)
qso-auth persona secret ki7mt qrz
# Set API key (for Logbook API: qrz_logbook_status, qrz_logbook_fetch)
qso-auth creds set --persona ki7mt --provider qrz --api-key YOUR_API_KEY
XML API (callsign lookup, DXCC) requires a QRZ XML Subscription ($35.95/yr). Free tier returns name and address only.
Logbook API requires an API key from QRZ Settings > API.
qrz-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": {
"qrz": {
"command": "qrz-mcp"
}
}
}
Add to .claude/settings.json:
{
"mcpServers": {
"qrz": {
"command": "qrz-mcp"
}
}
}
ChatGPT supports MCP via the OpenAI Agents SDK. Add under Settings > Apps & Connectors, or configure in your agent definition:
{
"mcpServers": {
"qrz": {
"command": "qrz-mcp"
}
}
}
Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"qrz": {
"command": "qrz-mcp"
}
}
}
Add to .vscode/mcp.json in your workspace:
{
"servers": {
"qrz": {
"command": "qrz-mcp"
}
}
}
Add to ~/.gemini/settings.json (global) or .gemini/settings.json (project):
{
"mcpServers": {
"qrz": {
"command": "qrz-mcp"
}
}
}
"Look up W1AW on QRZ — what's their grid and license class?"
"What DXCC entity is VP8PJ?"
"How many QSOs do I have in my QRZ logbook?"
"Show me all 20m FT8 QSOs from my QRZ logbook this year"
QRZ enforces undocumented rate limits that can trigger 24-hour IP bans. qrz-mcp protects you:
Set the mock environment variable to test all 4 tools without QRZ credentials:
QRZ_MCP_MOCK=1 qrz-mcp
qrz-mcp --transport streamable-http --port 8002
Then open