io.github.qso-graph/wspr-mcp

Name: io.github.qso-graph/wspr-mcp
Rating: 60 (1 reviews)
Author: io.github.qso-graph

MCPcommunity

v0.1.1io.github.qso-graphUnknownUpdated 3mo agoGitHub

WSPR beacon analytics MCP server. Band openings, path analysis, solar correlation.

MCP server for WSPR (Weak Signal Propagation Reporter) beacon data — live spots, band activity, top beacons, propagation paths, SNR trends, and more through any MCP-compatible AI assistant. Data from wspr.live (~2.7 billion spots, 2008-present). Part of the qso-graph project. No authentication required — all public data. Tool | Description | Key Parameters | ------|-------------|----------------|…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

3mo agoLast update

Package

Authorio.github.qso-graph

LicenseUnknown

Version0.1.1

Sourcemcp-registry

GitHubqso-graph/wspr-mcp

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

DependenciesNot audited

Tool surface—

Security scan✓ Cleanv0.3.2 · 19d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp