MCP server · trust report

io.github.nyuchi/mukoko-news

Passes 5 checks with a soft flag on version behavior — worth a look, not a dealbreaker.

Publisher
io.github.nyuchi
Repository
github.com/nyuchi/mukoko-news
Install
npm:@nyuchi/mukoko-news-mcp, npm:@nyuchi/mukoko-news-mcp
Versions
2
Inspected
6 of 6 checks · 100%
Scored
2026-09-03 · 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.

6 checks5 clean1 flagged
  • Injection surface

    pass25% of grade

    Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

    Scanned 99 text field(s); no instruction-injection patterns found. PASS = no static red flag. A server can serve different tool descriptions at runtime (the rug-pull class), which static scanning cannot see.

  • Supply chain

    pass25% of grade

    Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

    repository linkage verified

  • Credential hygiene

    pass15% of grade

    How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

    No hardcoded secrets, secret-shaped tool parameters, or leaked keys found. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

  • Permission scope

    pass15% of grade

    Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

    No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.

  • Version behavior

    warn10% of grade

    Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

    vs prior 1.1.0 (minor bump): new tool "get_briefing" touches a sensitive surface (email/exec/net/fs); new tool "track_story" appeared; new tool "get_location_news" appeared; new tool "compare_locations" appeared; new tool "get_source_view" appeared; new tool "find_stories" touches a sensitive surface (email/exec/net/fs); new tool "get_article" touches a sensitive surface (email/exec/net/fs); new tool "list_categories" appeared; new tool "list_sources" appeared; new tool "get_stats" appeared; new tool "get_my_feed" appeared; new tool "get_trending_analytics" appeared; new tool "detect_surge" appeared; new tool "get_content_analytics" appeared; new tool "trigger_enrichment" touches a sensitive surface (email/exec/net/fs); new tool "drain_enrichment_backlog" appeared.

  • Transport config

    pass10% of grade

    Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

    remote endpoint "https://news.mukoko.com/mcp" uses TLS (https); remote endpoint "https://news.mukoko.dev/mcp" uses TLS (https); remote endpoint uses OAuth (strongest auth mode)

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.

VersionPublishedGradeScoreInspectedChange
v1.2.0 · current2026-06-30 A956/6 · 100%B→A in v1.2.0
v1.1.02026-06-27 B1004/6 · 65%