Ext Ops Panel
Open dashboard
Comparison

com.petabloom/podcasts vs Podwise

com.petabloom/podcasts is an MCP server published by petabloom.com. Marketplaces we read that list it: 1 (Official MCP Registry). Podwise is an MCP server published by hardhackerlabs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacecom.petabloom/podcastsPodwise
Official MCP Registry Listed
Version: 0.2.8
No figure published
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

com.petabloom/podcasts vs Podwise
Factcom.petabloom/podcastsPodwise
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (podcasts.petabloom.com/mcp)Remote server (mcp.podwise.ai/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/hardhackerlabs/podwise-plugin
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-18
Endpoint at the last check (differs)Responded 2 h agonot checked yet

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

com.petabloom/podcasts

In its own words, on Official MCP Registry:

An MCP server that provides tools to discover and retrieve podcast episodes transcripts.

Podwise

In its own words, on Official MCP Registry:

Podcast knowledge for AI agents: search episodes, pull transcripts and ask questions.

How to run each

com.petabloom/podcasts As a remote MCP server

Claude Code
claude mcp add --transport http podcasts https://podcasts.petabloom.com/mcp

Podwise As a remote MCP server

Claude Code
claude mcp add --transport http podwise https://mcp.podwise.ai/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only com.petabloom/podcasts has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: com.petabloom/podcasts · What it can do: Podwise · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built