newsblog-composer-mcp@0.8.0
VERIFIED· not startedPublisher claims: "MCP server that researches, verifies and audits news blog posts. The writer writes the prose." 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
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso google.com, gdeltproject.org, gptzero.me, sapling.ai, techcrunch.com, theverge.com, arstechnica.com, wired.com, theregister.com, zdnet.com, venturebeat.com, thenextweb.com, siliconangle.com, techradar.com, tomshardware.com, cnet.com, techspot.com, axios.com, gizmodo.com, technologyreview.com, ieee.org, bbci.co.uk, theguardian.com, cnbc.com, npr.org, the-decoder.com, marktechpost.com, blog.google, deepmind.google, nvidia.com — 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 under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
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 84/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
"/.env.example",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Identity comes from profile.json, not .env, so a second person installingFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.except Exception as exc: # a dead provider must not kill the callFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Then in ChatGPT: Settings → Connectors → Advanced → Developer mode, then **AddFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.""".env sits beside the code in a checkout, in the data dir otherwise."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Then in ChatGPT: Settings → Connectors → Advanced → Developer mode, then **AddFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.return data_dir() / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.return _SOURCE_ROOT / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.every post carries whatever happens to be in .env - which means a second personFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.the project, ``.env`` read from there.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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 newsblog-composer-mcp@0.8.0 as of 32 h ago. This is the package itself, not its dependencies.