news-monitor-mcp@0.4.0
VERIFIED· not startedPublisher claims: "MCP server for global news monitoring via WorldNewsAPI – search, sentiment analysis, top headlines, and media monitoring for Swiss public institutions" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
MCP_BEARER_TOKENWORLD_NEWS_API_KEYConfiguration, not credentials: GITHUB_OUTPUT, GITHUB_STEP_SUMMARY, MCP_ALERT_RETENTION_DAYS, MCP_ALLOWED_HOSTS, MCP_ALLOWED_ORIGINS, MCP_CACHE_MAX_PER_TYPE, MCP_CACHE_SWEEP_SECONDS, MCP_HOST, MCP_PORT, NEWS_MONITOR_ALERTS_DIR, NEWS_MONITOR_ALERTS_FILE- Where it talks to
- no vendor host named in the codeAlso worldnewsapi.com, shields.io — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names worldnewsapi.com, shields.io as well as its own vendor. The guard injects MCP_BEARER_TOKEN, WORLD_NEWS_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-13 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
ergebnis = subprocess.run(["git", *argumente], cwd=pfad, env=umgebung, capture_output=True, text=True, check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.&& chown -R 10001:10001 /dataFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.subprocess.run([sys.executable, str(_SKRIPT), str(pfad)], capture_output=True, text=True, env=umgebung)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.&& rm -rf /wheelsFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""`MCPServer` lehnt einen unbekannten Schluessel schon im Konstruktor ab;Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.return subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.done = subprocess.run(call, capture_output=True, text=True, check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.return subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.ergebnis = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for news-monitor-mcp@0.4.0 as of 32 h ago. This is the package itself, not its dependencies.