MCP.Market

Podcast Parser MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/podcast-parser·v0.2.1

podcast-parser (CanonCannon) — what gets repeated across 162 tracked podcasts.

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Podcast Parser yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Podcast Parser tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Podcast Parser compares

Against every graded Media MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 1,337 Media servers
Uptime
100%
of our recent checks; the typical remote Media server answers 100%
Response time
102 ms
faster than 88% of 862 Media servers

Release history: 4 versions in the registry since 2026-09-16, latest 2026-11-04, typically one every 8 days.

Install Podcast Parser in Claude Code, Cursor or VS Code

claude mcp add --transport http podcast-parser https://gateway.pipeworx.io/podcast-parser/mcp
Add to Cursor

What the publisher says

From the Podcast Parser repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/podcast-parser

What gets repeated across 162 tracked podcasts — claims extracted from 10,000+ episodes, each carrying the measurement behind its status: how many independent podcasts and speakers repeat it, excluding whoever originated it.

Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.

LIVE, BYO-ONLY. Promoted out of _incubator and wired into the gateway on 2026-09-14 (fleet #1958), once Bruce's partner key existed and all eight exported tools returned non-empty payloads against the real API.

It ships BYO-only even though a Pipeworx platform key exists, and that is a deliberate choice, not an oversight. The gateway is AT Cloudflare's limit of 250 text bindings, so wrangler secret put PLATFORMCANONCANNONKEY is rejected outright — "Too many text bindings, found a total of 251, they exceed the limit of 250" (code 10055). Declaring platformKeyEnv without the secret actually present would un-sink this pack in routing and send podcast-consensus questions to a tool that can only refuse, which is strictly worse than an honest nomatch — the fda-inspections precedent, fleet #617. So the pack declares no platformKeyEnv, keyBlockedTools() keeps it out of askpipeworx retrieval, and a caller with their own CanonCannon key can still call it directly with _apiKey.

To finish it: free one text binding on the gateway, then land the wrangler secret put and platformKeyEnv: 'PLATFORMCANONCANNONKEY' in the SAME change. The key itself is already issued, stored in the canonical checkout's gitignored .env, and verified live. canon_citations is separately held — see the integrity gate.

Tools

Eight are exported. canon_citations is implemented and deliberately held — see the integrity gate.

Each row carries tier and its measurement.

  • canon_search(query?, tier?, label?, limit?, cursor?) — find recurring ideas.

books, plus the measurement spelled out in one sentence beside it.

  • canon_get(slug) — the full entry: claim, evidence, nuance, gaps, related,

of the canon bar.

  • canonepisodesearch(query?, podcast?, since?, limit?, cursor?) — the episode corpus.
  • canonepisodeget(slug) — one episode with its extracted ideas, guests and books.
  • canonpersonget(slug) — what one person has actually said, across shows.
  • canonpodcastlist(limit?, cursor?) — the tracked-show roster, i.e. the denominator

and originator involvement.

  • canonpodcastget(slug) — one tracked show.
  • canoncorpusstats() — corpus counts and the bar currently in force.
  • canoncitations(slug) — HELD.** Every episode citing an idea, with speakers

Auth

BYO only today: apiKey (Authorization: Bearer cclive...). Every /api/v1 endpoint refuses without one — GET /stats with no key is a clean 401 {"error":"Missing or malformed API key. Send Authorization: Bearer cclive_..."}, so a missing credential is unambiguous rather than looking like an outage.

There is no platformKeyEnv because we hold no key. When Bruce issues the partner key, wire PLATFORMCANONCANNONKEY on the gateway in the SAME change that adds the MCP_PACKS entry (fda-inspections precedent, fleet #617) — a declared-but-unset platform key sinks every tool in the pack under the key rule and reads to a caller as a broken pack rather than an unfunded one.

The citations endpoint is additionally restricted to an internal-tier key, so a partner key gets 403 there. That is upstream policy, not our gate.

The measurement envelope — the whole contract

tier is never served without a measurement sibling, in one of exactly two shapes:

{ "available": true, "measured_at": "…", "independent_podcasts": 23,
  "independent_speakers": 41, "independent_episodes": 36,
  "threshold": 9, "tracked_podcasts": 162 }

{ "available": false, "reason": "not_yet_measured" | "not_yet_persisted" }

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Podcast Parser: common questions

Is Podcast Parser MCP server safe?
Mostly: it is graded B (77/100). Read the Podcast Parser safety report
How do I install Podcast Parser?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Podcast Parser need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Podcast Parser maintained?
The last commit was 39 days ago (2026-09-26). The latest release is v0.2.1.
Is Podcast Parser up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Podcast Parser?
Servers from other publishers that do the same job: Katto MCP server, Spoken MCP server and Spotify Trends MCP server.
How does Podcast Parser compare with other Media MCP servers?
safety score 77/100 (higher than 50% of 1,337 Media servers); uptime 100% (of our recent checks; the typical remote Media server answers 100%); response time 102 ms (faster than 88% of 862 Media servers). Full comparison.

Alternatives to Podcast Parser

Same job from other publishers: the closest match first, then the best rated.

  • Katto
    AI video clipping MCP: long videos and podcasts into scored, captioned 9:16 shorts.
    B
  • Spoken
    Podcast transcripts as clean Markdown with real speaker names — via the Spoken API.
    A
  • Spotify Trends MCP
    Spotify podcast and artist trends over time, with growth metrics. Free key at trendsmcp.ai
    A
  • Aetherwave
    Music, image, video and audio generation across top AI providers - one key, one credit pool.
    B

More from pipeworx-io →