NewsMCP
com.newsmcp/newsmcp · 1.0.0
Live world news deduplicated into story events, with corroboration counts and source links.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 60 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://mcp.newsmcp.com/mcpstreamable-httpx-api-keyoptional, secret: Optional NewsMCP API key. Omit for keyless access.
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 5 tools.
- Protocol
- 2025-06-18
- Calls itself
- NewsMCP 0.6.4
- Handshake time
- 145 ms
- HTTP status
- 200
The tools it lists (5, as of 2 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
newsSearch 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 st
get_storyExpand 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.
check_coverageJudge 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 sto
check_limitsReport 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 i
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.newsmcp/newsmcp, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 35 days ago. The registry entry · newsmcp.com