Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Nothing to run from here
The Stochastic Parrot is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
19
tools declared
remote
at its publisher
—
calls last 7d
What it does
Span-grounded audits of how US outlets covered the same story, quotes checkable at the source.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http the-stochastic-parrot-mcp https://thestochasticparrot.com/api/mcp
# 2 — ask your agent for something these tools do
# editor_pending, editor_decide, editor_log and 16 more
The Stochastic Parrot costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
POAll 1 server
portneymk1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http the-stochastic-parrot-mcp https://thestochasticparrot.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
19 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
The site editor's pitch cards waiting for Mike's decision. Each card is one proposed change to thestochasticparrot.com that the editor judged too big to make on its own. Returns the cards; the attached widget lets the user decide each with Approve / Hold / Kill. Requires the editor key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | no | The editor key, only if the connector does not send it as a bearer header. |
Record Mike's decision on one editor card: approve (the editor executes it next cycle), hold (keep it, not now), or kill (never pitch it again). Only call this when the user has explicitly decided; never infer a decision. Requires the editor key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | no | — |
| id | string | yes | Card id, e.g. E-20261003-1425-retire-boomer |
| decision | string | yes | — |
| note | string | no | Optional one-line reason from the user. |
What the site editor did recently: its ledger of small changes it shipped on its own, cards it filed, and decisions recorded. Use to answer 'what did the editor change'. Requires the editor key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | no | — |
| n | integer | no | — |
Internal: the desk's mirror sync (push cards + ledger, read back all cards, clear ids). Not for conversational use.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | no | — |
| cards | array | no | — |
| ledger | array | no | — |
| clear | array | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search terms, e.g. 'McConnell hospital photo'. Terms are matched as whole words, all required; plain words work best (no special query syntax needed). |
| limit | integer | no | Maximum results to return (default 25, hard cap 100). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The piece's URL slug, e.g. 'mcconnell-proof-of-life-photo'. |
List published pieces (summaries: slug, title, kind, date, counts of hard contradictions and naming/framing splits), newest first. All filters optional and combinable.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| outlet | string | no | Only pieces whose sources include this outlet, matched exactly but case-insensitively, e.g. 'Reuters' or 'Fox News'. |
| kind | string | no | Only pieces of this kind: 'audit' (discrepancy audit), 'coverage' (coverage brief), 'dispatch', or 'solo' (solo audit). |
| since | string | no | Only pieces dated on or after this ISO date (YYYY-MM-DD). |
| until | string | no | Only pieces dated on or before this ISO date (YYYY-MM-DD). |
| limit | integer | no | Maximum results to return (default 25, hard cap 100). |
The desk's public corrections ledger: every logged error on a published piece — what was wrong, what changed, and when — in original ledger order.
No parameter schema on file.
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain_id | string | no | A chain id from the no-argument listing. Omit to list all chains. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The piece's URL slug, e.g. 'mcconnell-proof-of-life-photo'. |
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | yes | Chain slug, e.g. 'mcconnell' or 'fauci'. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | yes | Chain slug, e.g. 'fauci'. |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| day | string | yes | The day, YYYY-MM-DD. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The letter (plain text, up to ~4000 chars). |
| from | string | no | Initials or short byline, e.g. 'M.P.'. |
| key | string | yes | The reader key issued by the desk's operator. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | Slug of the piece, if known. |
| description | string | yes | What looks wrong, and where. |
| key | string | yes | The reader key issued by the desk's operator. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | no | Chain slug, if the tip extends a chain. |
| tip | string | yes | The development, with a source if you have one. |
| key | string | yes | The reader key issued by the desk's operator. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install The Stochastic Parrot or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.1.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest4fa6562b6df7c4729e62c12b33eff3371477d9def0d0b14e16aaa9f40566e12a
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| editor_pending | no tags | |
| editor_decide | no tags | |
| editor_log | no tags | |
| editor_sync | no tags | |
| search_corpus | no tags | |
| get_audit | untrusted-input | untrusted-input: keyword "fetch" |
| list_audits | no tags | |
| list_corrections | no tags | |
| get_chain | no tags | |
| verify_piece | no tags | |
| get_framing_index | no tags | |
| get_coverage_record | no tags | |
| get_claim_ledger | no tags | |
| get_storyboards | no tags | |
| list_letters | no tags | |
| get_boxscore | no tags | |
| submit_letter | no tags | |
| report_error | no tags | |
| propose_development | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest4fa6562b6df7c472
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish The Stochastic Parrot can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.