The Stochastic Parrot MCP server

• get_auditFree

  Fetch one piece's full detail JSON by slug: headline, kind, date, context, dek, outlets, verified contradictions with verbatim spans, naming/framing splits, and the full source list. Slugs come from search_corpus or list_audits.

• get_boxscoreFree

  The Daily Box Score for one day — the desk's frozen per-day stat snapshot. Requires the day; days are listed at /boxscore/ on the site.

• get_chainFree

  Story chains: multi-piece storylines the desk has covered more than once. Call without arguments to list the available chain ids; pass chain_id for one chain in full (its pieces in order, claim ledger, and reopen conditions).

• get_claim_ledgerFree

  A story chain's claim ledger: specific verbatim claims outlets made, each tracked through states (open, corroborated, contradicted, corrected, quietly_abandoned, resolved) with a receipt for every transition. Empty claims list = the desk has not logged claims for that chain yet.

• get_coverage_recordFree

  The capture-coverage record: what the desk's observatory actually monitored and when, including gaps. Read this before treating any silence in the corpus as meaningful — the desk's own rule.

• get_framing_indexFree

  The Framing Index: across the cross-outlet corpus, how often disagreements between outlets are hard contradictions vs naming/framing splits — totals, rate, monthly trend, per-outlet appearances. The desk's core longitudinal measurement.

• get_storyboardsFree

  A chain's per-newsroom storyboards: for each outlet, every piece it filed on the story entry-by-entry, the desk's published READ of what each piece was built to do (objective label, motive with its mandatory innocent read, confidence), the label arc, and the desk's 'story, as built' synthesis where one exists.

• list_auditsFree

  List published pieces (summaries: slug, title, kind, date, counts of hard contradictions and naming/framing splits), newest first. All filters optional and combinable.

• list_correctionsFree

  The desk's public corrections ledger: every logged error on a published piece — what was wrong, what changed, and when — in original ledger order.

• list_lettersFree

  Letters to the Desk: reader mail, excerpted and initialed, with the desk's replies in its own voice. The desk's only interactive surface with its readership.

• propose_developmentFree

  Tip the desk that a story moved — a development on an existing chain or a story worth auditing. Lands in the same proposed-developments queue the observatory's triggers feed; the desk decides what, if anything, to file. Requires the reader key.

• report_errorFree

  Report a suspected error in a published piece (a miscount, a quote that reads wrong, a broken claim). Verified catches are fixed and logged on the public corrections ledger, credited 'Caught by a reader.' Requires the reader key.

• search_corpusFree

  Full-text search over every published piece (titles, deks, context lines, outlet names, and source headlines). Returns matching pieces with slug, title, URL, and a highlighted snippet, best matches first. Use the slug with get_audit for full detail.

• submit_letterwrite actionFree

  Submit a letter to the desk. If the desk answers, the exchange may be published on the Letters page (excerpted, initialed) — through the desk's normal editorial process, never directly. Requires the reader key.

• verify_pieceFree

  Provenance record for one piece: SHA-256 hashes of its canonical JSON and published HTML as of the last corpus sync. Re-hash the live artifacts at the piece's URL and compare to confirm what you read is what the desk published.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1531ms20/20
• Tool poisoning15 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
• Maintenanceno repository listed3/15
• Maintainer identityno repository or website to verify2/10

The Stochastic Parrot: common questions

Is The Stochastic Parrot MCP server safe?

With care: it is graded C, so read the findings first (57/100). Read the The Stochastic Parrot safety report

How do I install The Stochastic Parrot?

It runs remotely at thestochasticparrot.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does The Stochastic Parrot need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is The Stochastic Parrot maintained?

The latest release is v1.1.0.

Is The Stochastic Parrot up?

100% of our last 19 checks got an answer. We check remote servers about four times a day.

What can I use instead of The Stochastic Parrot?

Servers from other publishers that do the same job: QVeris MCP server.