原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Podcast Parser

作者:pipeworx-io版本 0.2.1i★ –i电脑或云端
注册名称io.github.pipeworx-io/podcast-parser

安装

概览

作者提供的说明(英文原文)

podcast-parser (CanonCannon) — what gets repeated across 162 tracked podcasts.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 电脑或云端
  • 传输方式: stdio, Streamable HTTP
  • 分类: 游戏、体育、美食与学习
  • 你需要填写:PIPEWORX_API_KEY

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你需要

  • 在云端运行无需安装任何东西,通过互联网连接
  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude:

  1. 打开 Settings → Connectors
  2. 点击 Add custom connector
  3. 粘贴下面的地址,然后点击 Add
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Add2https://…3
https://gateway.pipeworx.io/podcast-parser/mcp

或者在你的电脑上运行

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "podcast-parser": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-podcast-parser"
      ],
      "env": {
        "PIPEWORX_API_KEY": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add --transport http podcast-parser https://gateway.pipeworx.io/podcast-parser/mcp

或者在你的电脑上运行

claude mcp add podcast-parser --env PIPEWORX_API_KEY=your-value -- npx -y @pipeworx/mcp-podcast-parser

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "podcast-parser": {
      "url": "https://gateway.pipeworx.io/podcast-parser/mcp"
    }
  }
}

或者在你的电脑上运行

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "podcast-parser": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-podcast-parser"
      ],
      "env": {
        "PIPEWORX_API_KEY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "podcast-parser": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/podcast-parser/mcp"
    }
  }
}

