Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MCP Sidecar

NPM · MCP-SIDECAR

Cross-platform MCP server for managing long-lived background processes from any MCP client

Available components

−1 this week 94 Trust /100

Last scanned (12 hours ago)

Scores higher than 97% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 5 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to lsequeiraa/mcp-sidecar). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 156 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 238 tokens (~39/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 −2
    • Stability: pass → 0.87 functional
  • 28 Oct 26 0
    • Stability: 0.97 → pass security
  • 27 Oct 26 0
    • Stability: pass → 0.97 functional
  • 21 Oct 26 0
    • Stability: 0.97 → pass security
  • 20 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.83 → pass security
  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/mcp-sidecar@0.3.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo lsequeiraa/mcp-sidecar
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/lsequeiraa/mcp-sidecar/.github/workflows/release.yml@refs/tags/v0.3.2
Rekor log index 1699931668
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:27e9d2b290e08035f424a19c1735d67f8263469b3dc00ff60ca5bf27ba6eba79d5714fec6b1994edec5052e9d87136a3150586214ce57dcfff9ebe8be

Background: How many MCP packages publish verified provenance →

Dependencies 5 packages
Packages resolved 5
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~238 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
list ~12

List all managed processes

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

output ~73

Get buffered stdout and stderr of a process

NameTypeReqDescription
idstringyesProcess ID
maxBytesnumber–Max total bytes for stdout+stderr combined (0 = unlimited). Keeps the most recent output. Stderr is prioritized.
tailnumber–Return only the last N lines (0 = all)

No output schema declared.

No examples provided.

send ~40

Write to a process's stdin

NameTypeReqDescription
idstringyesProcess ID
inputstringyesText to send (a trailing newline is added automatically)

No output schema declared.

No examples provided.

start ~58

Spawn a background process

NameTypeReqDescription
commandstringyesShell command to execute
cwdstring–Working directory for the process
envobject–Additional environment variables
namestring–Human-friendly name for the process

No output schema declared.

No examples provided.

status ~24

Get detailed state of a single process

NameTypeReqDescription
idstringyesProcess ID

No output schema declared.

No examples provided.

stop ~31

Terminate a managed process (graceful, then force)

NameTypeReqDescription
idstringyesProcess ID to stop

No output schema declared.

No examples provided.

Install

How do I install the MCP Sidecar server?

MCP Sidecar runs locally as an npm package, launched with npx -y mcp-sidecar. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcp-sidecar

# add to Claude Code
claude mcp add lsequeiraa-mcp-sidecar -- npx -y mcp-sidecar
Common questions

What is the MCP Sidecar server?

MCP Sidecar is listed in the public MCP registry as io.github.lsequeiraa/mcp-sidecar. Cross-platform MCP server for managing long-lived background processes from any MCP client. This page covers its npm package (mcp-sidecar).

Is the MCP Sidecar server safe to use?

MCP Sidecar scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the MCP Sidecar server expose?

MCP Sidecar exposes 6 tools: list, output, send, start, status, stop. Their descriptions and schemas cost roughly 238 tokens of context every time the server is loaded.

Is the MCP Sidecar server still maintained?

MCP Sidecar is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the MCP Sidecar server under?

MCP Sidecar declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the MCP Sidecar server?

VerifyMCP ran 16 checks on MCP Sidecar, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.