NewsMCP MCP server
com.newsmcp/newsmcpnewsmcp.comstreamable-httpv1.0.0Scanned
Live world news deduplicated into story events, with corroboration counts and source links.
5 tools: 3 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the NewsMCP MCP server can do
The NewsMCP MCP server is published by newsmcp.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (3 tools: check_coverage, check_limits and check_health), but cannot delete data. 2 tools only read.
3 tools bring in text other people can write (news, get_story and check_coverage).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 3Claude Code: ask
check_coverageJudge how widely and how independently a claim has been reported.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
check_healthCheck whether the NewsMCP REST API is reachable and healthy.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
check_limitsReport what this caller may do right now — and never spend any of it to find out.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 2Show 2 read-only tools
get_storyExpand one story: full summary, classification, actors, and source links.Reads text others writeNo findings
Why it is in this group
- The name "get_story" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
newsSearch already-synthesized news events — pre-built story digests — or fetch one by id.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:43 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.newsmcp.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://mcp.newsmcp.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.newsmcp.com/mcp: tools/list returned 5 tools to an anonymous client, including check_coverage (write), check_limits (write), check_health (write)
Posture changes
- Oct 29, 2026
- RFC 9728 protected resource metadata: none to https://mcp.newsmcp.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://mcp.newsmcp.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools5 changed.~5 changedView diff
- Changed:check_coverageChanges thingsinputSchema
- Changed:check_healthChanges thingsinputSchema
- Changed:check_limitsChanges thingsinputSchema
- Changed:get_storyOnly readsinputSchema
- Changed:newsOnly readsinputSchema
Tools5 changed.~5 changedView diff
- Changed:check_coverageChanges thingsinputSchema
- Changed:check_healthChanges thingsinputSchema
- Changed:check_limitsChanges thingsinputSchema
- Changed:get_storyOnly readsinputSchema
- Changed:newsOnly readsinputSchema
PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://mcp.newsmcp.com/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://mcp.newsmcp.com; Dynamic client registration: not observed -> yes…View diff
- RFC 9728 protected resource metadata: none to https://mcp.newsmcp.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://mcp.newsmcp.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http newsmcp https://mcp.newsmcp.com/mcpclaude mcp add --transport http newsmcp https://mcp.newsmcp.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__newsmcp__news",
"mcp__newsmcp__get_story"
],
"ask": [
"mcp__newsmcp__check_coverage",
"mcp__newsmcp__check_limits",
"mcp__newsmcp__check_health"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as newsmcp. Review it before you use it.
Capability tags behind 3 rules
- mcp__newsmcp__news untrusted-input
- mcp__newsmcp__get_story untrusted-input
- mcp__newsmcp__check_coverage untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.newsmcp/newsmcp/verify?hash=ec723c4e701c6d655bdf4d20c457f1a06ca79c5d72716358ca0d336c5e8306f2" | jq -e '.changed == false'Pinned hash ec723c4e701c, from Nov 13, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.newsmcp/newsmcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.newsmcp/newsmcp)Source: MCP Registry. Synced Oct 21, 2026, 17:59 UTC.
NewsMCP MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the NewsMCP MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the NewsMCP MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the NewsMCP MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the NewsMCP MCP server have?
- 5 tools: 3 write, 2 read. check_coverage, check_limits, check_health, news and get_story.
Does the NewsMCP MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the NewsMCP MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the NewsMCP MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.