Radiomcp MCP Server

radiomcp PyPI v1.3.1

Published by zeus-kim — 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.

Trust grade
B
89/100
Last scanned
Trust
B · 89/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Critical
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
B Why this grade threat 100 − adoption risk = 89/100

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 − 11 = 89. 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:

PointsAdoption-risk factor
−10 capability blast radius (critical) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable
inspection depth (source) — how much of the target the scan could see

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 3

high Shell/command execution in server code (radiomcp/dj_broadcast.py)MTC-SRC-002

In the server's implementation (`radiomcp/dj_broadcast.py:636`): 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: subprocess.run(

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 radiomcp/dj_broadcast.py

high Shell/command execution in server code (radiomcp/server.py)MTC-SRC-002

In the server's implementation (`radiomcp/server.py:187`): 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: subprocess.Popen(

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 radiomcp/server.py

high Shell/command execution in server code (radiomcp/tui.py)MTC-SRC-002

In the server's implementation (`radiomcp/tui.py:228`): 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: subprocess.run(

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 radiomcp/tui.py

Tools 78

Each tool and what it can reach — statically extracted from the published source.

  • dj_fetch_contentingests untrusted input
  • dj_fresh_newsingests untrusted input
  • dj_rss_listingests untrusted input
  • dj_rss_subscribeingests untrusted input
  • dj_rss_telegramingests untrusted input
  • dj_rss_unsubscribeingests untrusted input
  • dj_top_headlinesingests untrusted input
  • sync_with_apiingests untrusted input
  • add_favoriteno sensitive capability
  • add_to_blocklistno sensitive capability
  • advanced_searchno sensitive capability
  • check_stationno sensitive capability
  • check_streamno sensitive capability
  • check_stream_detailedno sensitive capability
  • dj_get_content_for_commentsno sensitive capability
  • dj_get_scheduleno sensitive capability
  • dj_healthno sensitive capability
  • dj_logsno sensitive capability
  • dj_news_briefno sensitive capability
  • dj_news_langno sensitive capability
  • dj_one_hourno sensitive capability
  • dj_play_setno sensitive capability
  • dj_play_videono sensitive capability
  • dj_play_with_infono sensitive capability
  • dj_providersno sensitive capability
  • dj_reddit_talkno sensitive capability
  • dj_scheduler_statusno sensitive capability
  • dj_set_scheduleno sensitive capability
  • dj_song_infono sensitive capability
  • dj_start_schedulerno sensitive capability
  • dj_statsno sensitive capability
  • dj_stopno sensitive capability
  • dj_stop_schedulerno sensitive capability
  • dj_stop_videono sensitive capability
  • expand_searchno sensitive capability
  • get_blocklistno sensitive capability
  • get_categoriesno sensitive capability
  • get_db_statsno sensitive capability
  • get_favoritesno sensitive capability
  • get_historyno sensitive capability
  • get_listening_statsno sensitive capability
  • get_player_backendno sensitive capability
  • get_popularno sensitive capability
  • get_radio_guideno sensitive capability
  • get_radio_statusno sensitive capability
  • get_recognized_songsno sensitive capability
  • get_user_profileno sensitive capability
  • get_volumeno sensitive capability
  • global_radio_chartno sensitive capability
  • health_checkno sensitive capability
  • now_playingno sensitive capability
  • personalized_recommendno sensitive capability
  • playno sensitive capability
  • play_favoriteno sensitive capability
  • purge_deadno sensitive capability
  • radio_chartno sensitive capability
  • recognize_songno sensitive capability
  • recommendno sensitive capability
  • recommend_by_timeno sensitive capability
  • recommend_by_weatherno sensitive capability
  • refresh_blocklistno sensitive capability
  • remove_favoriteno sensitive capability
  • remove_from_blocklistno sensitive capability
  • resumeno sensitive capability
  • rising_songsno sensitive capability
  • searchno sensitive capability
  • search_artistno sensitive capability
  • search_by_countryno sensitive capability
  • search_by_languageno sensitive capability
  • set_alarmno sensitive capability
  • set_player_backendno sensitive capability
  • set_sleep_timerno sensitive capability
  • set_volumeno sensitive capability
  • share_stationno sensitive capability
  • similar_artistsno sensitive capability
  • similar_stationsno sensitive capability
  • spotify_chartno sensitive capability
  • stopno sensitive capability

What this scan could not see

Versions

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.

VersionScoreFindingsEngineScanned
v1.3.1 latest B 89/100 3 1.8.0 2026-07-23

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.

MCP Trust Score: B · 89/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/radiomcp/badge.svg)](https://mcptrustchecker.com/registry/radiomcp)
HTML
<a href="https://mcptrustchecker.com/registry/radiomcp"><img src="https://mcptrustchecker.com/registry/radiomcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/radiomcp/badge.json via https://img.shields.io/endpoint?url=…

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 radiomcp --online --registry pypi

Use the free API → How scoring works

More in Design & Media