The Stochastic Parrot MCP server
io.github.portneymk/stochastic-parrotportneymkstreamable-httpv1.1.0Scanned
Span-grounded audits of how US outlets covered the same story, quotes checkable at the source.
16 tools: 1 do something that can't be undone, 5 change things and 10 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the The Stochastic Parrot MCP server can do
The The Stochastic Parrot MCP server is published by the GitHub account portneymk. It has 16 tools. It can do things that cannot be undone, such as sending, paying or publishing (get_coverage_record) and create or change data (5 tools: whats_new, verify_piece, submit_letter, report_error and 1 more), but cannot delete data. 10 tools only read.
1 tool reads private data (list_letters); 1 tool brings in text other people can write (list_letters).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 21, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
16 tools
Can't be undone 1Claude Code: ask
get_coverage_recordThe capture-coverage record: what the desk's observatory actually monitored and when, including gaps.No findings
Why it is in this group
- The name "get_coverage_record" says "get": a word for reading.
- The description's first verb is "capture": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
Changes things 5Claude Code: ask
propose_developmentTip the desk that a story moved — a development on an existing chain or a story worth auditing.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
report_errorReport a suspected error in a published piece (a miscount, a quote that reads wrong, a broken claim).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
submit_letterSubmit a letter to the desk.No findings
Why it is in this group
- The name "submit_letter" says "submit": a word for a change.
Description, as the server wrote it 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.
verify_pieceProvenance record for one piece: SHA-256 hashes of its canonical JSON and published HTML as of the last corpus sync.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
whats_newThe 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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 — so a scheduled agent can poll it safely. Filter by date, kind, or chain. For anything older than the window, use list_audits with a date range.
Only reads 10Show 10 read-only tools
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 lis…No findings
Why it is in this group
- The name "get_audit" says "get": a word for reading.
Description, as the server wrote it 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.
get_boxscoreThe Daily Box Score for one day — the desk's frozen per-day stat snapshot.No findings
Why it is in this group
- The name "get_boxscore" says "get": a word for reading.
Description, as the server wrote it 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_chainStory chains: multi-piece storylines the desk has covered more than once.No findings
Why it is in this group
- The name "get_chain" says "get": a word for reading.
Description, as the server wrote it 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).
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 r…No findings
Why it is in this group
- The name "get_claim_ledger" says "get": a word for reading.
Description, as the server wrote it 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_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-outle…No findings
Why it is in this group
- The name "get_framing_index" says "get": a word for reading.
Description, as the server wrote it 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_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…No findings
Why it is in this group
- The name "get_storyboards" says "get": a word for reading.
Description, as the server wrote it 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.
list_auditsList published pieces (summaries: slug, title, kind, date, counts of hard contradictions and naming/framing splits), newest first.No findings
Why it is in this group
- The name "list_audits" says "list": a word for reading.
Description, as the server wrote it List 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.No findings
Why it is in this group
- The name "list_corrections" says "list": a word for reading.
Description, as the server wrote it 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_lettersLetters to the Desk: reader mail, excerpted and initialed, with the desk's replies in its own voice.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "list_letters" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "mail": it reads mail.
- untrusted-inputThe description's first sentence says "mail": it reads inbound email, which other people can write.
Description, as the server wrote it 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.
search_corpusFull-text search over every published piece (titles, deks, context lines, outlet names, and source headlines).No findings
Why it is in this group
- The name "search_corpus" says "search": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:09 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://thestochasticparrot.com/api/mcp: tools/list returned 16 tools to an anonymous client, including get_coverage_record (irreversible), whats_new (write), verify_piece (write), submit_letter (write), report_error (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added, 4 removed.+1 added−4 removedView diff
- Added:whats_newChanges things
- Removed:editor_decide
- Removed:editor_log
- Removed:editor_pending
- Removed:editor_sync
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http stochastic-parrot https://thestochasticparrot.com/api/mcpclaude mcp add --transport http stochastic-parrot https://thestochasticparrot.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__stochastic-parrot__search_corpus",
"mcp__stochastic-parrot__get_audit",
"mcp__stochastic-parrot__list_audits",
"mcp__stochastic-parrot__list_corrections",
"mcp__stochastic-parrot__get_chain",
"mcp__stochastic-parrot__get_framing_index",
"mcp__stochastic-parrot__get_claim_ledger",
"mcp__stochastic-parrot__get_storyboards",
"mcp__stochastic-parrot__list_letters",
"mcp__stochastic-parrot__get_boxscore"
],
"ask": [
"mcp__stochastic-parrot__whats_new",
"mcp__stochastic-parrot__verify_piece",
"mcp__stochastic-parrot__get_coverage_record",
"mcp__stochastic-parrot__submit_letter",
"mcp__stochastic-parrot__report_error",
"mcp__stochastic-parrot__propose_development"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as stochastic-parrot. Review it before you use it.
Capability tags behind 1 rule
- mcp__stochastic-parrot__list_letters private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.portneymk/stochastic-parrot/verify?hash=78190415dc95fec80673dfda7785c886d5b6052e7d81a7d19ee5c658e3664dc2" | jq -e '.changed == false'Pinned hash 78190415dc95, from Nov 21, 2026, 02:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.portneymk/stochastic-parrot/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.portneymk/stochastic-parrot)Source: MCP Registry. Synced Oct 21, 2026, 18:45 UTC.
The Stochastic Parrot MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the The Stochastic Parrot MCP server safe?
- No scan can promise that. What its definitions show: 16 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the The Stochastic Parrot MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the The Stochastic Parrot MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: get_coverage_record.
What tools does the The Stochastic Parrot MCP server have?
- 16 tools: 1 irreversible, 5 write, 10 read. get_coverage_record, whats_new, verify_piece, submit_letter, report_error, propose_development, search_corpus, get_audit and 8 more.
Does the The Stochastic Parrot MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the The Stochastic Parrot MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the The Stochastic Parrot MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 6, 2026. Every change is on this page and in its Atom feed.