_ registry / mcp streamable-http · checked 16h ago

development-radio

https://developmentradio.dev

Registry code: aa97e6b55ba23c53

api record

Read-only index of Development Radio, a podcast for senior engineers on AI, security and software development news and engineering practices: episode summaries, takeaways, chapters, timed transcripts and the primary sources each episode cites. The hosts, Maya and Alex, are AI-generated voices.

endpoint
https://developmentradio.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is development-radio live?
Yes — it answered the hub's last check (checked 16h ago). It answered 100% of checks over the last 30 days.
Is development-radio free to use?
Yes — the hub reached it with no key and no payment.
What tools does development-radio have?
4 tools: search_episodes, get_episode, get_transcript, list_episodes.
Is development-radio safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
182ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_episodes open 16h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "lane": {
          "enum": [
            "ai",
            "security",
            "software",
            "practices"
          ],
          "type": "string",
          "description": "Only episodes in this lane of the show."
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum number of episodes to return."
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • search_episodes unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "lane": {
          "enum": [
            "ai",
            "security",
            "software",
            "practices"
          ],
          "type": "string",
          "description": "Only episodes in this lane of the show."
        },
        "limit": {
          "type": "integer",
          "default": 5,
          "maximum": 20,
          "minimum": 1,
          "description": "Maximum number of episodes to return."
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 3,
          "description": "Keywords, for example \"nginx http2 rce\" or \"redis lock expiry\"."
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • get_episode unknown 16h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Episode id as returned by search_episodes or list_episodes, for example 2026-11-20-nginx-five-teams-daily."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_transcript unknown 16h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Episode id as returned by search_episodes or list_episodes, for example 2026-11-20-nginx-five-teams-daily."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id aa97e6b55ba23c53.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/aa97e6b55ba23c53/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/aa97e6b55ba23c53/badge.svg)](https://brick.blue/agent/aa97e6b55ba23c53?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.