# Bizzy Radio (remote · bizzy.fm)

Find Bizzy radio stations, read station cards and public author information. Read-only; no playback.

- Trust score: 85/100 (high trust)
- Change this week: +53
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `bizzy.fm`: 85/100 (this document), [markdown](https://verifymcp.io/servers/fm-bizzy-radio/bizzy.md), [page](https://verifymcp.io/servers/fm-bizzy-radio/bizzy)

## Channel facts

- Endpoint: `https://bizzy.fm/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 252 tokens (~84/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Bizzy Radio MCP server?

Bizzy Radio is a hosted endpoint at https://bizzy.fm/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http fm-bizzy-radio 'https://bizzy.fm/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "fm-bizzy-radio": {
      "url": "https://bizzy.fm/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fm-bizzy-radio": {
      "type": "http",
      "url": "https://bizzy.fm/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fm-bizzy-radio]
url = "https://bizzy.fm/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fm-bizzy-radio": {
      "type": "remote",
      "url": "https://bizzy.fm/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fm-bizzy-radio --url 'https://bizzy.fm/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fm-bizzy-radio:
    url: "https://bizzy.fm/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fm-bizzy-radio": {
      "Transport": "http",
      "Url": "https://bizzy.fm/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fm-bizzy-radio -t streamable-http -u 'https://bizzy.fm/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fm-bizzy-radio": {
      "type": "http",
      "url": "https://bizzy.fm/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 82, +50)

- [security improvement] Authorization: unverified → partial
- [security improvement] HTTPS: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.60

### 2026-09-14 (score 32, −15)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-13 (score 47, −16)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-12 (score 63, −16)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-10 (score 79, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] HTTPS: pass → unverified
- [security regression] Stability: 0.40 → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

## MCP tools (3)

### `find_stations` (~103 tokens)

Find stations in Bizzy's full backend catalog by name or location, including unavailable stations. Empty query lists all. ID-sorted, bounded pagination; follow next_offset until null.

Input parameters:

- `limit` (integer): Maximum number of results, from 1 to 50.
- `offset` (integer): Number of matching stations to skip; results are sorted by ID.
- `query` (string): Case-insensitive substring of station name or location. Empty lists all stations.

Output parameters:

- `limit` (integer)
- `next_offset`: Next page offset, or null at the end. Catalog changes can move results between pages.
- `offset` (integer)
- `stations` (array)
- `total` (integer): Number of matches in the full backend catalog, including unavailable stations.

### `get_station` (~53 tokens)

Get a Bizzy station by a real catalog UUID. Returns the listening page, not an audio stream. Does not start playback.

Input parameters:

- `id` (string, required): Station UUID from the Bizzy catalog. Never invent an ID.

Output parameters:

- `availability` (string): Backend health flag, not a live playback guarantee.
- `id` (string): Station UUID from the Bizzy catalog. Never invent an ID.
- `listen_url` (string): Canonical Bizzy listening page to share with a person; not a raw audio stream.
- `location` (string): Backend location, or an empty string if unspecified.
- `name` (string): Station name as supplied by the backend.

### `get_bizzy_info` (~29 tokens)

Read the Bizzy authors and Misha Naer's public contact channels. No authentication required.

Output parameters:

- `authors` (array)
- `contact` (object)
- `name` (string)
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fm-bizzy-radio/bizzy#diagnostics

## Score history

- 2026-09-21: 85
- 2026-09-20: 85
- 2026-09-19: 84
- 2026-09-18: 84
- 2026-09-17: 83
- 2026-09-16: 83
- 2026-09-15: 82
- 2026-09-14: 32
- 2026-09-13: 47
- 2026-09-12: 63
- 2026-09-11: 79
- 2026-09-10: 79
- 2026-09-09: 79
- 2026-09-08: 79
- 2026-09-07: 78
- 2026-09-06: 78
- 2026-09-05: 78
- 2026-09-04: 77
- 2026-09-03: 77
- 2026-09-02: 76
- 2026-09-01: 76
- 2026-08-31: 75
- 2026-08-30: 75
- 2026-08-29: 74
- 2026-08-28: 74

## Common questions

### What is the Bizzy Radio MCP server?

Bizzy Radio is an MCP server listed in the public MCP registry as fm.bizzy/radio. Find Bizzy radio stations, read station cards and public author information. Read-only; no playback. This page covers its hosted endpoint (https://bizzy.fm/mcp).

### Is the Bizzy Radio MCP server safe to use?

Bizzy Radio scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Bizzy Radio MCP server expose?

Bizzy Radio exposes 3 tools: find_stations, get_station, get_bizzy_info. Their descriptions and schemas cost roughly 185 tokens of context every time the server is loaded.

### Does the Bizzy Radio MCP server require authentication?

No. We connected to Bizzy Radio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Bizzy Radio MCP server still maintained?

Bizzy Radio is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://bizzy.fm/mcp
- Website: https://bizzy.fm/
- Changelog RSS feed: https://verifymcp.io/servers/fm-bizzy-radio/bizzy.xml
- Changelog JSON feed: https://verifymcp.io/servers/fm-bizzy-radio/bizzy.json
- HTML version of this page: https://verifymcp.io/servers/fm-bizzy-radio/bizzy