MCP server · trust report

io.github.sidebutton/sidebutton

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

Publisher
io.github.sidebutton
Repository
github.com/sidebutton/sidebutton
Install
npm:@sidebutton/server, npm:@sidebutton/server
Versions
2
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.

6 checks2 clean3 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.

    package name "@sidebutton/server" is edit-distance 1 from popular package "semver" (typosquat candidate); dependency "@sentry/node" is edit-distance 2 from popular package "@babel/core" (typosquat candidate); dependency "@fastify/cors" is edit-distance 1 from popular package "@babel/core" (typosquat candidate); dependency "@sidebutton/core" is edit-distance 1 from popular package "cors" (typosquat candidate)

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

    Network egress present (dashboard/assets/index-BXbktGRP.js: outbound HTTP/socket call) — expected for most servers and not a finding on its own. 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 1.1.1 (minor bump): new capability primitive(s) in source: child_process, http-client; new hardcoded outbound host/BCC destination(s): api.anthropic.com, api.openai.com, docs.sentry.io, github.com, sentry.io, sidebutton.com, svelte.dev, www.w3.org.

  • Transport config

    warn10% of grade

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

    sends telemetry to third-party SDK (sentry.io) — disclosure, verify opt-in; manifest/source references analytics 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
v1.5.2 · current2026-07-27 C72.55/6 · 75%B→C in v1.5.2
v1.1.12026-04-16 B87.53/6 · 55%