trackpodcasts
Registry code: f25f275c90b99988
Podcast sponsorship data detected from transcribed audio. Use get_show_sponsors for "who sponsors X", get_brand_podcasts for "where does brand Y advertise", get_sponsor_activity_summary for trends over time, and get_busiest_categories for the market view. Coverage is partial and growing: every response carries a coverage note, and you should pass that caveat on rather than presenting a list as complete. Each response also carries a source link — include it so the reader can check the data.
- endpoint
- https://trackpodcasts.com/api/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is trackpodcasts live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is trackpodcasts free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does trackpodcasts have?
- 5 tools: get_coverage_info, get_brand_podcasts, get_busiest_categories, get_sponsor_activity_summary, get_show_sponsors.
- Is trackpodcasts safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_coverage_info auth-required 1h ago
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_brand_podcasts auth-required 1h ago
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.
{ "type": "object", "required": [ "brand" ], "properties": { "brand": { "type": "string", "description": "Brand name, slug or domain, e.g. \"Squarespace\" or \"squarespace.com\"." } }, "additionalProperties": false }arguments 13 linesget_busiest_categories auth-required 1h ago
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.
{ "type": "object", "properties": { "days": { "enum": [ 30, 90, 365 ], "type": "integer", "description": "Lookback window in days. Defaults to 30." } }, "additionalProperties": false }arguments 15 linesget_sponsor_activity_summary auth-required never probed
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.
{ "type": "object", "required": [ "brand" ], "properties": { "brand": { "type": "string", "description": "Brand name, slug or domain." }, "months": { "type": "integer", "maximum": 36, "minimum": 1, "description": "Months of history to return. Defaults to 12." } }, "additionalProperties": false }arguments 19 linesget_show_sponsors auth-required never probed
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.
{ "type": "object", "required": [ "show" ], "properties": { "show": { "type": "string", "description": "Podcast title, slug or trackpodcasts.com URL, e.g. \"The Glenn Beck Program\"." } }, "additionalProperties": false }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idf25f275c90b99988.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f25f275c90b99988/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f25f275c90b99988?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.