Pure Report — Neutral News
REMOTE · PURE.REPORT · SCANNED AUG 3
Neutral, bias-scored news for AI agents: compare left/right media-bias framing, fact-check receipts.
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 →
Endpoint Security63
- 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 7 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
- 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1316 tokens (~164/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 Management27
- Stability observed for 8 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · pure.report
claude mcp add --transport http report-pure-news https://pure.report/mcp
[mcp_servers.report-pure-news] url = "https://pure.report/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"report-pure-news": {
"type": "remote",
"url": "https://pure.report/mcp",
"enabled": true
}
}
} openclaw mcp add report-pure-news --url https://pure.report/mcp --transport streamable-http
mcp_servers:
report-pure-news:
url: "https://pure.report/mcp" {
"mcpServers": {
"report-pure-news": {
"type": "http",
"url": "https://pure.report/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.
- 3 Aug 26 0
- Schema quality: 135 → 164 ▼ functional
- “submit_feedback” added an optional parameter “category” cosmetic
- “about_pure_report” added an optional parameter “event_slug” cosmetic
- “about_pure_report” added an optional parameter “report_body” cosmetic
- “about_pure_report” added an optional parameter “report_kind” cosmetic
- “about_pure_report” added an optional parameter “report_subject” cosmetic
- “search_news” added an optional parameter “offset” cosmetic
- “search_news” added an optional parameter “published_after” cosmetic
- “search_news” added an optional parameter “published_before” cosmetic
- “about_pure_report” added an optional parameter “article_id” cosmetic
- “submit_feedback” reworded the description of “body” cosmetic
- “submit_feedback” reworded the description of “kind” cosmetic
- “submit_feedback” made “kind” optional cosmetic
- 2 Aug 26 0
- Schema quality: 122 → 135 ▼ functional
- New tool “submit_feedback” functional
- New tool “check_feedback” functional
- “search_news” reworded the description of “limit” cosmetic
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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 Jul 26 65
First indexed and scored.
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 3 Aug 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 | 24 Jul 2026 | 22 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 55cebd31af336edfdc30458743038b505a4 |
| 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 |
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=() |
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.
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 ~60
Fetch one article by id: neutral rewritten title + body, a bias_score for the ORIGINAL source (not the rewrite), 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 ~110
Get the full neutral writeup of one news event by slug: a verification-gated account (lede, what-we-know bullets with verbatim source receipts, single-source attributed items) plus a coverage census (how many outlets by political lean, earliest report). If no gated account exists yet, the coverage census is still 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 | — | — |
| name | string|null | — | — |
| slug | string | yes | — |
| status | string|null | — | — |
| url | string | yes | — |
No examples provided.
search_news Search neutral news ~292
Search Pure Report's neutral, bias-scored news. Returns articles rewritten to remove loaded language; bias_score (0-100) rates the ORIGINAL source reporting before neutralization (0 = wire-neutral, 100 = advocacy), NOT the returned rewrite, 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 ~90
List the news events with the most current coverage activity. Each event clusters many outlets' articles about one story and includes has_account (boolean): true means get_event returns a full verification-gated writeup, false means only the coverage census is available yet. 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.