NewsMCP
REMOTE · MCP.NEWSMCP.COM
Live world news deduplicated into story events, with corroboration counts and source links.
Available components
Last scanned (7 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 7 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability72
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 6289 tokens (~1048/item across 6 items; 5 tools + 1 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 7 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.6.4 → 0.7.0 functional
- “check_coverage” dropped the optional parameter “api_key” cosmetic
- “check_coverage” dropped the optional parameter “llm_model” cosmetic
- “check_health” dropped the optional parameter “llm_model” cosmetic
- “check_limits” dropped the optional parameter “api_key” cosmetic
- “check_limits” dropped the optional parameter “llm_model” cosmetic
- “get_story” dropped the optional parameter “api_key” cosmetic
- “get_story” dropped the optional parameter “llm_model” cosmetic
- “news” dropped the optional parameter “api_key” cosmetic
- “news” dropped the optional parameter “llm_model” cosmetic
- 6 Nov 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
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- “check_coverage” added an optional parameter “llm_model” cosmetic
- “check_health” added an optional parameter “llm_model” cosmetic
- “check_limits” added an optional parameter “llm_model” cosmetic
- “get_story” added an optional parameter “llm_model” cosmetic
- “news” added an optional parameter “llm_model” cosmetic
5 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 2 Oct 26 0
- Stability: 0.97 → pass 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
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 7 Nov 2026 · Probed https://mcp.newsmcp.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.newsmcp.com | CN=YR1,O=Let's Encrypt,C=US | 7 Oct 2026 | 5 Jan 2027 | RSA 2048 | SHA256-RSA | 52eab0efb73956056c2964acb37290fd052 |
| SANs: mcp.newsmcp.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.newsmcp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| newsmcp.com. | No DS | 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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.newsmcp.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.newsmcp.com/mcp | HTTPS enforced | 308 | https://mcp.newsmcp.com/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 →
check_coverage ~250
Judge how widely and how independently a claim has been reported. Answers "is this real?" rather than returning a list. Reports the number of INDEPENDENT newsrooms — outlets that reported it themselves — separately from the number of domains that carried it, which includes syndication. A story on 200 domains from 3 newsrooms is one story reprinted, not 200 confirmations. Because upstream clustering splits a story across languages, this totals the likely variants of the same story and presents that total as an upper bound, listing what was combined so the caller can check it is really one story.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | The claim or headline to check, phrased in the words a headline would use. Matched literally against headlines and summaries, not by meaning, so "atomic arsenal" will not find stories about nuclear w… |
| days_back | integer | – | How far back to look, in days. Defaults to 14. Clamped down to whatever the caller's plan allows, with a note saying so. |
| response_format | string | – | markdown (default), text, or json. Pass the format the user asked for rather than reformatting afterwards. |
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_newsrooms | integer | yes | Independent newsrooms for the best-corroborated matching story. |
| combined_newsrooms_upper_bound | integer | yes | Sum across clustered variants of the same story — an upper bound, not a confirmed count. |
| matched | boolean | yes | Whether any story matched the claim text in the window. |
| notes | array | yes | Query-normalization and plan-clamping notes to relay verbatim. |
| total_matching_stories | integer | yes | – |
| variants | array | yes | Anchor story first, then its likely variants. |
No examples provided.
check_health ~62
Check whether the NewsMCP REST API is reachable and healthy. Does not require an API token. Use when diagnosing connectivity, not for searching news. For allowances and remaining budget use `check_limits` instead. Returns: str: Health status reported by the API.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
check_limits ~195
Report what this caller may do right now — and never spend any of it to find out. Answers the questions the `news` tool descriptions cannot: how many searches are left this hour, how far back this plan reaches, the largest `limit` it allows, how many searches may run at once, and how long to wait if the budget is spent. These ceilings are per-plan and change without a release, so trust this over any number written into a description. Checking is free: the endpoint is exempt from every metering stage, so calling it does not consume an hourly call, a concurrency slot, or a credit. Reach for it before planning a batch of calls, and after any plan-limit or rate-limit error instead of guessing the ceiling that was hit.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | `text` (default) for a readable summary, `json` for the raw payload. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_story ~199
Expand one story: full summary, classification, actors, and source links. Use this after any search, when the user wants more than the digest line for a particular story. It is the only tool that can return a story's complete source list.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | The `event_id` of a story from an earlier result (e.g. `evt_...`). A story folded into a more complete one answers 404 naming its replacement id — fetch that instead. |
| include_sources | boolean | – | False (default) returns a sample of source links; True returns every one. A large story can carry several hundred, so leave this off unless the user asked for the full list. This is the only place th… |
| response_format | string | – | markdown (default), text, or json. Pass the format the user asked for rather than reformatting afterwards. |
| Name | Type | Req | Description |
|---|---|---|---|
| abstract | string|null | – | – |
| content_type | string|null | – | – |
| entities | array | – | Key actors named in the story. |
| event_id | string | – | Stable id, e.g. evt_... |
| event_type | string|null | – | family.leaf taxonomy value, e.g. deals.merger_acquisition. |
| first_seen | string|null | – | ISO 8601 UTC. |
| headline | string|null | – | – |
| language_count | integer|null | – | – |
| last_seen | string|null | – | ISO 8601 UTC. |
| newsrooms | integer|null | – | Independent newsrooms — the corroboration signal. |
| one_liner | string|null | – | – |
| reports | integer|null | – | – |
| sector | string|null | – | – |
| size | integer|null | – | Article count. |
| source_count | integer|null | – | Publisher domains, mirrors included. |
| sources | array | – | Source article URLs — a sample or the full list per verbosity. |
No examples provided.
news ~2,131
Search already-synthesized news events — pre-built story digests — or fetch one by id. Each story comes with a generated headline, one-liner, abstract, key actors, and industry/event-type labels. Use it for a quick digest of what happened, for deal/incident-type or industry filtering, and for corroboration ranking. Nothing is required: a bare call returns the most-corroborated stories of the last 24 hours. Limits — keyless: 7-day `from_` lookback, 20 calls/hour, 20 stories per call, over-limit narrowed with a notice. With a key: per-plan ceilings (free tier today 14 days, 50 calls/hour, 50 stories), over-limit rejected rather than narrowed. Call `check_limits` for the live numbers; it is free and never spends the budget it reports on. Filters combine with AND; `event_type`, `content_type`, and `sector` each accept several comma-separated values combined with OR.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | – | – | The FORM the reporting takes, independent of what it is about. Comma-separated for OR. One of: news_report, press_release, service_info, human_interest, explainer, commentary, analysis, opinion, inte… |
| event_id | – | – | Superseded by the `get_story` tool, which does this with two arguments instead of nineteen and can return every source link. Kept for compatibility. Fetch ONE story directly by the `event_id` of an e… |
| event_type | – | – | What KIND of event the story is, independent of industry. Exact `family.leaf` value; a bare family (`deals`) is invalid and unknown values are rejected naming them. Comma-separated for OR (`deals.mer… |
| from_ | – | – | Inclusive lower bound on when the story BEGAN (its first_seen) — NOT the publish date of any one article, so a story still running today but started last week falls outside the default window. ISO 86… |
| limit | integer | – | Stories per page, 1–50, default 20, but capped for the caller: keyless 20 (softly, with a notice), and per-plan with a key (50 on the free tier today, over it is a validation error naming the maximum… |
| min_newsrooms | – | – | Minimum outlets that reported INDEPENDENTLY, mirrors excluded — the strongest is-this-real signal. Reach for this over min_sources whenever the user wants to exclude a story that one outlet ran and e… |
| q | – | – | Optional search terms, matched case-insensitively against the story's headline, one-liner, abstract, and named actors (no article body text, no stemming). Space-separated words are ANDed, so ALWAYS q… |
| response_format | string | – | Output shape in content[0].text. Default `markdown` (readable digest). `text` = plain lines. `json` = full API payload. Match what the user asks for. |
| sector | – | – | Industry the story belongs to. Comma-separated for OR (`software_it_services,semiconductors` = "tech and chips"). One of: government_public_sector, media_entertainment, financial_services, healthcare… |
| sort | – | – | What "best" means for this call. **Omit it** unless the user asked for a specific ordering: the API then picks `relevance` when `q` or `subject` is set and `newsrooms` when neither is, which is almos… |
| subject | – | – | A single company, person, place, or organisation to centre the search on — plain name, no quoting. Quoted for you, which is the difference between a phrase and a bag of words: `Bank of America` unquo… |
| verbosity | string | – | Controls ONLY the source-link list; headline, summary, actors, and labels are always present. `compact`: no links. `standard` (default): up to 3. `full`: every link, uncapped — use it for "show me ev… |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | Present for a search call (event_id unset). |
| keyless_notices | array | – | Present when a keyless caller's request was narrowed. |
| total | integer | – | Total matching stories; present for a search call. |
No examples provided.
How do I install the NewsMCP MCP server?
NewsMCP is a hosted endpoint at https://mcp.newsmcp.com/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 · mcp.newsmcp.com
claude mcp add --transport http com-newsmcp-newsmcp 'https://mcp.newsmcp.com/mcp'
What is the NewsMCP MCP server?
NewsMCP is an MCP server listed in the public MCP registry as com.newsmcp/newsmcp. Live world news deduplicated into story events, with corroboration counts and source links. This page covers its hosted endpoint (https://mcp.newsmcp.com/mcp).
Is the NewsMCP MCP server safe to use?
NewsMCP scores 87 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 NewsMCP MCP server expose?
NewsMCP exposes 5 tools: news, get_story, check_coverage, check_limits, check_health. Their descriptions and schemas cost roughly 2,837 tokens of context every time the server is loaded.
Does the NewsMCP MCP server require authentication?
No. We connected to NewsMCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the NewsMCP MCP server still maintained?
NewsMCP is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the NewsMCP MCP server?
VerifyMCP ran 13 checks on NewsMCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.