MCPgrade

MCP server · trust report

io.github.cyanheads/mcp-ts-core

Published by io.github.cyanheads

version-controlanalytics

1 check that ran failed — version behavior — so this release can’t be trusted as-is.

Publisher
io.github.cyanheads
Repository
github.com/cyanheads/mcp-ts-core
Install
npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core, npm:@cyanheads/mcp-ts-core
Versions
132
Inspected
5 of 6 checks · 75%
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 checks1 clean4 flagged1 not inspected

  • Injection surface

    unscannable25% of grade

    Tool 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

    warn25% of grade

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

    dependency "hono" is edit-distance 2 from popular package "pino" (typosquat candidate); dependency "jose" is edit-distance 2 from popular package "@babel/core" (typosquat candidate); dependency "@opentelemetry/api" is edit-distance 2 from popular package "pg" (typosquat candidate); dependency "@modelcontextprotocol/client" is edit-distance 2 from popular package "@aws-sdk/client-s3" (typosquat candidate); dependency "@modelcontextprotocol/server" is edit-distance 1 from popular package "semver" (typosquat candidate)

  • Credential hygiene

    pass15% of grade

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

    Reads secrets from the environment (e.g. scripts/devcheck.ts) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

  • Permission scope

    warn15% of grade

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

    references credential paths: scripts/devcheck.ts: references a credential path (/mcp.json) references credential paths: scripts/lint-packaging.ts: references a credential path (/mcp.json) discloses shell/exec capability: 8 files (scripts/build.ts, scripts/check-framework-antipatterns.ts, scripts/check-skill-versions.ts, +5 more) 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 grade

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

    vs prior 0.12.3 (patch bump): new capability primitive(s) in source: child_process; new hardcoded outbound host/BCC destination(s): caseyjhand.com, github.com, mcp.example.com, no-color.org, unpkg.com, www.buymeacoffee.com, your-idp.example.com; new install hook(s) not present in prior version: prepare.

  • Transport config

    warn10% of grade

    Remote 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.

VersionPublishedGradeScoreInspectedChange
v0.12.5 · current2026-09-02 C655/6 · 75%B→C in v0.12.5
v0.12.32026-08-21 B804/6 · 65%±0
v0.11.52026-08-13 B804/6 · 65%±0
v0.11.42026-08-10 B803/6 · 55%C→B in v0.11.4
v0.11.22026-08-10 C655/6 · 75%±0
v0.11.12026-08-02 C655/6 · 75%B→C in v0.11.1
v0.11.02026-07-26 B754/6 · 65%±0
v0.12.12026-08-20 B803/6 · 55%C→B in v0.12.1
v0.10.152026-07-19 C655/6 · 75%B→C in v0.10.15
v0.10.142026-07-06 B754/6 · 65%±0
v0.9.212026-06-02 B754/6 · 65%±0
v0.1.272026-03-23 B754/6 · 65%—