Skip to main content

js8call-mcp

PyPI

In development

This package is published so the name is held while the work is planned in the open. It registers one tool, get_version_info, and does nothing else yet. If you install it expecting a working server, that is what you will find — which is why it says so here, in the server's own instructions, and in the one tool it has.

PyPI does not reserve a name for a pending trusted publisher, so a name is only held once something is actually published. Given that, a package that says what it is beats an empty one that does not.

Read-only access to JS8Call's API: the decode stream, stations heard, message traffic and the propagation those imply. No write, no PTT, no transmit control — a permanent constraint, not a first-version limit.

Planned work, including the data sources it would use and whether each is actually available, is tracked in qso-graph-devel#48.

Part of the qso-graph project.

Install

uvx js8call-mcp            # run it; nothing to install

Tools

Tool Description
get_version_info Service version, development status, and where the work is tracked

Quick Start

No credentials needed — install and configure your MCP client.

Configure your MCP client

js8call-mcp works with any MCP-compatible client. Add the server config and restart.

Claude Desktop

Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows):

{
  "mcpServers": {
    "js8call": {
      "command": "uvx",
      "args": ["js8call-mcp"]
    }
  }
}

Claude Code

Add to .claude/settings.json:

{
  "mcpServers": {
    "js8call": {
      "command": "uvx",
      "args": ["js8call-mcp"]
    }
  }
}

ChatGPT Desktop

Configure via Settings > Apps & Connectors, or in your agent definition:

{
  "mcpServers": {
    "js8call": {
      "command": "uvx",
      "args": ["js8call-mcp"]
    }
  }
}

Questions it will answer

Not yet — these are what the finished server is for:

"Who has JS8Call heard on 40m in the last hour?"

"What message traffic has come through for my callsign?"

"Which stations are relaying, and how far away are they?"

Licence

GPL-3.0-or-later. See LICENSE.

Metadata

Release files for js8call-mcp 0.0.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for js8call-mcp 0.0.3
File Size Uploaded Provenance
js8call_mcp-0.0.3.tar.gz 181.3 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for js8call-mcp 0.0.3
File Interpreter ABI Platform
js8call_mcp-0.0.3-py3-none-any.whl Python 3 none any Details

Total release size: 198.5 kB

Release files / js8call_mcp-0.0.3.tar.gz

Download URL js8call_mcp-0.0.3.tar.gz
Size 181.3 kB
Tags Source
SHA-256 checksum
How to use checksums
959957b17a678c4794a6b5264bd05aaffb737e00bc15a66c8109d1a5aaee0d0a
BLAKE2b-256 checksum
How to use checksums
451fd7cf24a851d8fc5ff46ce71a2537370eb6fc2dfd24310c6710c06085d3f6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / js8call_mcp-0.0.3-py3-none-any.whl

Download URL js8call_mcp-0.0.3-py3-none-any.whl
Size 17.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0eac064776191ce110ea4fb7e5ab9bab8caabae85269ac4275e7bde09cae0f38
BLAKE2b-256 checksum
How to use checksums
7b4f8d04f1f0e697f74f110703084c422db15334ff4b5d5dd441edbb3be77246
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Security for js8call-mcp 0.0.3

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for js8call_mcp-0.0.3.tar.gz

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

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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