Sidebutton MCP Server

@sidebutton/server npm v1.5.9

Published by @sidebutton — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

SideButton MCP server for AI agents — REST API, web dashboard, knowledge packs, and workflow engine

Trust grade
B
83/100
Last scanned get badge →
Trust
B · 83/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Critical
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
B Why this grade threat 94 − adoption risk = 83/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 6.3 = 94. What the published surface and source actually contain:

PointsWhat was foundCategory
−6.3 Untrusted input concatenated into a command sink MTC-SRC-009 injection

2. Client adoption risk — 94 − 11 = 83. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−10 capability blast radius (critical) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 5

high Shell/command execution in server code (dashboard/assets/index-CsPS9ETx.js)MTC-SRC-002

In the server's implementation (`dashboard/assets/index-CsPS9ETx.js:528`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: peared after the window spawn (window ${r.windowExited?`exited ${r.windowExitCode}`:`still running`}) \u2014 launching h

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dashboard/assets/index-CsPS9ETx.js

high Shell/command execution in server code (dist/chunk-VQUZOFC6.js)MTC-SRC-002

In the server's implementation (`dist/chunk-VQUZOFC6.js:1509`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: import { spawn } from "child_process"; var DEFAULT_TIMEOUT_MS = 3e4; function executePluginTool(plugin, tool, input) {

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/chunk-VQUZOFC6.js

high Shell/command execution in server code (dist/cli.js)MTC-SRC-002

In the server's implementation (`dist/cli.js:986`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: exec } = await import("child_process"); const openCmd = process.platform === "darwin" ? "open" : process.platform =

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/cli.js

medium Hardcoded egress to an external endpoint (dist/cli.js)MTC-SRC-003

In the server's implementation (`dist/cli.js:963`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const deviceRes = await fetch(`https://${AUTH0_DOMAIN}/oauth/device/code`, { method: "POST", headers: { "Con

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/cli.js

medium Untrusted input concatenated into a command sink (dist/cli.js)MTC-SRC-009

In the server's implementation (`dist/cli.js:988`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: tart" : "xdg-open"; exec(`${openCmd} "${deviceData.verification_uri_complete}"`); console.log(" Waiting for aut

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/cli.js

Tools 29

Each tool and what it can reach — statically extracted from the published source.

  • publish_artifactingests untrusted input
  • browser_batchno sensitive capability
  • capture_pageno sensitive capability
  • clear_basic_authno sensitive capability
  • clickno sensitive capability
  • evaluateno sensitive capability
  • existsno sensitive capability
  • extractno sensitive capability
  • extract_allno sensitive capability
  • extract_mapno sensitive capability
Show 19 more tools ↓
  • fillno sensitive capability
  • get_browser_statusno sensitive capability
  • get_run_logno sensitive capability
  • get_workflowno sensitive capability
  • hoverno sensitive capability
  • inject_cssno sensitive capability
  • list_run_logsno sensitive capability
  • list_workflowsno sensitive capability
  • navigateno sensitive capability
  • press_keyno sensitive capability
  • run_workflowno sensitive capability
  • screenshotno sensitive capability
  • scrollno sensitive capability
  • scroll_into_viewno sensitive capability
  • select_optionno sensitive capability
  • set_basic_authno sensitive capability
  • snapshotno sensitive capability
  • typeno sensitive capability
  • waitno sensitive capability

What this scan could not see

Versions 6

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.5.9 latest B 83/100 5 1.13.0 2026-09-07
v1.5.8 B 83/100 5 1.13.0 2026-08-31
v1.5.5 B 83/100 4 1.13.0 2026-08-30
v1.5.3 B 83/100 4 1.12.1 2026-08-09
v1.5.2 B 83/100 4 1.12.1 2026-08-05
Show 1 more version ↓
v1.5.1 B 83/100 4 1.10.0 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: B · 83/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/sidebutton-server/badge.svg)](https://mcptrustchecker.com/registry/sidebutton-server)
HTML
<a href="https://mcptrustchecker.com/registry/sidebutton-server"><img src="https://mcptrustchecker.com/registry/sidebutton-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/sidebutton-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @sidebutton/server --online

Use the free API → How scoring works

Other implementations of Sidebutton 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Developer Tools