Sipcode MCP Server

sipcode npm v1.6.20 Source verified

Published by anuj7411 — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Sip your tokens, don't gulp them. Keep Claude Code's context clean: drift detection, re-read dedup, integrity scoring, AST-aware reads, and 15 MCP tools for Claude Desktop.

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/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
High
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
A Why this grade threat 100 − adoption risk = 94/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 − 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 − 6 = 94. 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
−6 capability blast radius (high) — client exposure if the model is manipulated

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 (dist/cli.js)MTC-SRC-002

In the server's implementation (`dist/cli.js:254`): 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: --live: safety cap per spawn (default 1.00)") .action(async (opts) => { const { runBenchmark } = await import("

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

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

In the server's implementation (`dist/commands/update.js:13`): 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: spawnSync } from "node:child_process"; const UPDATE_CMD = "npm i -g sipcode@latest"; const CHANGELOG_URL = "https://git

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/commands/update.js

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

In the server's implementation (`dist/lib/clipboard.js:12`): 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: { execFile } from "node:child_process"; import { promisify } from "node:util"; import * as nodeFs from "node:fs"; const

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/lib/clipboard.js

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

In the server's implementation (`dist/lib/git.js:7`): 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: { execFile } from "node:child_process"; import { promisify } from "node:util"; const execFileP = promisify(execFile); ex

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/lib/git.js

low Shell/command execution in packaging/dev tooling (dist/modules/benchmark/liveRunner.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`dist/modules/benchmark/liveRunner.js:18`): 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: rt { spawn } from "node:child_process"; import { promises as fs } from "node:fs"; import path from "node:path"; export c

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/modules/benchmark/liveRunner.js

Tools 15

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

  • audit_latest_sessionno sensitive capability
  • estimate_task_costno sensitive capability
  • forecast_monthly_spendno sensitive capability
  • get_agent_scoreno sensitive capability
  • get_drift_reportno sensitive capability
  • get_project_manifestno sensitive capability
  • get_proxy_statsno sensitive capability
  • get_proxy_statusno sensitive capability
  • get_session_statsno sensitive capability
  • get_sipcode_infono sensitive capability
Show 5 more tools ↓
  • get_today_summaryno sensitive capability
  • install_proxyno sensitive capability
  • list_recent_sessionsno sensitive capability
  • uninstall_proxyno sensitive capability
  • verify_sipcode_impactno sensitive capability

What this scan could not see

Versions 1

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.6.20 latest A 94/100 5 1.13.0 2026-09-09

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: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/sipcode/badge.svg)](https://mcptrustchecker.com/registry/sipcode)
HTML
<a href="https://mcptrustchecker.com/registry/sipcode"><img src="https://mcptrustchecker.com/registry/sipcode/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/sipcode/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 sipcode --online

Use the free API → How scoring works

More in Developer Tools