Skip to content

Development Radio MCP server

dev.developmentradio/development-radiodevelopmentradio.devstreamable-httpv1.0.1Scanned

Search podcast episodes on AI, security and software news; get sources and timed transcripts.

4 tools: 4 only read.

Tools: 0 delete, 0 irreversible, 0 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Development Radio MCP server can do

The Development Radio MCP server is published by developmentradio.dev, a domain the MCP Registry verified. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool reads private data (get_episode); 3 tools bring in text other people can write (list_episodes, get_episode and get_transcript).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Only reads 4Show 4 read-only tools
  • get_episodeReturns one episode's show notes: summary, takeaways, the check the episode suggests running, chapters with timestamps, topics, every primary source it cites (title and URL), and l…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_episode" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "note": it reads notes.
    • untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Returns one episode's show notes: summary, takeaways, the check the episode suggests running, chapters with timestamps, topics, every primary source it cites (title and URL), and links to the page, the MP3 and the YouTube video when there is one. Use this when you have an episode id and need its findings and sources without the full transcript. The show's hosts are AI-generated voices.

    Annotations the server declares

    • title: Get one episode's notes and sources
    • readOnlyHint: true
    • openWorldHint: false
  • get_transcriptReturns one episode's full timed transcript as Markdown, with speaker names and HH:MM:SS timestamps, preceded by its title, page URL and the primary sources it cites.Reads text others writeNo findings

    Why it is in this group

    • The name "get_transcript" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Returns one episode's full timed transcript as Markdown, with speaker names and HH:MM:SS timestamps, preceded by its title, page URL and the primary sources it cites. Use this when you need exact wording, or to quote or locate a passage; get_episode is shorter when a summary is enough. The speakers, Maya and Alex, are AI-generated voices.

    Annotations the server declares

    • title: Get one episode's timed transcript
    • readOnlyHint: true
    • openWorldHint: false
  • list_episodesLists Development Radio episodes, newest first, each with its id, title, date, length, lanes, page URL, one-line description and the URLs of the primary sources it cites.Reads text others writeNo findings

    Why it is in this group

    • The name "list_episodes" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Lists Development Radio episodes, newest first, each with its id, title, date, length, lanes, page URL, one-line description and the URLs of the primary sources it cites. Use this when you need the most recent episodes, an overview of what the show has covered, or a valid episode id for get_episode or get_transcript. The show's hosts are AI-generated voices.

    Annotations the server declares

    • title: List Development Radio episodes
    • readOnlyHint: true
    • openWorldHint: false
  • search_episodesKeyword search over Development Radio episodes: titles, topics, chapter titles, takeaways, summaries, cited source titles and the full timed transcripts.No findings

    Why it is in this group

    • The name "search_episodes" says "search": a word for reading.
    Description, as the server wrote it
    Keyword search over Development Radio episodes: titles, topics, chapter titles, takeaways, summaries, cited source titles and the full timed transcripts. Up to six keywords of three or more characters are used; a keyword matches at the start of a word. Episodes are ranked by how many keywords they contain, and when any episode contains more than half of them, episodes containing half or fewer are left out. Each result comes with its id, title, date, page URL, the best-matching passage (with a timestamp when it comes from the transcript) and the URLs of the primary sources the episode cites. Use this when you need a sourced account of a security incident, CVE, outage, AI or software-development news item, or an engineering practice such as lock expiry, replica lag, queue fairness or content security policy. The show's hosts are AI-generated voices.

    Annotations the server declares

    • title: Search Development Radio episodes
    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:19 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http development-radio https://developmentradio.dev/mcp
claude mcp add --transport http development-radio https://developmentradio.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__development-radio__search_episodes",
      "mcp__development-radio__list_episodes",
      "mcp__development-radio__get_episode",
      "mcp__development-radio__get_transcript"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as development-radio. Review it before you use it.

Capability tags behind 3 rules
  • mcp__development-radio__list_episodes untrusted-input
  • mcp__development-radio__get_episode private-data, untrusted-input
  • mcp__development-radio__get_transcript untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.developmentradio/development-radio/verify?hash=a35bf3351c8831e6ebaa5eceb5241c1a32ff048ac353ee23b6ac45703deb2427" | jq -e '.changed == false'

Pinned hash a35bf3351c88, from Nov 20, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.developmentradio/development-radio/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.developmentradio/development-radio
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.developmentradio/development-radio.svg)](https://radar.anlyon.com/servers/dev.developmentradio/development-radio)

Source: MCP Registry · repository. Synced Nov 20, 2026, 17:17 UTC.

Development Radio MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Development Radio MCP server safe?

No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Development Radio MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Development Radio MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Development Radio MCP server have?

4 tools: 4 read. search_episodes, list_episodes, get_episode and get_transcript.

Does the Development Radio MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Development Radio MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Development Radio MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.