78trust / 100

The Stochastic Parrot

by thestochasticparrot.com in Security & trust

MCP serverPassing, checked 7 h ago

Span-grounded audits of how US outlets covered the same story, quotes checkable at the source.

https://thestochasticparrot.com/api/mcp
Tools
16
open to any client
Uptime
100%
last 30 days
Response time
332 ms
510 ms slowest 5%
Last check
Passed
7 h ago, next any minute now

Scan it nowHow to connect

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "the-stochastic-parrot": {
      "type": "http",
      "url": "https://thestochasticparrot.com/api/mcp"
    }
  }
}

16 tools

  • whats_new

    The desk's change window: the 20 most recently published pieces, newest first, with the desk's own dek, its computed split counts, and the story-chain ids each piece belongs to. This is the cheap 'what moved since I last looked' call — a few KB, not the multi-megabyte /feed.json…

  • search_corpus

    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.

  • get_audit

    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.

  • list_audits

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

  • list_corrections

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

  • get_chain

    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).

  • verify_piece

    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.

  • get_framing_index

    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_coverage_record

    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_claim_ledger

    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_storyboards

    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…

  • list_letters

    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.

  • get_boxscore

    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.

  • submit_letter

    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.

  • report_error

    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.

  • propose_development

    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.

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
7 h agoPassed200328 ms
18 h agoPassed200328 ms
32 h agoPassed200408 ms
2 days agoPassed200305 ms
3 days agoPassed200326 ms
Show 10 older checks
3 days agoPassed200419 ms
4 days agoPassed200302 ms
4 days agoPassed200360 ms
5 days agoPassed200350 ms
5 days agoPassed200309 ms
6 days agoPassed200344 ms
6 days agoPassed200316 ms
7 days agoPassed200271 ms
8 days agoPassed200338 ms
8 days agoPassed200338 ms