Queued from get_server miss — agent explicitly requested this URL
Queued from get_server miss — agent explicitly requested this URL
active Production-safe Score 92/100 http no auth
At a glance
| Endpoint | https://pure.report/mcp |
|---|---|
| Transport | http |
| Tools | 8 |
| Auth | none |
| First seen | 2026-08-01 14:18:58 |
| Last checked | 2026-11-17 21:48:25 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 557 / 1883 ms |
| Last successful check | 2026-11-17 21:48:25 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (8)
search_news— Search Pure Report's neutral, bias-scored news. Returns articles with neutral summaries in our own words; bias_score (0-100) rates the ORIGItrending_events— List the news events with the most current coverage activity. Each event clusters many outlets' articles about one story and includes headliget_event— Get the full neutral writeup of one news event by slug: 'story', Pure Report's own neutral news story (headline + paragraphs, written from tcompare_coverage— Show how outlets across the political spectrum framed one event: a per-outlet bias-score spectrum and, where they editorialized, the verbatiget_article— Fetch one article by id: neutral title + short summary with key facts (null for older articles), source_url for the full story, a bias_scoreabout_pure_report— How Pure Report works — the bias scale, neutralization method, the two-gate verification for event accounts, lean labeling, coverage scope (submit_feedback— 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 outlcheck_feedback— Look up feedback you filed with submit_feedback, using the ref it returned (e.g. PR-7F3K2Q). Returns the current status (open, answered, clo
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:48:25 | ✓ | ✓ | 286 ms | 94 | active |
| 2026-11-17 21:33:19 | ✓ | ✓ | 611 ms | 90 | active |
| 2026-11-17 21:18:11 | ✓ | ✓ | 406 ms | 90 | active |
| 2026-11-17 21:03:08 | ✓ | ✓ | 323 ms | 90 | active |
| 2026-11-17 20:47:46 | ✓ | ✓ | 412 ms | 90 | active |
| 2026-11-17 20:32:41 | ✓ | ✓ | 420 ms | 90 | active |
| 2026-11-17 20:17:38 | ✓ | ✓ | 526 ms | 90 | active |
| 2026-11-17 20:02:04 | ✓ | ✓ | 492 ms | 90 | active |
| 2026-11-17 19:46:43 | ✓ | ✓ | 510 ms | 90 | active |
| 2026-11-17 19:31:39 | ✓ | ✓ | 282 ms | 94 | active |
| 2026-11-17 19:16:34 | ✓ | ✓ | 498 ms | 90 | active |
| 2026-11-17 19:00:54 | ✓ | ✓ | 599 ms | 90 | active |
| 2026-11-17 18:45:52 | ✓ | ✓ | 419 ms | 90 | active |
| 2026-11-17 18:30:50 | ✓ | ✓ | 333 ms | 90 | active |
| 2026-11-17 18:15:46 | ✓ | ✓ | 468 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://pure.report/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/pure-report-mcp # JSON