# p0dcasters (remote · p0dcasters.com)

Podcast directory (p0dcasters.com)

- Trust score: 78/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `p0dcasters.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-profullstack-p0dcasters/api-mcp.md), [page](https://verifymcp.io/servers/com-profullstack-p0dcasters/api-mcp)

## Channel facts

- Endpoint: `https://p0dcasters.com/api/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-11-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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1617 tokens (~107/item across 15 items; 14 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 59% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 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 p0dcasters MCP server?

p0dcasters is a hosted endpoint at https://p0dcasters.com/api/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 com-profullstack-p0dcasters 'https://p0dcasters.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-profullstack-p0dcasters": {
      "url": "https://p0dcasters.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-profullstack-p0dcasters": {
      "type": "http",
      "url": "https://p0dcasters.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-profullstack-p0dcasters]
url = "https://p0dcasters.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-profullstack-p0dcasters": {
      "type": "remote",
      "url": "https://p0dcasters.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-profullstack-p0dcasters --url 'https://p0dcasters.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-profullstack-p0dcasters:
    url: "https://p0dcasters.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-profullstack-p0dcasters": {
      "Transport": "http",
      "Url": "https://p0dcasters.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-profullstack-p0dcasters -t streamable-http -u 'https://p0dcasters.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-profullstack-p0dcasters": {
      "type": "http",
      "url": "https://p0dcasters.com/api/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-11-21 (score 78, +1)

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

### 2026-11-19 (score 77, +1)

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

### 2026-11-18 (score 76, +17)

- [security improvement] Authorization: unverified → partial
- [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] Stability: unverified → 0.20
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass

### 2026-11-17 (score 59, −15)

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

### 2026-11-15 (score 74, 0)

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

### 2026-11-13 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 73, +69)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 59
- [functional] First check of Schema quality: good

### 2026-11-11 (score 4)

First indexed and scored.

## MCP tools (14)

### `search` (~91 tokens)

Search the directory

Full-text search over the titles, descriptions, authors and domains of every podcast listed, on any host (own domain, hosting platform or network library). Returns shows, each with its slug, feed URL, page and playlist. Only shows with an episode inside the last 90 days are listed.

Input parameters:

- `limit` (integer): Shows to return. Default 30.
- `query` (string, required): What to search for.

### `get_podcast` (~84 tokens)

Read one show

One show by slug: title, publisher, full description, episode count, cadence, language, categories, feed URL, site and page. Slugs come from search, list_shows and the page URL /podcast/<slug>. Episodes are a separate call, list_episodes, because they are read live from the publisher's feed.

Input parameters:

- `slug` (string, required)

### `list_episodes` (~95 tokens)

Episodes of a show

The episodes of one show, newest first, read live from the publisher's feed (cached half an hour): title, date, duration, description, audio URL. Feeds are slow, so this is the one call here that can take seconds. Also returns an M3U playlist URL for a player that takes one.

Input parameters:

- `limit` (integer): Episodes to return. Default 20.
- `slug` (string, required)

### `list_shows` (~135 tokens)

List shows by subject, language or domain

Shows in one category (a single lowercase word such as history or comedy), one language (ISO 639-1 code) or on one domain, ranked by catalogue depth and longevity weighted by recency, the same order as the site's pages. Call browse first for the categories and languages that exist and how many shows each holds.

Input parameters:

- `category` (string)
- `host` (string): A domain, e.g. example.org.
- `language` (string): ISO 639-1, e.g. en, de, pt.
- `limit` (integer): Default 30.
- `offset` (integer)

### `browse` (~32 tokens)

Subjects and languages

Every category and every language in the directory with its show count and page URL. The cheap first call before list_shows.

### `directory_stats` (~43 tokens)

The directory in numbers

Shows, domains, episodes, how many published this week, how many were added by their publishers, and the OPML export URL for taking the whole thing in one request.

### `submit_feed` (~99 tokens)

Add a podcast to p0dcasters

Submit one URL or a list of them to p0dcasters. A site URL works as well as a feed URL: the feed is discovered from the page. Anyone may submit; there is no account and no review queue. One URL resolves in the call and the answer carries its page; a list may be queued, and the answer says which. Rate limited per caller.

Input parameters:

- `urls` (array, required): Podcast or site URLs. One is fine.

### `get_openprofile` (~124 tokens)

The podcaster's profile

The person or organisation behind a show as an OpenProfile.md (logicsrc.com/openprofile) with the Broadcast section (logicsrc.com/openbroadcast): name, kind, site, avatar, accounts, topics, and the show's feed, cadence, language and since when. Generated from the feed the publisher serves, enriched from rssamplifier.com, corrected by the person once they have claimed it. Returns the Markdown and the URL the file is served at. A booking platform matches a Broadcast section against a guest's Guest section.

Input parameters:

- `slug` (string, required)

### `update_openprofile` (~210 tokens)

Correct a podcaster's profile

Edit the profile on its owner's behalf. Takes either the whole OpenProfile.md as `markdown`, or a partial overlay: `identity` (keys to set, null removes), `headline`, `sections` (body by section name, `none` removes), `public`. The server keeps the difference from the generated document, so a section left alone keeps following the feed. Needs an OpenAccess bearer (hub https://openaccess.logicsrc.com, scope openprofile:edit) in the request's Authorization header, for a profile the person has claimed; an unclaimed profile is refused with the claim step.

Input parameters:

- `headline` (string)
- `identity` (object): Identity keys to set; a null value removes the key.
- `markdown` (string): The whole file, as text.
- `public` (boolean)
- `sections` (object): Section bodies by name (accounts, topics, broadcast, guest, ...); `none` removes.
- `slug` (string, required)

### `claim_openprofile` (~90 tokens)

Claim a podcaster's profile

Claim the profile behind a show as the person it is about. Needs an OpenAccess bearer with scopes openprofile:edit and email in the Authorization header; the claim goes through when the token's address is the feed's itunes:owner address, or when the show's site or feed description links to the profile URL. Nothing else is needed, and nobody reviews it.

Input parameters:

- `slug` (string, required)

### `get_newsletter` (~73 tokens)

The weekly digest

The p0dcasters weekly email: when it goes out (Fridays 15:00 UTC unless reconfigured), the next send time, and the latest issue sent (week, subject, how many it went to). Read-only; subscribing is a setting on a signed-in account, not something this server does.

### `newsletter_preview` (~101 tokens)

This week's digest so far

This week's issue of the weekly digest as it would be built now from the live directory: subject, plain text and, with html: true, the HTML. Shows new to the directory, the most followed this week, long-running shows that published, the busiest networks. Read-only, no recipients; the per-reader unsubscribe link is a placeholder. Rebuilt at most every 15 minutes.

Input parameters:

- `html` (boolean): Include the HTML body too. Default false.

### `list_submissions` (~40 tokens)

The review queue

The submitted feeds waiting for a person to list or reject them. For reviewers: needs an OpenAccess bearer with scope submissions:review in the Authorization header.

### `accept_submissions` (~101 tokens)

Accept all waiting submissions

List every submission waiting for review at once, or only the given ids (from list_submissions). A feed already in the directory comes back as existing; one failure does not stop the rest. Returns counts listed / existing / failed and a result per id. Needs an OpenAccess bearer with scope submissions:review.

Input parameters:

- `ids` (array): Only these submissions. Omit for all waiting.
- `reason` (string): A note for the review log.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-profullstack-p0dcasters/api-mcp#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 77
- 2026-11-19: 77
- 2026-11-18: 76
- 2026-11-17: 59
- 2026-11-16: 74
- 2026-11-15: 74
- 2026-11-14: 74
- 2026-11-13: 74
- 2026-11-12: 73
- 2026-11-11: 4

## Common questions

### What is the p0dcasters MCP server?

p0dcasters is an MCP server listed in the public MCP registry as com.profullstack/p0dcasters. Podcast directory (p0dcasters.com). This page covers its hosted endpoint (https://p0dcasters.com/api/mcp).

### Is the p0dcasters MCP server safe to use?

p0dcasters scores 78 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 p0dcasters MCP server expose?

p0dcasters exposes 14 tools: search, get_podcast, list_episodes, list_shows, browse, and 9 more. Their descriptions and schemas cost roughly 1,318 tokens of context every time the server is loaded.

### Does the p0dcasters MCP server require authentication?

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

### Is the p0dcasters MCP server still maintained?

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

### What did VerifyMCP test on the p0dcasters MCP server?

VerifyMCP ran 13 checks on p0dcasters, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://p0dcasters.com/api/mcp
- Website: https://p0dcasters.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-profullstack-p0dcasters/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-profullstack-p0dcasters/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-profullstack-p0dcasters/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-profullstack-p0dcasters/api-mcp
