# The Stochastic Parrot (remote · thestochasticparrot.com)

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

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `thestochasticparrot.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/portneymk-stochastic-parrot/api-mcp.md), [page](https://verifymcp.io/servers/portneymk-stochastic-parrot/api-mcp)

## Channel facts

- Endpoint: `https://thestochasticparrot.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1499 tokens (~99/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the The Stochastic Parrot MCP server?

The Stochastic Parrot is a hosted endpoint at https://thestochasticparrot.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.portneymk-stochastic-parrot]
url = "https://thestochasticparrot.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "portneymk-stochastic-parrot": {
      "type": "remote",
      "url": "https://thestochasticparrot.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add portneymk-stochastic-parrot --url 'https://thestochasticparrot.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  portneymk-stochastic-parrot:
    url: "https://thestochasticparrot.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "portneymk-stochastic-parrot": {
      "Transport": "http",
      "Url": "https://thestochasticparrot.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add portneymk-stochastic-parrot -t streamable-http -u 'https://thestochasticparrot.com/api/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 77, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (15)

### `search_corpus` (~121 tokens)

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.

Input parameters:

- `limit` (integer): Maximum results to return (default 25, hard cap 100).
- `query` (string, required): Search terms, e.g. 'McConnell hospital photo'. Terms are matched as whole words, all required; plain words work best (no special query syntax needed).

### `get_audit` (~86 tokens)

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.

Input parameters:

- `slug` (string, required): The piece's URL slug, e.g. 'mcconnell-proof-of-life-photo'.

### `list_audits` (~179 tokens)

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

Input parameters:

- `kind` (string): Only pieces of this kind: 'audit' (discrepancy audit), 'coverage' (coverage brief), 'dispatch', or 'solo' (solo audit).
- `limit` (integer): Maximum results to return (default 25, hard cap 100).
- `outlet` (string): Only pieces whose sources include this outlet, matched exactly but case-insensitively, e.g. 'Reuters' or 'Fox News'.
- `since` (string): Only pieces dated on or after this ISO date (YYYY-MM-DD).
- `until` (string): Only pieces dated on or before this ISO date (YYYY-MM-DD).

### `list_corrections` (~40 tokens)

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` (~78 tokens)

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

Input parameters:

- `chain_id` (string): A chain id from the no-argument listing. Omit to list all chains.

### `verify_piece` (~81 tokens)

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.

Input parameters:

- `slug` (string, required): The piece's URL slug, e.g. 'mcconnell-proof-of-life-photo'.

### `get_framing_index` (~56 tokens)

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` (~48 tokens)

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` (~90 tokens)

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.

Input parameters:

- `chain` (string, required): Chain slug, e.g. 'mcconnell' or 'fauci'.

### `get_storyboards` (~95 tokens)

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.

Input parameters:

- `chain` (string, required): Chain slug, e.g. 'fauci'.

### `list_letters` (~42 tokens)

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` (~55 tokens)

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.

Input parameters:

- `day` (string, required): The day, YYYY-MM-DD.

### `submit_letter` (~109 tokens)

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.

Input parameters:

- `from` (string): Initials or short byline, e.g. 'M.P.'.
- `key` (string, required): The reader key issued by the desk's operator.
- `text` (string, required): The letter (plain text, up to ~4000 chars).

### `report_error` (~99 tokens)

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.

Input parameters:

- `description` (string, required): What looks wrong, and where.
- `key` (string, required): The reader key issued by the desk's operator.
- `slug` (string): Slug of the piece, if known.

### `propose_development` (~110 tokens)

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.

Input parameters:

- `chain` (string): Chain slug, if the tip extends a chain.
- `key` (string, required): The reader key issued by the desk's operator.
- `tip` (string, required): The development, with a source if you have one.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/portneymk-stochastic-parrot/api-mcp#diagnostics

## Score history

- 2026-09-25: 77
- 2026-09-24: 77
- 2026-09-23: 76
- 2026-09-22: 76
- 2026-09-21: 75
- 2026-09-20: 75
- 2026-09-19: 74
- 2026-09-18: 74
- 2026-09-17: 73
- 2026-09-16: 73
- 2026-09-15: 72
- 2026-09-14: 72
- 2026-09-13: 71
- 2026-09-12: 71
- 2026-09-11: 71
- 2026-09-10: 70
- 2026-09-09: 70
- 2026-09-08: 69
- 2026-09-07: 69
- 2026-09-06: 68
- 2026-09-05: 68
- 2026-09-04: 67
- 2026-09-03: 67
- 2026-09-02: 66
- 2026-09-01: 66
- 2026-08-31: 65
- 2026-08-30: 65
- 2026-08-29: 64
- 2026-08-28: 64

## Common questions

### What is the The Stochastic Parrot MCP server?

The Stochastic Parrot is an MCP server listed in the public MCP registry as io.github.portneymk/stochastic-parrot. Span-grounded audits of how US outlets covered the same story, quotes checkable at the source. This page covers its hosted endpoint (https://thestochasticparrot.com/api/mcp).

### Is the The Stochastic Parrot MCP server safe to use?

The Stochastic Parrot scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the The Stochastic Parrot MCP server expose?

The Stochastic Parrot exposes 15 tools: search_corpus, get_audit, list_audits, list_corrections, get_chain, and 10 more. Their descriptions and schemas cost roughly 1,289 tokens of context every time the server is loaded.

### Does the The Stochastic Parrot MCP server require authentication?

No. We connected to The Stochastic Parrot without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the The Stochastic Parrot MCP server still maintained?

The Stochastic Parrot is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://thestochasticparrot.com/api/mcp
- Website: https://thestochasticparrot.com/connect/
- Changelog RSS feed: https://verifymcp.io/servers/portneymk-stochastic-parrot/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/portneymk-stochastic-parrot/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/portneymk-stochastic-parrot/api-mcp