Aetherlink MCP Server
aetherlink
PyPI
v0.1.3
Published by n-erickson — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for Software Defined Radio — control RTL-SDR & HackRF from Claude
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
low Shell/command execution in packaging/dev tooling (examples/test_client.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`examples/test_client.py:22`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: erver process = subprocess.Popen( [sys.executable, "-m", "sdr_mcp.server"], stdout=subpr
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server examples/test_client.py
Tools 26
Each tool and what it can reach — statically extracted from the published source.
audio_record_startno sensitive capabilityaudio_record_stopno sensitive capabilityaviation_get_aircraftno sensitive capabilityaviation_stop_trackingno sensitive capabilityaviation_track_aircraftno sensitive capabilityhackrf_set_tx_gainno sensitive capabilityism_get_devicesno sensitive capabilityism_start_scanningno sensitive capabilityism_stop_scanningno sensitive capabilitymarine_get_vesselsno sensitive capability
Show 16 more tools ↓
marine_stop_trackingno sensitive capabilitymarine_track_vesselsno sensitive capabilitypager_get_messagesno sensitive capabilitypager_start_decodingno sensitive capabilitypager_stop_decodingno sensitive capabilityrecording_startno sensitive capabilityrecording_stopno sensitive capabilitysatellite_decode_meteorno sensitive capabilitysdr_connectno sensitive capabilitysdr_disconnectno sensitive capabilitysdr_get_statusno sensitive capabilitysdr_set_frequencyno sensitive capabilitysdr_set_gainno sensitive capabilitysignal_generatorno sensitive capabilityspectrum_analyzeno sensitive capabilityspectrum_scanno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (26 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.3 latest |
A 99/100 | 1 | 1.12.1 | 2026-07-27 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan aetherlink --online --registry pypiMore in Analytics & Monitoring
Public-safe MCP admin discovery contract descriptors and response builders.
Pokemon Champions battle advisor MCP server
Airflow MCP server — DAG list, runs, task instances, log tails, trigger and clear over the Airflow REST API
MCP analytics wrapper SDK that instruments MCP tool declarations with telemetry.
AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
AI-native social listening. Monitor buying signals and run GTM workflows via natural language.