Pure Report — Neutral News
REMOTE · PURE.REPORT
Neutral, bias-scored news for AI agents: compare left/right media-bias framing, fact-check receipts.
Available components
Last scanned (3 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category News and Social
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1417 tokens (~177/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_article” rewrote its description, which is the text the model reads security
- Tool “search_news” rewrote its description, which is the text the model reads security
- 10 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_event” rewrote its description, which is the text the model reads security
- Tool “trending_events” rewrote its description, which is the text the model reads security
- 28 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
- 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
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
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 5 Nov 2026 · Probed https://pure.report/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pure.report | CN=YE1,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5792cf26a478d62f5f80552e1a272e782cf |
| SANs: pure.report | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pure.report. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| report. | present | 23221 | 8 | Verified |
| pure.report. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://unpkg.com https://cdn.jsdelivr.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https:; connect-src 'self' https://api.polygon.io; frame-ancestors 'self'; form-action 'self'; base-uri 'self'; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pure.report/mcp | Verified | 200 | |
| http (plaintext) | http://pure.report/mcp | HTTPS enforced | 301 | https://pure.report/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 →
about_pure_report About & methodology ~153
How Pure Report works — the bias scale, neutralization method, the two-gate verification for event accounts, lean labeling, coverage scope (topic list), and the support contact. Call this to cite the source or explain its methodology to a user.
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | integer | – | Optional context for the report. |
| event_slug | string | – | Optional context for the report. |
| report_body | string | – | Optional. The detail needed to act. |
| report_kind | string | – | Optional, defaults to bug. |
| report_subject | string | – | Optional. Providing this (with report_body) files feedback and returns a ref under "filed" — use only if submit_feedback is missing from your tools. |
| Name | Type | Req | Description |
|---|---|---|---|
| bias_scale | string | yes | – |
| coverage_scope | object | – | – |
| filed | object|null | – | – |
| freshness | string | – | – |
| lean_labeling | string | – | – |
| name | string | – | – |
| neutralization | string | – | – |
| reporting_problems | string | – | – |
| reporting_problems_if_submit_feedback_is_missing | string | – | – |
| support | string | yes | – |
| verification_gate | string | – | – |
| website | string | – | – |
| what_it_is | string | – | – |
No examples provided.
check_feedback Check a feedback reply ~106
Look up feedback you filed with submit_feedback, using the ref it returned (e.g. PR-7F3K2Q). Returns the current status (open, answered, closed) and the operator's reply once one exists. Replies are written by a human and are not immediate — poll sparingly, on the order of hours or days, not seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | yes | The ref from submit_feedback, e.g. 'PR-7F3K2Q'. |
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| message | string | – | – |
| ref | string | yes | – |
| replied_at | string|null | – | – |
| reply | string|null | – | – |
| status | string | yes | – |
| subject | string | – | – |
| submitted_at | string|null | – | – |
No examples provided.
compare_coverage Compare outlet framing ~81
Show how outlets across the political spectrum framed one event: a per-outlet bias-score spectrum and, where they editorialized, the verbatim framing quotes grouped by left/center/right. The core 'compare the coverage' view — use it to detect slant and consensus.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Event slug from trending_events or a search_news result. |
| Name | Type | Req | Description |
|---|---|---|---|
| framing_spectrum | object|null | – | – |
| how_each_side_framed_it | object|null | – | – |
| name | string|null | – | – |
| slug | string | yes | – |
| url | string | yes | – |
No examples provided.
get_article Get article ~75
Fetch one article by id: neutral title + short summary with key facts (null for older articles), source_url for the full story, a bias_score for the ORIGINAL source (not the summary), source, extracted entities, and the events it belongs to.
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | integer | yes | Numeric article id (from search_news results). |
| Name | Type | Req | Description |
|---|---|---|---|
| bias_score | number|null | – | – |
| content | string|null | – | – |
| entities | object|array|null | – | – |
| events | array | – | – |
| id | integer | yes | – |
| published_at | string|null | – | – |
| source_name | string|null | – | – |
| source_url | string|null | – | – |
| summary | string|null | – | – |
| title | string|null | – | – |
| url | string | yes | – |
No examples provided.
get_event Neutral event writeup ~144
Get the full neutral writeup of one news event by slug: 'story', Pure Report's own neutral news story (headline + paragraphs, written from the outlets' reports and checked before publishing); 'account', a sentence-cited breakdown (lede, what-we-know bullets with verbatim source receipts, single-source attributed items) when one passed its gates; and a coverage census (how many outlets by political lean, earliest report). Either writeup may be null; the census is always returned.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Event slug from trending_events or a search_news result, e.g. "tyler-robinson-trial-for-charlie-kirk-murder". |
| Name | Type | Req | Description |
|---|---|---|---|
| account | object|null | – | – |
| account_note | string|null | – | – |
| article_count | integer|null | – | – |
| coverage | object | yes | – |
| coverage_report | object|null | – | – |
| first_seen | string|null | – | – |
| headline | string|null | – | – |
| name | string|null | – | – |
| slug | string | yes | – |
| status | string|null | – | – |
| story | object|null | – | – |
| url | string | yes | – |
No examples provided.
search_news Search neutral news ~291
Search Pure Report's neutral, bias-scored news. Returns articles with neutral summaries in our own words; bias_score (0-100) rates the ORIGINAL source reporting (0 = wire-neutral, 100 = advocacy), NOT the returned summary, which is neutral by design. Each result also lists the event(s) it belongs to — pass an event slug to get_event for the neutral writeup or compare_coverage for cross-outlet framing. Ranked by relevance and recency.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results to RETURN, 1-40 (default 15). Does not affect total_matches, which always reports how many articles matched. |
| offset | integer | – | Skip this many matches — page through results beyond the 40-row limit. The response echoes offset/returned/next_offset; next_offset is null on the last page. |
| published_after | string | – | Only articles published on/after this date. 'YYYY-MM-DD' or full ISO. Use with published_before to bound a period, e.g. coverage during June. |
| published_before | string | – | Only articles published on/before this date. 'YYYY-MM-DD' or full ISO. |
| query | string | yes | Keywords or phrase, e.g. "Iran sanctions" or "2026 election". |
| topic | string | – | Optional topic-slug filter. An unrecognized value searches all topics and returns a warning. |
| Name | Type | Req | Description |
|---|---|---|---|
| applied_topic | string|null | – | – |
| next_offset | integer|null | – | – |
| offset | integer | – | – |
| query | string | yes | – |
| result_composition | object | – | Factual description of what the returned set is ABOUT. Search is lexical, so every query term appears in every result; this reports whether a term is the SUBJECT (title/entities/lede) or only a body… |
| results | array | yes | – |
| returned | integer | – | – |
| total_matches | integer | yes | TOTAL articles matching the query, independent of `limit` — not the number returned. len(results) < total_matches means more exist. |
| warning | string | – | – |
No examples provided.
submit_feedback Send feedback to the operator ~263
Report a problem or request to Pure Report's operator and get a tracking ref back. Use this when the data looks wrong — a bias score or outlet lean that doesn't match the source, an event cluster mixing unrelated stories, a missing neutral writeup, a broken article — or to ask a methodology question or request a capability. Include the article_id or event_slug you were looking at; that context is what makes a report actionable. A human reads these: replies take time and are not guaranteed. Call check_feedback with the returned ref to read the reply.
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | integer | – | Optional article the report concerns. |
| body | string | yes | The detail needed to act: what you expected, what you got, and how to reproduce it. Max 12000 chars. |
| category | string | – | bug = broken or erroring; dx = developer-experience friction; data_error = wrong/miscategorised data; data_gap = missing coverage or field; feature = a capability request; question = methodology or u… |
| event_slug | string | – | Optional event slug the report concerns. |
| kind | string | – | DEPRECATED alias for category; still accepted. |
| subject | string | yes | One line, max 200 chars. |
| Name | Type | Req | Description |
|---|---|---|---|
| how_to_check | string | – | – |
| message | string | – | – |
| ref | string | yes | – |
| status | string | yes | – |
No examples provided.
trending_events Trending news events ~106
List the news events with the most current coverage activity. Each event clusters many outlets' articles about one story and includes headline (the published story's headline, else the event name), has_story (get_event returns Pure Report's neutral news story) and has_account (get_event also returns a sentence-cited account with verbatim receipts). Returns slugs to pass to get_event / compare_coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max events, 1-25 (default 10). |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | – |
No examples provided.
How do I install the Pure Report — Neutral News MCP server?
Pure Report — Neutral News is a hosted endpoint at https://pure.report/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 · pure.report
claude mcp add --transport http report-pure-news 'https://pure.report/mcp'
What is the Pure Report — Neutral News MCP server?
Pure Report — Neutral News is an MCP server listed in the public MCP registry as report.pure/news. Neutral, bias-scored news for AI agents: compare left/right media-bias framing, fact-check receipts. This page covers its hosted endpoint (https://pure.report/mcp).
Is the Pure Report — Neutral News MCP server safe to use?
Pure Report — Neutral News scores 86 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 Pure Report — Neutral News MCP server expose?
Pure Report — Neutral News exposes 8 tools: search_news, trending_events, get_event, compare_coverage, get_article, and 3 more. Their descriptions and schemas cost roughly 1,219 tokens of context every time the server is loaded.
Does the Pure Report — Neutral News MCP server require authentication?
No. We connected to Pure Report — Neutral News without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pure Report — Neutral News MCP server still maintained?
Pure Report — Neutral News is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.