The Stochastic Parrot

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

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

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

    How to connect

    How to connect The Stochastic Parrot to Claude

    The server address to paste into Claude settings:

    https://thestochasticparrot.com/api/mcp

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect The Stochastic Parrot to ChatGPT

    The server address to paste into ChatGPT settings:

    https://thestochasticparrot.com/api/mcp

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect The Stochastic Parrot to Cursor

    The server address to paste into Cursor settings:

    https://thestochasticparrot.com/api/mcp

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (15)

    Raw names from tools/list. Only developers need these.

    search_corpusFull-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_auditFetch 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_auditsList published pieces (summaries: slug, title, kind, date, counts of hard contradictions and naming/framing splits), newest first. All filters optional and combinable.
    list_correctionsThe desk's public corrections ledger: every logged error on a published piece — what was wrong, what changed, and when — in original ledger order.
    get_chainStory 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_pieceProvenance 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_indexThe 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_recordThe 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_ledgerA 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_storyboardsA 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_lettersLetters 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_boxscoreThe 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_letterSubmit 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_errorReport 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_developmentTip 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.