The Stochastic Parrot
REMOTE · THESTOCHASTICPARROT.COM · SCANNED SEP 25
Span-grounded audits of how US outlets covered the same story, quotes checkable at the source.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1499 tokens (~99/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · thestochasticparrot.com
claude mcp add --transport http portneymk-stochastic-parrot 'https://thestochasticparrot.com/api/mcp'
{
"mcpServers": {
"portneymk-stochastic-parrot": {
"url": "https://thestochasticparrot.com/api/mcp"
}
}
} {
"servers": {
"portneymk-stochastic-parrot": {
"type": "http",
"url": "https://thestochasticparrot.com/api/mcp"
}
}
} [mcp_servers.portneymk-stochastic-parrot] url = "https://thestochasticparrot.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"portneymk-stochastic-parrot": {
"type": "remote",
"url": "https://thestochasticparrot.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add portneymk-stochastic-parrot --url 'https://thestochasticparrot.com/api/mcp' --transport streamable-http
mcp_servers:
portneymk-stochastic-parrot:
url: "https://thestochasticparrot.com/api/mcp" {
"McpServers": {
"portneymk-stochastic-parrot": {
"Transport": "http",
"Url": "https://thestochasticparrot.com/api/mcp"
}
}
} assistant mcp add portneymk-stochastic-parrot -t streamable-http -u 'https://thestochasticparrot.com/api/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 11 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://thestochasticparrot.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=thestochasticparrot.com | CN=WE1,O=Google Trust Services,C=US | 15 Aug 2026 | 13 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | c7d1f971cd15adeb13466e178d35fd36 |
| SANs: thestochasticparrot.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of thestochasticparrot.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| thestochasticparrot.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://thestochasticparrot.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://thestochasticparrot.com/api/mcp | HTTPS enforced | 301 | https://thestochasticparrot.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_audit ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The piece's URL slug, e.g. 'mcconnell-proof-of-life-photo'. |
No output schema declared.
No examples provided.
get_boxscore ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| day | string | yes | The day, YYYY-MM-DD. |
No output schema declared.
No examples provided.
get_chain ~78
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).
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | – | A chain id from the no-argument listing. Omit to list all chains. |
No output schema declared.
No examples provided.
get_claim_ledger ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain slug, e.g. 'mcconnell' or 'fauci'. |
No output schema declared.
No examples provided.
get_coverage_record ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_framing_index ~56
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_storyboards ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain slug, e.g. 'fauci'. |
No output schema declared.
No examples provided.
list_audits ~179
List published pieces (summaries: slug, title, kind, date, counts of hard contradictions and naming/framing splits), newest first. All filters optional and combinable.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
list_corrections ~40
The desk's public corrections ledger: every logged error on a published piece — what was wrong, what changed, and when — in original ledger order.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_letters ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
propose_development ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Chain slug, if the tip extends a chain. |
| key | string | yes | The reader key issued by the desk's operator. |
| tip | string | yes | The development, with a source if you have one. |
No output schema declared.
No examples provided.
report_error ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What looks wrong, and where. |
| key | string | yes | The reader key issued by the desk's operator. |
| slug | string | – | Slug of the piece, if known. |
No output schema declared.
No examples provided.
search_corpus ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results to return (default 25, hard cap 100). |
| 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). |
No output schema declared.
No examples provided.
submit_letter ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Initials or short byline, e.g. 'M.P.'. |
| key | string | yes | The reader key issued by the desk's operator. |
| text | string | yes | The letter (plain text, up to ~4000 chars). |
No output schema declared.
No examples provided.
verify_piece ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The piece's URL slug, e.g. 'mcconnell-proof-of-life-photo'. |
No output schema declared.
No examples provided.
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.