newsflash

endpoint

https://newsflash.sh/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is newsflash live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is newsflash free to use?

Yes — the hub reached it with no key and no payment.

What tools does newsflash have?

5 tools: get_event, list_sources, corpus_stats, get_events, search_articles.

Is newsflash safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• list_sources reads open 1h ago

  List all news sources Newsflash tracks, with categories and live article counts.

  mcp-tool

  12345

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  }

  arguments 5 lines copy
• corpus_stats reads open 10h ago

  Corpus size and freshness: source / article / event counts and the latest article timestamp.

  mcp-tool

  12345

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  }

  arguments 5 lines copy
• get_events reads open 10h ago

  Query 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).

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "q": {
        "type": "string",
        "description": "Free-text theme/keyword to match on headline + summary"
      },
      "to": {
        "type": "string",
        "description": "Only events active on/before this date. ISO 8601 date/time, e.g. 2026-07-01 or 2026-07-01T00:00:00Z"
      },
      "from": {
        "type": "string",
        "description": "Only events active on/after this date. ISO 8601 date/time, e.g. 2026-07-01 or 2026-07-01T00:00:00Z"
      },
      "limit": {
        "type": "integer",
        "maximum": 100,
        "minimum": 1,
        "description": "Max events (default 15)"
      },
      "source": {
        "type": "string",
        "description": "Source slug, e.g. 'coindesk' (see list_sources)"
      },
      "category": {
        "enum": [
          "crypto",
          "tradfi",
          "business",
          "tech",
          "politics",
          "world",
          "science",
          "health",
          "energy",
          "sports"
        ],
        "type": "string",
        "description": "Source category"
      },
      "semantic": {
        "type": "boolean",
        "description": "Rank by meaning (embedding similarity) instead of keyword match — requires q; better for concepts ('monetary easing') than exact strings"
      },
      "min_sources": {
        "type": "integer",
        "maximum": 50,
        "minimum": 1,
        "description": "Only events corroborated by at least this many distinct outlets — use 2-3 for briefings/headlines to skip single-source noise"
      }
    },
    "additionalProperties": false
  }

  arguments 55 lines copy
• search_articles reads open 10h ago

  Search raw articles (not collapsed into events). Use when you want the underlying items or need per-outlet coverage rather than deduped happenings.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "q": {
        "type": "string",
        "description": "Free-text keyword on headline + summary"
      },
      "to": {
        "type": "string",
        "description": "ISO 8601 date/time, e.g. 2026-07-01 or 2026-07-01T00:00:00Z"
      },
      "from": {
        "type": "string",
        "description": "ISO 8601 date/time, e.g. 2026-07-01 or 2026-07-01T00:00:00Z"
      },
      "limit": {
        "type": "integer",
        "maximum": 100,
        "minimum": 1,
        "description": "Max articles (default 25)"
      },
      "source": {
        "type": "string",
        "description": "Source slug"
      },
      "category": {
        "enum": [
          "crypto",
          "tradfi",
          "business",
          "tech",
          "politics",
          "world",
          "science",
          "health",
          "energy",
          "sports"
        ],
        "type": "string",
        "description": "Source category"
      }
    },
    "additionalProperties": false
  }

  arguments 45 lines copy
• get_event reads unknown 1h ago

  Fetch a single event by id, including every corroborating article (source, url, timestamp).

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "integer",
        "description": "Event id from get_events"
      }
    },
    "additionalProperties": false
  }

  arguments 14 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.