# NewsMCP

> Live world news deduplicated into story events, with corroboration counts and source links.

- name: com.newsmcp/newsmcp
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 80/100 flags: no-repository
- quality: 85/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.newsmcp%2Fnewsmcp
- tools: https://api.protogrid.dev/v1/servers/com.newsmcp%2Fnewsmcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "newsmcp": {
      "type": "http",
      "url": "https://mcp.newsmcp.com/mcp",
      "headers": {
        "x-api-key": "${X_API_KEY}"
      }
    }
  }
}
```

Placeholders to fill: `${X_API_KEY}`.

## Trust

- hygiene: 80
- liveness: 100
- freshness: 85
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% ~updated-48d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 85/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 5 of 5 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_story (idempotentHint); check_coverage (idempotentHint); check_limits (idempotentHint); …
- pass `tools.token_cost`: about 3,922 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 5, about 3,922 tokens to load them all
- tool set hash: 49156161051661db0af1b14334c69830
- badge: [![protogrid quality](https://protogrid.dev/badge/com.newsmcp/newsmcp.svg)](https://protogrid.dev/servers/com.newsmcp/newsmcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://mcp.newsmcp.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (5)

- `check_coverage`: 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.
- `check_health`: 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.
- `check_limits`: 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.
- `get_story`: 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.
- `news`: 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.