com.petabloom/podcasts
REMOTE · PODCASTS.PETABLOOM.COM
An MCP server that provides tools to discover and retrieve podcast episodes transcripts.
Available components
Last scanned (16 hours ago)
Scores higher than 90% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Search and Retrieval
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1612 tokens (~268/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 26 Oct 26 0
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 25 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 18 Oct 26 0
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Nov 2026 · Probed https://podcasts.petabloom.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=podcasts.petabloom.com | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 18 Aug 2026 | 3 Mar 2027 | RSA 2048 | SHA256-RSA | 432e6954cabce933b6f383ad562210c |
| SANs: podcasts.petabloom.com | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of podcasts.petabloom.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| petabloom.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://podcasts.petabloom.com/mcp | Verified | 200 | |
| http (plaintext) | http://podcasts.petabloom.com/mcp | HTTPS enforced | 301 | https://podcasts.petabloom.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_latest_episodes Get Latest Episodes ~158
Return the most recent transcript-ready episodes across the full podcast catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | integer | – | Zero-based episode offset for pagination. Use the `next_cursor` returned by a prior search/listing call to fetch the next page of results. |
| limit | integer | – | Maximum number of episodes to return. Must be between 1 and 50. |
| published_after | – | – | Inclusive lower publication-date bound. Accepts YYYY-MM-DD or ISO 8601 datetime. |
| published_before | – | – | Inclusive upper publication-date bound. Accepts YYYY-MM-DD or ISO 8601 datetime. |
| sort | string | – | Sort order for results. `relevance` ranks full-text searches first and falls back to newest-first when no query is provided. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of episodes returned on this page. |
| episodes | array | yes | Matching transcript-ready episodes. |
| next_cursor | – | – | Cursor to pass to the next search call to retrieve the next page of results, or null if there are no more pages. |
| total_count | integer | yes | Total number of matching transcript-ready episodes across all pages. |
| total_count_is_approximate | boolean | – | When true, `total_count` is a lower bound — more matches may exist than were counted. False for exact lexical/date counts; can be true only for semantic results (e.g. the topic-search fallback). |
No examples provided.
get_transcript Get Transcript ~153
Fetch a bounded transcript chunk for a specific episode using its show and episode GUIDs. Use `next_cursor` to continue reading.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | integer | – | Zero-based character offset into the transcript. Use the `next_cursor` returned by a prior get_transcript call to fetch the next chunk. |
| episode_guid | string | yes | Episode GUID returned by `search_episodes` or `get_latest_episodes`. |
| max_chars | integer | – | Target maximum number of transcript characters to return. Chunks prefer natural boundaries and may be slightly shorter. Must be between 100 and 20000. |
| show_guid | string | yes | Podcast show GUID returned by `search_episodes` or `get_latest_episodes`. |
| Name | Type | Req | Description |
|---|---|---|---|
| char_end | integer | yes | Exclusive zero-based end offset of this chunk in the complete transcript. |
| char_start | integer | yes | Inclusive zero-based start offset of this chunk in the complete transcript. |
| duration_seconds | – | – | Episode duration in seconds when available from the source feed. |
| episode_guid | string | yes | Podcast episode GUID requested by the client. |
| episode_title | string | yes | Podcast episode title. |
| has_more | boolean | yes | Whether another get_transcript call is needed to continue reading. |
| next_cursor | – | – | Cursor to pass to the next get_transcript call, or null at the end. |
| published_date | string | yes | Episode publication timestamp in ISO 8601 format. |
| rss_feed_url | string | yes | RSS feed URL for the podcast show. |
| show_guid | string | yes | Podcast show GUID requested by the client. |
| show_title | string | yes | Podcast show title. |
| text | string | yes | Transcript chunk text. |
| total_chars | integer | yes | Total character count of the complete transcript text. |
No examples provided.
give_feedback Give Feedback ~51
Send structured feedback about bugs, missing data, unclear behavior, or feature requests.
| Name | Type | Req | Description |
|---|---|---|---|
| feedback | string | yes | Feedback for the server team. Include the problem, missing capability, or suggested improvement without sensitive user data. |
| Name | Type | Req | Description |
|---|---|---|---|
| feedback_id | string | yes | Stable feedback identifier. |
| message | string | yes | Human-readable result summary. |
| status | string | yes | Feedback persistence status. |
No examples provided.
search_episodes Search Episodes ~236
Search indexed podcast episodes by keyword or show name and return the show/episode GUIDs needed for transcript retrieval.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | integer | – | Zero-based episode offset for pagination. Use the `next_cursor` returned by a prior search/listing call to fetch the next page of results. |
| limit | integer | – | Maximum number of episodes to return. Must be between 1 and 50. |
| podcast_name | string | – | Optional podcast title or internal label to narrow results to a specific show. |
| published_after | – | – | Inclusive lower publication-date bound. Accepts YYYY-MM-DD or ISO 8601 datetime. |
| published_before | – | – | Inclusive upper publication-date bound. Accepts YYYY-MM-DD or ISO 8601 datetime. |
| published_within_hours | – | – | Filter episodes published in the past X hours. Maximum 168 hours (1 week). |
| query | string | – | Optional search keywords matched against indexed episode content. Use people, topics, companies, or phrases. |
| sort | string | – | Sort order for results. `relevance` ranks full-text searches first and falls back to newest-first when no query is provided. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of episodes returned on this page. |
| episodes | array | yes | Matching transcript-ready episodes. |
| next_cursor | – | – | Cursor to pass to the next search call to retrieve the next page of results, or null if there are no more pages. |
| total_count | integer | yes | Total number of matching transcript-ready episodes across all pages. |
| total_count_is_approximate | boolean | – | When true, `total_count` is a lower bound — more matches may exist than were counted. False for exact lexical/date counts; can be true only for semantic results (e.g. the topic-search fallback). |
No examples provided.
search_episodes_by_topic Search Episodes by Topic ~359
Semantic topic search across the podcast catalog. Unlike `search_episodes` (which does lexical/keyword matching), this tool understands meaning: a query for 'AI safety' will match episodes about 'AI alignment', 'AGI risk', or 'frontier model evaluation' even if they don't contain the exact phrase. Returns ranked episodes with the matched topic phrases so you can explain *why* each result is relevant before fetching the transcript. Best for conceptual or thematic queries — use `search_episodes` instead when the user is looking for a specific person, product, or verbatim phrase.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | integer | – | Zero-based episode offset for pagination. Use the `next_cursor` returned by a prior search/listing call to fetch the next page of results. |
| limit | integer | – | Maximum number of episodes to return. Must be between 1 and 50. |
| published_after | – | – | Inclusive lower publication-date bound. Accepts YYYY-MM-DD or ISO 8601 datetime. |
| published_before | – | – | Inclusive upper publication-date bound. Accepts YYYY-MM-DD or ISO 8601 datetime. |
| show_guid | string | – | Optional canonical show GUID (as returned by `search_episodes` or `get_latest_episodes` in the `show_guid` field) to restrict topic search to a single podcast. Leave empty to search across all shows. |
| topic | string | yes | Semantic topic to find episodes about. Free-form phrasing welcome — the server embeds this string and finds episodes whose extracted topic phrases are closest in meaning. Good examples: 'AI safety',… |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of episodes returned on this page. |
| episodes | array | yes | Episodes ranked by best topic-phrase similarity to the query. |
| next_cursor | – | – | Cursor to pass to the next search call to retrieve the next page of results, or null if there are no more pages. |
| query | string | yes | The topic query that was embedded and searched. |
| total_count | integer | yes | Number of matching episodes, counted over the nearest-match candidate window rather than the whole catalog. When `total_count_is_approximate` is true, treat this as a lower bound — broad queries may… |
| total_count_is_approximate | boolean | – | True when the candidate window was exhausted, so `total_count` undercounts the true number of matches. When false, `total_count` is exact. Refine the query for tighter results if this is true and you… |
No examples provided.
How do I install the com.petabloom/podcasts MCP server?
com.petabloom/podcasts is a hosted endpoint at https://podcasts.petabloom.com/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.
remote · podcasts.petabloom.com
claude mcp add --transport http com-petabloom-podcasts 'https://podcasts.petabloom.com/mcp'
What is the com.petabloom/podcasts MCP server?
com.petabloom/podcasts is an MCP server listed in the public MCP registry as com.petabloom/podcasts. An MCP server that provides tools to discover and retrieve podcast episodes transcripts. This page covers its hosted endpoint (https://podcasts.petabloom.com/mcp).
Is the com.petabloom/podcasts MCP server safe to use?
com.petabloom/podcasts 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 com.petabloom/podcasts MCP server expose?
com.petabloom/podcasts exposes 5 tools: search_episodes, get_latest_episodes, search_episodes_by_topic, get_transcript, give_feedback. Their descriptions and schemas cost roughly 957 tokens of context every time the server is loaded.
Does the com.petabloom/podcasts MCP server require authentication?
No. We connected to com.petabloom/podcasts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.petabloom/podcasts MCP server still maintained?
com.petabloom/podcasts is still listed as active in the MCP registry. We last reached this channel on 7 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 com.petabloom/podcasts MCP server?
VerifyMCP ran 13 checks on com.petabloom/podcasts, 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.