supasidebar-mcp
npm
v0.2.3
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP server for SupaSidebar - lets AI assistants interact with your bookmarks, spaces, and tabs. Open source. Zero telemetry.
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 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 8 = 92. 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:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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.
In the server's implementation (`dist/tools/actions.js:1`): 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: ort { exec } from "node:child_process"; export async function handleToggleSidebar(client) { const result = await cli
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/tools/actions.js
Untrusted-input tools ([web_search, list_search_shortcuts]) co-exist with external-action tools ([open_preferences]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [web_search, list_search_shortcuts] → sinks [open_preferences]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow web_search → open_preferences
Each tool and what it can reach — statically extracted from the published source.
list_search_shortcutsingests untrusted inputopen_preferencesnetwork egressweb_searchingests untrusted inputadd_atc_ruleno sensitive capabilityadd_linkno sensitive capabilityadd_search_shortcutno sensitive capabilityclear_shortcutno sensitive capabilitycreate_folderno sensitive capabilitycreate_spaceno sensitive capabilitydelete_atc_ruleno sensitive capabilityenable_featureno sensitive capabilityget_live_tabsno sensitive capabilityget_settingsno sensitive capabilityget_shortcutsno sensitive capabilityget_visibilityno sensitive capabilityguideno sensitive capabilitylaunch_sidebarno sensitive capabilitylist_atc_rulesno sensitive capabilitylist_browser_profilesno sensitive capabilitylist_foldersno sensitive capabilitylist_installed_browsersno sensitive capabilitylist_linksno sensitive capabilitylist_recentno sensitive capabilitylist_spacesno sensitive capabilitylist_tagsno sensitive capabilitymove_linkno sensitive capabilityopen_linkno sensitive capabilityremove_search_shortcutno sensitive capabilityreorder_atc_rulesno sensitive capabilitysearchno sensitive capabilityswitch_spaceno sensitive capabilitytoggle_command_panelno sensitive capabilitytoggle_sidebarno sensitive capabilityupdate_atc_ruleno sensitive capabilityupdate_settingno sensitive capabilityupdate_shortcutno sensitive capabilityCross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.2.3 latest |
A 92/100 | 2 | 1.13.0 | 2026-09-07 |
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.
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 supasidebar-mcp --online
Model Context Protocol (MCP) server that integrates AgentQL data extraction capabilities.
Screenshot any URL or HTML as PNG/JPEG/WebP from your AI agent. Full-page, clean, no install.
MCP server for aria51 accessibility scanner
Bridge any browser web app to Claude Code via MCP
Browserbase’s official MCP server: cloud headless browsers for agents, with sessions and screenshots.
MCP server for AI web browser automation using Browserbase and Stagehand