sh.newsflash/newsflash
Measured conclusion: Deep-tested. L2 outcome: tools_ok.
Real-time corroborated news events + 5-year archive, for agents. Free tier, no key.
| Author | sh.newsflash |
|---|---|
| Access | remote |
| Publisher key required | No |
| Measured state | Deep-tested |
| L1 liveness | alive |
| L1 latency | 2921 ms |
| Last measured | 2026-10-26 |
Add to your agent
Copy this into your MCP client config:
{
"mcpServers": {
"newsflash": {
"url": "https://newsflash.sh/mcp",
"transport": "streamable-http"
}
}
}
Measured tools (5)
get_eventsread-onlyQuery the deduped news event graph by theme, source, category and time window. Returns events (many articles about one happening collapsed into one), each with a corroboration count and confidence score. This is the primary tool — prefer it over raw articles. For headlines, briefings, or 'what's happening' asks, pass min_sources: 2 (or 3 for high signal) — the raw recency feed is dominated by single-outlet local stories without it. ONE call is normally enough: trust each event's corroboration (distinct outlets), confidence (0-1; 1.0 = fully corroborated), and sources list as-is, and present the top events directly, including each event's url as its link — do NOT call get_event per item or re-verify counts (only drill in when the user wants EVERY outlet's link for one story). The corpus spans 260+ global outlets and a five-year archive (history visible depends on tier).
Parameters:
q— string — Free-text theme/keyword to match on headline + summaryto— string — Only events active on/before this date. ISO 8601 date/time, e.g. 2026-07-01 or 2026-07-01T00:00:00Zfrom— string — Only events active on/after this date. ISO 8601 date/time, e.g. 2026-07-01 or 2026-07-01T00:00:00Zlimit— integer — Max events (default 15)source— string — Source slug, e.g. 'coindesk' (see list_sources)category— string — Source categorysemantic— boolean — Rank by meaning (embedding similarity) instead of keyword match — requires q; better for concepts ('monetary easing') than exact stringsmin_sources— integer — Only events corroborated by at least this many distinct outlets — use 2-3 for briefings/headlines to skip single-source noise
Hints: read-only yes · destructive no · idempotent yes · open-world no
get_eventread-onlyFetch a single event by id, including every corroborating article (source, url, timestamp).
Parameters:
id(required) — integer — Event id from get_events
Hints: read-only yes · destructive no · idempotent yes · open-world no
search_articlesread-onlySearch raw articles (not collapsed into events). Use when you want the underlying items or need per-outlet coverage rather than deduped happenings.
Parameters:
q— string — Free-text keyword on headline + summaryto— string — ISO 8601 date/time, e.g. 2026-07-01 or 2026-07-01T00:00:00Zfrom— string — ISO 8601 date/time, e.g. 2026-07-01 or 2026-07-01T00:00:00Zlimit— integer — Max articles (default 25)source— string — Source slugcategory— string — Source category
Hints: read-only yes · destructive no · idempotent yes · open-world no
list_sourcesread-onlyList all news sources Newsflash tracks, with categories and live article counts.
Hints: read-only yes · destructive no · idempotent yes · open-world no
corpus_statsread-onlyCorpus size and freshness: source / article / event counts and the latest article timestamp.
Hints: read-only yes · destructive no · idempotent yes · open-world no
Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.