1 check that ran failed — version behavior — so this release can’t be trusted as-is.
- Publisher
- io.github.AKzar1el
- Repository
- github.com/AKzar1el/mcp-trendpulse
- Install
- pypi:mcp-trendpulse, pypi:mcp-trendpulse
- Versions
- 3
- Inspected
- 5 of 6 checks · 75%
- Scored
- 2026-09-01 · rubric 1.0.0
What we checked
Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.
Injection surface
unscannable25% of gradeTool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).
No tool descriptions, server instructions, prompts, or resources were fetched; nothing to scan for injection.
Supply chain
pass25% of gradePackage provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.
Python build script has no build-time network/exec; repository linkage verified
Credential hygiene
warn15% of gradeHow the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.
tests/test_observability.py: assigns a literal to secret (sens…ed (len 41)) — non-provider secret literal; prefer environment intake. tests/test_remote_asgi.py: assigns a literal to secret (do-n…en (len 32)) — non-provider secret literal; prefer environment intake.
Permission scope
warn15% of gradeDeclared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.
discloses broad/destructive filesystem access: src/mcp_trendpulse/news.py: open(…, 'w'/'a'/'x') write-mode file access Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.
Version behavior
fail10% of gradeDiff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).
vs prior 0.2.10 (patch bump): new capability primitive(s) in source: fs-write; new hardcoded outbound host/BCC destination(s): 10.0.0.1, 127.0.0.1, 169.254.169.254, 172.16.0.1, 192.168.0.1, 224.0.0.1, 93.184.216.34, allowed.test, app.digestseo.com, clerk.example.test, digestseo.com, digestseo.example.test, evil.example.test, evil.test, example.com, github.com, img.com, issuer.example.test, mock.com, news.com, news.google.com, nytimes.com, staging.example.test, trendpulse.example.test, trends.com, user, www.google.com.
Transport config
warn10% of gradeRemote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.
manifest/source references telemetry behavior — disclosure
Version history
Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.
| Version | Published | Grade | Score | Inspected | Change |
|---|---|---|---|---|---|
| v0.2.11 · current | 2026-08-31 | C | 70 | 5/6 · 75% | B→C in v0.2.11 |
| v0.2.10 | 2026-08-30 | B | 100 | 4/6 · 65% | ±0 |
| v0.2.9 | 2026-07-12 | B | 100 | 3/6 · 55% | — |