Track Podcasts
REMOTE · TRACKPODCASTS.COM
Who sponsors which podcasts, from transcribed ad reads. Free: 10 calls/day with no key, 25 with one.
Available components
Last scanned (1 hour ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 576 tokens (~115/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability check failed: schema churn in the 15 days we've observed: 0 tool removals, 0 breaking changes, 1 auth/transport breaks, 0 additions. See how to fix → Fail
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40.
- 4 Nov 26 −12
- Authorization: fail → unverified ▼ security
- Stability: 0.43 → fail ▼ security
- Server version: 1.0.0 → 1.1.0 functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 1 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.
- 30 Oct 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.
- 28 Oct 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.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +11
- Transport: fail → pass ▲ security
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 5 Nov 2026 · Probed https://trackpodcasts.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trackpodcasts.com | CN=WE1,O=Google Trust Services,C=US | 30 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | cb180c524411c2790eeaa03e6762269d |
| SANs: trackpodcasts.com, *.trackpodcasts.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 trackpodcasts.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| trackpodcasts.com. | absent | 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 |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trackpodcasts.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://trackpodcasts.com/api/mcp | HTTPS enforced | 301 | https://trackpodcasts.com/api/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_brand_podcasts Podcasts a brand sponsors ~102
Which podcasts a brand advertises on. Returns the shows where that brand's ad reads were detected, newest first, with the exact total even when the list itself is truncated for the plan. Accepts a brand name, slug or domain (a domain is the most reliable). Returns candidate brands when the name is ambiguous.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Brand name, slug or domain, e.g. "Squarespace" or "squarespace.com". |
No output schema declared.
No examples provided.
get_busiest_categories Busiest advertiser categories ~68
Which advertiser categories are buying the most podcast ads right now, by ad reads detected, with the number of brands and shows behind each. Aggregate only — it does not list the brands in a category.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window in days. Defaults to 30. |
No output schema declared.
No examples provided.
get_coverage_info What this dataset covers ~62
How much of podcasting this dataset actually covers: shows indexed, episodes transcribed, and the real number of brands and shows with detected ad reads. Call this before stating any sponsor finding as complete, and to explain why a show or brand might be missing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_show_sponsors Sponsors of a podcast ~129
Who sponsors a given podcast. Returns every brand whose ad read was detected in that show's transcribed episodes, with how many reads, whether they were host-read or network-inserted, and when they were first and last heard. Accepts a show title, a trackpodcasts.com slug or a URL. If the title is ambiguous it returns candidate shows to choose from instead of guessing. Detected ad reads only — brands that were merely mentioned are not included.
| Name | Type | Req | Description |
|---|---|---|---|
| show | string | yes | Podcast title, slug or trackpodcasts.com URL, e.g. "The Glenn Beck Program". |
No output schema declared.
No examples provided.
get_sponsor_activity_summary A brand’s advertising over time ~111
How a brand’s podcast advertising has moved month by month: shows reached, ad reads detected and organic mentions, for up to 36 months. Use this for trend questions ("is this brand spending more?", "when did they start?"). Months with no detections are returned as zero, which means nothing was detected rather than that the brand stopped.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Brand name, slug or domain. |
| months | integer | – | Months of history to return. Defaults to 12. |
No output schema declared.
No examples provided.
How do I install the Track Podcasts MCP server?
Track Podcasts is a hosted endpoint at https://trackpodcasts.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.
remote · trackpodcasts.com
claude mcp add --transport http com-trackpodcasts-podcast-sponsors 'https://trackpodcasts.com/api/mcp'
What is the Track Podcasts MCP server?
Track Podcasts is an MCP server listed in the public MCP registry as com.trackpodcasts/podcast-sponsors. Who sponsors which podcasts, from transcribed ad reads. Free: 10 calls/day with no key, 25 with one. This page covers its hosted endpoint (https://trackpodcasts.com/api/mcp).
Is the Track Podcasts MCP server safe to use?
Track Podcasts scores 72 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 Track Podcasts MCP server expose?
Track Podcasts exposes 5 tools: get_show_sponsors, get_brand_podcasts, get_sponsor_activity_summary, get_coverage_info, get_busiest_categories. Their descriptions and schemas cost roughly 472 tokens of context every time the server is loaded.
Does the Track Podcasts MCP server require authentication?
No. We connected to Track Podcasts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Track Podcasts MCP server still maintained?
Track Podcasts is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.