Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BitePods

REMOTE · BITEPODS.COM

Free podcast clip maker: share the exact moment of an episode from YouTube, Spotify or Apple.

Available components

+3 this week 75 Trust /100

Last scanned (18 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

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
Schema Quality & AI Usability76
  • 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 2146 tokens (~238/item across 9 items; 7 tools + 2 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 Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

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 →

Changelog

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 14 Nov 26 +1

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

  • 13 Nov 26 0
    • Tool “list_episodes” rewrote its description, which is the text the model reads security
  • 12 Nov 26 +1

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

  • 11 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 70

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://bitepods.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bitepods.com CN=WE1,O=Google Trust Services,C=US 22 Oct 2026 20 Jan 2027 ECDSA 256 ECDSA-SHA256 302627d2937db9e6132a9c0cf67a57cb
SANs: bitepods.com, *.bitepods.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of bitepods.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
bitepods.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
Header Value
content-security-policy default-src 'none'; sandbox
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://bitepods.com/mcp Verified 200
http (plaintext) http://bitepods.com/mcp HTTPS enforced 301 https://bitepods.com/mcp
MCP tools · 7 exposed · ~1,825 tokens

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 →

Tool Tokens
create_clip ~479

Marks a span of an episode and hands back the links that play it. Nothing is downloaded, transcoded or re-hosted: a clip is a pointer — the publisher's own URL plus an in and an out point — so the whole clip fits in its link and this call cannot fail for reasons of storage. The episode's name and cover are resolved and returned, so you can check you clipped what you meant to before sharing the link. Times are seconds from the start of the episode, decimals allowed. Returns `{ clip, links: { page, short, sourceAtMoment, mp3 }, shareText }`. Usually followed by: share links.short (or links.page); links.mp3 downloads the audio.

NameTypeReqDescription
audioUrlstring–The episode's audio file, when `url` is a page rather than the file. Pass the `audioUrl` from a resolve or an episode list: the clip then plays without waiting on the page to be read again.
endnumberyesWhere it ends, in seconds. Must be at least half a second after `start`.
shortenboolean–Also register the `/x/<id>` short link, which is the one thing this service stores. Set false to get only the self-contained long link and write nothing.
showUrlstring–The show this episode came out of (its feed). Pass the `showUrl` a resolve or an episode list gave you: it is what lets the clip page name the episode when its own page won't say, and what keeps a cl…
startnumberyesWhere the clip starts, in seconds from the start of the episode.
titlestring–A title of your own for this clip, shown in place of the episode's on the clip's card, its page and the link's unfurl. The episode's name says which episode; this says what the clip is, which is what…
urlstringyesThe episode to clip. Use the `clipUrl` from list_episodes or resolve_url when you have one.
NameTypeReqDescription
clipobjectyes–
linksobjectyes–
notestring––
playsinteger–Approximate: a per-clip counter, not an audit trail.
shareTextstringyes–
shortIdstring–The id in `/x/<id>`, when one was registered.
shortenedboolean––

No examples provided.

get_clip ~112

What a short id stands for: the episode, the two times, the links, and how many times the clip has been played. The id is the `/x/<id>` part of a short link. Play counts are approximate by design — a per-clip counter with no atomic increment behind it, not an audit trail. Returns `{ clip, links, plays, shareText }`.

NameTypeReqDescription
idstringyesThe short id, 8-32 characters, as it appears in `/x/<id>`.
NameTypeReqDescription
clipobjectyes–
linksobjectyes–
notestring––
playsinteger–Approximate: a per-clip counter, not an audit trail.
shareTextstringyes–
shortIdstring–The id in `/x/<id>`, when one was registered.
shortenedboolean––

No examples provided.

get_transcript ~345

The episode's own transcript with absolute timestamps in seconds, so a line's `start` is a number you can pass straight to create_clip. This is how you find the moment worth clipping: read the transcript, choose the span, clip it. These are the publisher's transcripts (Podcasting 2.0 `<podcast:transcript>`), and only about one show in six ships one. There is no speech-to-text here — deliberately, and it is not coming — so an episode without one answers `available: false` with a reason rather than an approximation. Cue-timed, not word-timed: a long cue is split into readable lines and `estimated: true` says the split points are interpolated between two known times. Returns `{ available, lines, lineCount, truncated, estimated, episode, … }`; `available: false` carries `reason`. Usually followed by: create_clip with a line's start and end.

NameTypeReqDescription
endnumber–Only lines that overlap up to this many seconds. 0 means to the end of the episode.
limitinteger–How many lines to return, at most. Clamped to 2000.
showUrlstring–The show the episode came out of (its feed). Pass the episode's `showUrl` from list_episodes: an episode whose `clipUrl` is its audio file finds its transcript through the feed.
startnumber–Only lines that overlap from this many seconds into the episode.
urlstringyesThe episode. An episode page, a direct audio file, or a `clipUrl` from list_episodes.
NameTypeReqDescription
availablebooleanyes–
episodeobjectyes–
estimatedboolean–True when long cues were split, so the split times are interpolated.
lineCountinteger––
linesarray––
reasonstring–Why there are no lines, when `available` is false.
totalLinesinteger––
transcriptUrlstring––
truncatedboolean–True when `limit` cut the answer; narrow the window or raise it.
windowobject––

No examples provided.

list_episodes ~353

Episodes of a show, newest first, from its RSS feed or its Apple Podcasts page. Feeds are read up to 60 items — that is the cap, not a page you can walk past. Each episode carries a `clipUrl`: pass it back as `url` to `create_clip` or `get_transcript` and the right episode is clipped, whatever the show's pages look like. Errors with `not_a_show` if the URL is one episode rather than a show. An episode from a feed may also carry `chapters` — the publisher's own timestamp index, read out of the show notes, as `{ startSeconds, title }` in the order they happen. That is a human being naming the parts of their own episode, so it is the cheapest way to find a moment worth clipping: pick a chapter, pass its `startSeconds` to `create_clip` as `start`, and the next chapter's `startSeconds` as `end`. Roughly two shows in five publish one, and a show that doesn't simply has no `chapters` field. Returns `{ show, episodes, total, offset, limit, hasMore }`. An episode may carry `chapters` and `soundbites`. Usually followed by: An episode's own `chapters` are the quickest way to a moment; get_transcript reads the words where a show publishes one. Then create_clip.

NameTypeReqDescription
limitinteger–How many episodes to return, at most. Clamped to 60.
offsetinteger–Skip this many episodes first, to page through a long feed.
urlstringyesA show: its RSS feed or Apple Podcasts page.
NameTypeReqDescription
episodesarrayyes–
hasMorebooleanyes–
limitintegeryes–
offsetintegeryes–
showobjectyes–
totalintegeryesEpisodes the source listed, up to the 60-item cap.

No examples provided.

resolve_url ~209

Turns any pasted link into something clippable, and says which of three things it is: `episode` (one playable thing, ready for create_clip), `show` (a feed or channel — a preview of its episodes, with list_episodes for the rest), or `unresolved` (nothing playable was found, and why). Answering `unresolved` is a real answer, not a failure: clipping the wrong audio confidently is worse. Spotify links resolve to the same episode in the show's own feed, because nothing else can play Spotify. Returns `{ type: 'episode' | 'show' | 'unresolved', … }` — always 200; read `type`. Usually followed by: create_clip for an episode, list_episodes for a show.

NameTypeReqDescription
urlstringyesAnything that points at an episode: an Apple Podcasts or Spotify episode link, an episode's own web page, an RSS feed, or a direct .mp3/.m4a file.

Structured output declared, but exposes no named fields.

No examples provided.

search_shows ~174

Searches the public podcast directory by show name. Use it when you have a name rather than a link. Each hit carries the show's RSS feed as `sourceUrl` — hand that to `list_episodes`. It searches shows, never episodes: there is no index of episode titles to search, so finding one episode means listing a show's episodes and matching the title yourself. Shows Apple rates explicit are left out. Returns `{ shows }` — id, name, author, artwork, feed, and the `sourceUrl` to list episodes from. Usually followed by: list_episodes with a show's sourceUrl.

NameTypeReqDescription
limitinteger–How many shows to return, at most. Clamped to 25.
qstringyesThe show's name, or enough of it to be distinctive. Two characters minimum.
NameTypeReqDescription
countrystring–Chart answers only: the country the chart is for.
showsarrayyes–

No examples provided.

top_shows ~153

The most-subscribed shows in a country, ranked. Useful as a starting point when nothing specific was named, and as a way to check that a show is the well-known one rather than a similarly named feed. Country defaults to the one the request came from. Returns `{ country, shows }`, each show carrying its 1-based `rank`. Usually followed by: list_episodes with a show's sourceUrl.

NameTypeReqDescription
countrystring–Two-letter ISO country code (`us`, `gb`, `de`). Defaults to the country the request arrives from, and to `us` when that is unknown.
limitinteger–How many shows to return, at most. Clamped to 100.
NameTypeReqDescription
countrystring–Chart answers only: the country the chart is for.
showsarrayyes–

No examples provided.

Install

How do I install the BitePods MCP server?

BitePods is a hosted endpoint at https://bitepods.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 · bitepods.com

# add to Claude Code
claude mcp add --transport http com-bitepods-bitepods 'https://bitepods.com/mcp'
Common questions

What is the BitePods MCP server?

BitePods is an MCP server listed in the public MCP registry as com.bitepods/bitepods. Free podcast clip maker: share the exact moment of an episode from YouTube, Spotify or Apple. This page covers its hosted endpoint (https://bitepods.com/mcp).

Is the BitePods MCP server safe to use?

BitePods scores 75 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 BitePods MCP server expose?

BitePods exposes 7 tools: search_shows, top_shows, list_episodes, resolve_url, get_transcript, and 2 more. Their descriptions and schemas cost roughly 1,825 tokens of context every time the server is loaded.

Does the BitePods MCP server require authentication?

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

Is the BitePods MCP server still maintained?

BitePods 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 BitePods MCP server?

VerifyMCP ran 13 checks on BitePods, 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.