或者在你的电脑上运行

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "podcast-parser": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-podcast-parser"
      ],
      "env": {
        "PIPEWORX_API_KEY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

ChatGPT 只能连接互联网上的服务器:

  1. 打开网页版 ChatGPT → Settings → Connectors (Apps)
  2. 点击 Create 或 Add(部分套餐需要先在 Advanced 中开启 Developer mode)
  3. 粘贴下面的地址,起个名字,然后保存
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Create2https://…3
https://gateway.pipeworx.io/podcast-parser/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • PIPEWORX_API_KEY 机密 env
    Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • ask_pipeworx

    PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring au

  • ask_pipeworx_beta

    Beta version of ask_pipeworx: identical universal router (same 7,176 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so

  • ask_pipeworx_grounded

    Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 7,176 across 1863 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbati

  • search_within

    Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into th

  • deep_research

    ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1863 STRUCTURED data sources (SEC filings,

  • discover_tools

    Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real est

  • resolve_entity

    "What's the ticker for…" / "find the CIK for…" / "what's the LEI for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X's official identifier" / "who owns X" / "is X a subsidiary of Y" — resolve a user-spoken NAME to the canonical/official identifiers other tools re

  • compare_entities

    "Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing

  • subscribe

    Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = o

  • unsubscribe

    Cancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.

  • list_subscriptions

    List the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.

  • recent_alerts

    Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp).

  • entity_profile

    "Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over cha

  • recent_changes

    "What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings s

  • validate_claim

    "Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm or refute" / "true or false" — natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is f

  • company_facts

    TYPED, DETERMINISTIC financial facts for a US public company for an EXPLICITLY NAMED reporting period — "Apple revenue for fiscal 2023", "Walmart net income FY2026 Q3", "Microsoft cash at the end of fiscal 2024". PREFER OVER entity_profile / get_company_financials whenever the pe

  • company_register_search

    Search the NATIONAL BUSINESS REGISTERS by company name and get the register's own id back — a Companies House number, a Norwegian organisasjonsnummer, a Finnish business id, a SIREN, a Japanese corporate number, an Estonian registry code, a CNPJ, or an LEI. Use this when you want

  • scan_dependency

    Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular

  • bet_research

    Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-kristi-noem-win-the-2028-republican-presidential-nomination"), a polymarket.com URL, or a question text. A dated slug ("...-by-june-30-2026") still resolves after it sett

  • polymarket_arbitrage

    Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets by weekly volume; pass `event` for the strongest per-event partition_check, or `topic` for a themed cross-event scan. `ev

  • polymarket_edges

    Scan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price. Built for "what should I bet on today" — agents discover opportunities without paging hundreds of markets. FIVE MODEL FAMILIES grouped into three response segments under by_segme

  • polymarket_kalshi_spread

    Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ — when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says s

  • polymarket_fill_risk

    Realizable-vs-theoretical edge check against live CLOB order-book depth — AND Polymarket's own taker fee, which is never zero and is folded in rather than left for you to add (fleet #3446: r/PredictionsMarkets flagged a "clean" fill that quietly omitted it as optimistic in the di

  • polymarket_edge_tracker

    Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers "how long has this edge existed and is it shrinking?" — a fresh wide edge and a 3-week-old wide edge are different trades (the latter is wide for a reason nobody is willing to take). Args: d

  • kalshi_weather_edge

    Prices Kalshi daily high-temperature markets against the NWS forecast for the market's OWN settlement station, and measures whether that forecast actually beats the market. Two modes. LIVE (default): returns the full strike ladder for one city and settlement date with market_prob

  • resolution_audit

    Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market: who publishes the settling number (source), the clock time + timezone it is taken at (falling back to the market TITLE when the clause itself says "the time range specified in the title" — e.g. P

  • resolution_diff

    Field-by-field diff of TWO markets' settlement clauses (one from each of `a` and `b`; either can be Polymarket .com, Polymarket US, or Kalshi) — runs resolution_audit on both sides and compares source, settle time, precision, comparison_basis, and evidence standard. Returns `equi

  • release_calendar_markets

    JOIN of the official release calendar (econ data, the FOMC, FDA decisions, SEC rules) against LIVE Polymarket/Kalshi markets — which scheduled releases land in the next N hours, and which live markets resolve on them. This is a POSITIONING tool, not a speed product: results are c

  • prediction_calibration

    REALIZED win rate by shown price and minutes elapsed for short-horizon crypto up/down markets, net of taker fee — read from our own settled-outcomes archive, not from live prices. Answers the one question no venue will: "a side shown at 82 with five minutes left, how often did it

  • updown_venue_compare

    The same 15-minute crypto "up or down" window priced on polymarket.com, Polymarket US and Kalshi, side by side, with whether each pair is actually the same contract. Pass asset (btc | eth | sol | xrp | bnb) and window ("current" default, "next", "previous", or the window START as

  • updown_divergence_rate

    How often two venues settled the SAME 15-minute crypto window differently, over every settled window on record. Compares polymarket.com (Chainlink TWAP) with Kalshi and with Polymarket US (both CF Benchmarks BRTI), and Kalshi with Polymarket US as the same-feed control. Per pair:

  • archive_evidence

    What did a web page say on a given date? Finds the archived capture of a URL nearest that date across the Internet Archive Wayback Machine, Common Crawl and Arquivo.pt, reads it, and returns the readable text (HTML stripped) with the capture timestamp, a link to the archived copy

  • archive_compare

    What changed on a web page between two dates? Resolves the archived capture nearest each date (Internet Archive Wayback Machine, Common Crawl, Arquivo.pt), extracts the readable text of both, and returns a text-level diff: the segments removed and added, a similarity score, and b

  • research_row

    Claygent-style per-row research: answer ONE question about ONE company and return a JSON object matching your output_schema, with every field wrapped in its own evidence — {value, evidence_url, quote, status}. status is NEVER self-reported by the model: "found" means this code in

  • classify_row

    Cheap categorization: given a company and a list of candidate labels, decide which labels apply — the most common GTM/AI usage shape (tagging a list by industry, ICP fit, etc.), one small model call. Same evidence contract as research_row: each label comes back {label, applies, e

  • pipeworx_trending

    What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice

  • suggest_questions

    What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed e

  • generate_llms_txt

    Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at si

  • ai_visibility_check

    Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass `_apiKey` to also probe Anthropic (BYO key — you pay Anthropic directly for those calls). Returns pe

  • scan_competitor_ai_presence

    Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our co

  • pipeworx_feedback

    Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipewor

  • remember

    Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-v

  • recall

    Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous

  • forget

    Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.

  • canon_search

    Search CanonCannon for ideas that recur across podcasts — claims extracted from 10,000+ episodes of 162 tracked shows, each with the MEASUREMENT behind its status: how many independent podcasts and speakers repeat it (excluding whoever originated it) and the bar in force. Use thi

  • canon_get

    The full CanonCannon entry for one idea — the claim, the evidence behind it, the nuance and gaps, related entries and books — alongside its measurement (independent podcast count, independent speaker count, the bar in force, and when it was last verified). Get the slug from canon

  • canon_episode_search

    Search the CanonCannon episode corpus — 10,000+ podcast episodes with the ideas, guests and books extracted from each. Filter by show, by publication date, or by free text. Requires a CanonCannon API key via _apiKey. Example: canon_episode_search({ query: "sleep apnea", since: "2

  • canon_episode_get

    One podcast episode from CanonCannon with everything extracted from it — the ideas it raised, its guests, and the books mentioned. Get the slug from canon_episode_search. Requires a CanonCannon API key via _apiKey. Example: canon_episode_get({ slug: "pa-392-sleep-apnea" }).

  • canon_person_get

    What one person has actually said across podcasts, per CanonCannon — their appearances by show and the ideas attributed to them, drawn from 3,800+ people in the corpus. Answers "does this person keep making this claim, and where" rather than "who is this person". Requires a Canon

  • canon_podcast_list

    Every podcast CanonCannon tracks, with its episode count — the roster that forms the denominator of the canon bar (an idea needs ceil(5%) of these shows to clear it). Requires a CanonCannon API key via _apiKey. Example: canon_podcast_list({ limit: 100 }).

  • canon_podcast_get

    One tracked show from CanonCannon, with its episode count and metadata. Get the slug from canon_podcast_list. Requires a CanonCannon API key via _apiKey. Example: canon_podcast_get({ slug: "peter-attia-drive" }).

  • canon_corpus_stats

    CanonCannon corpus size and the canon bar CURRENTLY in force — entry, episode, idea and person counts, the tracked-podcast count, and the independent-podcast threshold an idea must clear. Call this to state the standard you are quoting: the bar is ceil(5% of tracked podcasts), so

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 pipeworx-io 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • ✓ 通过

    端点有响应

    在 114 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 52 个工具描述,未发现针对 AI 的隐藏指令

与“游戏、体育、美食与学习”中的其他服务器比较i

  • 星标数多于此分类中其他 1290 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1290 个服务器的 88% 更新
  • 基础检查结果等于或优于此分类中其他 1290 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Podcast Parser 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:PIPEWORX_API_KEY

它在我的电脑上运行还是在云端?

两种方式都可以:安装在你的电脑上,或者连接云端版本。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.2.1)于4天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。

有什么可以替代它?

同一分类中有:Sports MCP Server, Social Content MCP Server, Kizupi

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Sports MCP Server

作者:thenextgennexus.com

NBA, NFL, NHL and combined sports scores as agent tools.

在云端运行今天更新
安装

Social Content MCP Server

作者:thenextgennexus.com

Steam games, Dev.to articles, events and podcasts as agent tools.

在云端运行今天更新
安装

Kizupi

作者:miradero

The math tutor that asks why, for grades 1 to 6, with free printable word-problem worksheets.

在云端运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

@pipeworx/podcast-parser

What gets repeated across 162 tracked podcasts — claims extracted from 10,000+ episodes, each carrying the measurement behind its status: how many independent podcasts and speakers repeat it, excluding whoever originated it.

Part of Pipeworx — an MCP gateway connecting AI agents to 1867+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

LIVE, BYO-ONLY. Promoted out of _incubator and wired into the gateway on 2026-09-14 (fleet #1958), once Bruce's partner key existed and all eight exported tools returned non-empty payloads against the real API.

It ships BYO-only even though a Pipeworx platform key exists, and that is a deliberate choice, not an oversight. The gateway is AT Cloudflare's limit of 250 text bindings, so wrangler secret put PLATFORM_CANONCANNON_KEY is rejected outright — *"Too many text bindings, found a total of 251, they exceed the limit of 250"* (code 10055). Declaring platformKeyEnv without the secret actually present would un-sink this pack in routing and send podcast-consensus questions to a tool that can only refuse, which is strictly worse than an honest no_match — the fda-inspections precedent, fleet #617. So the pack declares no platformKeyEnv, keyBlockedTools() keeps it out of ask_pipeworx retrieval, and a caller with their own CanonCannon key can still call it directly with _apiKey.

To finish it: free one text binding on the gateway, then land the wrangler secret put and platformKeyEnv: 'PLATFORM_CANONCANNON_KEY' in the SAME change. The key itself is already issued, stored in the canonical checkout's gitignored .env, and verified live. canon_citations is separately held — see the integrity gate.

Tools

Eight are exported. canon_citations is implemented and deliberately held — see the integrity gate.

  • canon_search(query?, tier?, label?, limit?, cursor?) — find recurring ideas. Each row carries tier and its measurement.
  • canon_get(slug) — the full entry: claim, evidence, nuance, gaps, related, books, plus the measurement spelled out in one sentence beside it.
  • canon_episode_search(query?, podcast?, since?, limit?, cursor?) — the episode corpus.
  • canon_episode_get(slug) — one episode with its extracted ideas, guests and books.
  • canon_person_get(slug) — what one person has actually said, across shows.
  • canon_podcast_list(limit?, cursor?) — the tracked-show roster, i.e. the denominator of the canon bar.
  • canon_podcast_get(slug) — one tracked show.
  • canon_corpus_stats() — corpus counts and the bar currently in force.
  • canon_citations(slug) — HELD. Every episode citing an idea, with speakers and originator involvement.

Auth

BYO only today: _apiKey (Authorization: Bearer cc_live_...). Every /api/v1 endpoint refuses without one — GET /stats with no key is a clean 401 {"error":"Missing or malformed API key. Send Authorization: Bearer cc_live_..."}, so a missing credential is unambiguous rather than looking like an outage.

There is no `platformKeyEnv` because we hold no key. When Bruce issues the partner key, wire PLATFORM_CANONCANNON_KEY on the gateway in the SAME change that adds the MCP_PACKS entry (fda-inspections precedent, fleet #617) — a declared-but-unset platform key sinks every tool in the pack under the key rule and reads to a caller as a broken pack rather than an unfunded one.

The citations endpoint is additionally restricted to an internal-tier key, so a partner key gets 403 there. That is upstream policy, not our gate.

The measurement envelope — the whole contract

tier is never served without a measurement sibling, in one of exactly two shapes:

{ "available": true, "measured_at": "…", "independent_podcasts": 23,

"independent_speakers": 41, "independent_episodes": 36, "threshold": 9, "tracked_podcasts": 162 }

{ "available": false, "reason": "not_yet_measured" | "not_yet_persisted" }

We reproduce that nesting exactly instead of flattening it into top-level nullable fields. The point is that a caller can tell "not computed" from "computed, and the answer is zero". Zero independent speakers is a strong claim about an entry; unavailable is no claim at all; a null reads as both, and next to a populated tier it reads as *"ignore this, trust the tier"*.

The two unavailable reasons are different claims and we never collapse them:

reasonwhat it meanshow often
not_yet_measuredthis entry is newer than the last nightly recomputeper-row, permanent by design — true of every entry added today
not_yet_persistedthe counts are not being stored at all right nowcorpus-wide, a real but temporary upstream deficiency

Render both as a generic "measurement unavailable" and a caller reads *broken* for something that is fine — manufacturing a false defect report about a healthy pipeline, immediately after we went to some length not to manufacture a false consensus count.

measured_at is load-bearing, not metadata. CanonCannon's bar is bidirectional: an entry can lose canon status without losing a single endorsement, purely because the corpus grew around it (the bar is ceil(5% of tracked_podcasts)). And per-row measured_at is the only thing that makes not_yet_measured detectable from outside the system at all.

threshold is never reported without tracked_podcasts. "9 of 162" is a claim; "9" alone is a number.

Integrity gate on canon_citations

CITATIONS_VERIFICATION_LANDED = false in src/index.ts keeps the tool out of the exported tools array, and callTool refuses it with the reason.

CanonCannon's extractor was using canon entries as filing labels, so an entry's own summary text could count as an endorsement of itself. canon_citations returns a consensus count — the shape a caller is least able to check — so publishing it over contaminated links would put a confident wrong number in front of every agent that calls it, under the Pipeworx name. A verification pass over 4,218 links is running upstream.

Before flipping the flag:

  1. Confirm the verification pass has completed. "The API is live" does not imply it — the pass is a separate pipeline job on its own schedule.
  2. Check rows come back verified: true. The endpoint carries the flag per row, so the gate is enforced upstream rather than by anyone remembering it.
  3. Do not hard-code the exclusion rule. Whether the fix changes the rule's *shape* or only its *inputs* was still open when this was written, so the tool reports the rule the API states, never the intended one.

Why every tool is canon_-prefixed

episode_get, person_get, podcast_list and corpus_stats were the names in CanonCannon's own API-PLAN.md §3, and they are clear across mcps/* and the live gateway today (checked 2026-09-14). They are also generic enough that the next podcast pack anyone builds — Listen Notes, Podcast Index, a transcript source — would want four of them.

That matters because of how the gateway resolves a bare tools/call: while a name is unique to one pack it is exposed bare, and the moment a second pack exports it BOTH become reachable only as _ . So a future pack would silently rename this pack's live tools, breaking its tool-examples.json keys and every caller that had learned the bare name. Nine central-bank packs all exporting exchange_rates is the measured precedent, and before it was swept a "Bank of Japan policy rate" question was answered with Israel's number.

The canon_ prefix costs nothing now and cannot be added later without a breaking rename. Re-run the check at promotion anyway — it is cheap:

for n in canon_search canon_get canon_citations canon_episode_search          canon_episode_get canon_person_get canon_podcast_list          canon_podcast_get canon_corpus_stats; do

grep -rl "name: '$n'" mcps/*/src/ | head -3 done scripts/pwcall.sh names canon_ # and against the live gateway

The name check now applies: the pack lives at mcps/podcast-parser/, which pnpm check:collisions and check:error-body-leak do glob. All nine canon_* names were confirmed unique across mcps/*/src at promotion.

Data sources

  • Canoncannon — the contract. Keyless; build tool schemas from this artifact, not from prose.
  • Canoncannon, /canon/{slug}, /canon/{slug}/citations, /episodes, /episodes/{slug}, /people/{slug}, /podcasts, /podcasts/{slug}, /stats — what the eight-plus-one tools wrap.

Specced upstream and deliberately not wrapped yet: GET /people (list), GET /search (cross-corpus), GET /changes?since= (cheap polling). Add tools when a caller asks for them; every tool needs a tool-examples.json entry recorded from a call that actually returned rows, and we cannot record one today.

Things the next person would otherwise rediscover

  • Cursor pagination, never offset. ?cursor= is keyset. Terminate on next_cursor: null or an empty page — *never* on a short one, because a short page is what silent truncation looks like. Their convention came from the same PostgREST 1,000-row cap that has bitten us; see docs/postgrest-row-cap.md. This pack makes one upstream request per tool call and hands the cursor back, so a caller can never be given a truncated list that looks complete.
  • We are the only consumer of `/api/v1` on the wire. CanonCannon's own pages render in-process (a Worker fetching its own zone re-enters the Worker), so their production traffic never exercises these routes. We will find the API's bugs. Treat the OpenAPI artifact as intent and the live endpoint as truth — which is why every response here can carry contract_warnings, and why those warnings ride out to the caller instead of being swallowed.
  • A contract bug there already survived twenty green assertions (canon_related has two foreign keys to canon, the embed was ambiguous, every detail request 500'd in production while every stubbed test passed). The detail endpoints have no declared response schema, which is why this pack passes their payloads through rather than hand-mapping fields nobody here has observed.
  • `citation_count` is not exposed and must not be reintroduced. It was a text column of model prose wearing a number's name.
  • No direct Supabase access, ever. The canon-cannon Supabase project (admbyodxaxsikiczgfjf) is a separate project; Pipeworx must never point a migration, an ingest or the data-pipeline worker at it. Going over HTTP is what makes us inherit the bar when it moves instead of drifting from it. Do not "optimise" this into a direct read, and do not ingest their corpus into a Pipeworx table.
  • Their `api_keys` table briefly shipped without RLS (anon-readable and anon-writable; caught and closed within the hour, independently re-probed). Recorded because the key we will hold is issued from that table.

Tests

src/index.test.ts — 25 assertions over fixtures taken from the published OpenAPI artifact. They prove our handling of the declared contract: the two unavailable reasons staying distinct, tier never passing bare, null being flagged rather than forwarded, a page count never presented as a total, the refusal saying *"requires an API key"* in those words.

They do not prove the live API returns these shapes — nothing here has made a live call. Replace the fixture payloads with recorded live ones when the key lands, before anyone calls this pack verified.

What promotion found (2026-09-14)

All eight exported tools were smoke-tested live against the real API before the gateway wiring landed, and two defects surfaced that only a live call could:

  1. **canon_corpus_stats told every caller the bar was

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx