MCP server · trust report

io.routescore/mcp

3 checks that ran failed — credential hygiene, version behavior and transport config — so this release can’t be trusted as-is.

Publisher
io.routescore
Repository
github.com/routescore/mcp
Install
npm:@routescore/mcp, npm:@routescore/mcp
Versions
2
Inspected
6 of 6 checks · 100%
Scored
2026-07-20 · 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 checks2 clean4 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 77 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

    warn25% of grade

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

    package name "@routescore/mcp" is edit-distance 2 from popular package "yup" (typosquat candidate)

  • Credential hygiene

    fail15% of grade

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

    tool "check_swap" has a secret-shaped input parameter "token_out" — secrets must never be tool parameters (the model would supply/handle the credential). tool "check_swap" has a secret-shaped input parameter "token_in" — secrets must never be tool parameters (the model would supply/handle the credential). tool "quote_lrt_slashing" has a secret-shaped input parameter "lrt_token" — secrets must never be tool parameters (the model would supply/handle the credential).

  • 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

    fail10% of grade

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

    vs prior 0.3.3 (patch bump): new tool "check_swap" touches a sensitive surface (email/exec/net/fs); new tool "get_preflight_record" touches a sensitive surface (email/exec/net/fs); new tool "whoami" touches a sensitive surface (email/exec/net/fs); new tool "get_detector_manifest" touches a sensitive surface (email/exec/net/fs); new tool "quote_mev_cover" appeared; new tool "quote_bridge_refund" appeared; new tool "quote_lrt_slashing" appeared; new tool "simulate_scenario" touches a sensitive surface (email/exec/net/fs); new hardcoded outbound host/BCC destination(s): github.com, www.routescore.io.

  • Transport config

    fail10% of grade

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

    remote MCP endpoint declares NO authentication (unauthenticated remote — nginx-ui/CVE-2026-33032 class)

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
v0.3.5 · current2026-07-19 D52.56/6 · 100%B→D in v0.3.5
v0.3.32026-07-15 B87.53/6 · 55%