# Portneymk Stochastic Parrot MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.portneymk%2Fstochastic-parrot
Registry id: `mcp-registry/io.github.portneymk/stochastic-parrot`
Status: live (checked 2026-10-27T03:38:43.118Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 5013
- Outages (90 days): 2

## Install

```json
{
  "mcpServers": {
    "portneymk-stochastic-parrot-mcp-server": {
      "type": "http",
      "url": "https://thestochasticparrot.com/api/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http portneymk-stochastic-parrot-mcp-server https://thestochasticparrot.com/api/mcp
```

## Tools (16)

- `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
- `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.
- `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
- `get_claim_ledger`: A story chain's claim ledger: specific verbatim claims outlets made, each tracked through states (open, corroborated, contradicted, corrected, quietly_abandoned
- `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 mea
- `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, mont
- `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
- `list_audits`: List published pieces (summaries: slug, title, kind, date, counts of hard contradictions and naming/framing splits), newest first. All filters optional and comb
- `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.
- `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.
- `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 
- `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 correc
- `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, an
- `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
- `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 U
- `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 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.