Tracepulse MCP Server

tracepulse npm v0.9.31

Published by sourjya — 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.

Runtime feedback MCP server for AI coding agents. ViewGraph sees the UI - TracePulse feels the backend.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/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 = 93/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 − 7 = 93. 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
−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 15

high Tool "verify_build" exposes command/code executionMTC-CAP-001

Tool "verify_build" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool verify_build

high Tool "run_and_watch" exposes command/code executionMTC-CAP-001

Tool "run_and_watch" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool run_and_watch

high Tool "verify_mcp" exposes command/code executionMTC-CAP-001

Tool "verify_mcp" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool verify_mcp

high Tool "start_server" exposes command/code executionMTC-CAP-001

Tool "start_server" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool start_server

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

In the server's implementation (`dist/cli.js:2099`): 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"; import { createInterface } from "readline"; import { resolve } from "path"; impo

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/init-command-V6O4TMLD.js)MTC-SRC-003

In the server's implementation (`dist/init-command-V6O4TMLD.js:101`): 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 res = await fetch("https://registry.npmjs.org/tracepulse/latest", { signal: AbortSignal.timeout(3e3)

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/init-command-V6O4TMLD.js

medium Unconstrained command parameter "typecheck_command" on "verify_build"MTC-CAP-006

Tool "verify_build" takes a command-shaped parameter "typecheck_command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool verify_build · inputSchema.properties.typecheck_command

medium Unconstrained command parameter "build_command" on "verify_build"MTC-CAP-006

Tool "verify_build" takes a command-shaped parameter "build_command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool verify_build · inputSchema.properties.build_command

medium Unconstrained command parameter "command" on "run_and_watch"MTC-CAP-006

Tool "run_and_watch" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool run_and_watch · inputSchema.properties.command

medium Unconstrained command parameter "command" on "verify_mcp"MTC-CAP-006

Tool "verify_mcp" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool verify_mcp · inputSchema.properties.command

medium Unconstrained command parameter "command" on "start_server"MTC-CAP-006

Tool "start_server" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool start_server · inputSchema.properties.command

low Mutating tool "verify_build" declares no destructiveHintMTC-CAP-005

Tool "verify_build" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool verify_build

low Mutating tool "run_and_watch" declares no destructiveHintMTC-CAP-005

Tool "run_and_watch" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool run_and_watch

low Mutating tool "verify_mcp" declares no destructiveHintMTC-CAP-005

Tool "verify_mcp" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool verify_mcp

low Mutating tool "start_server" declares no destructiveHintMTC-CAP-005

Tool "start_server" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool start_server

Tools 44

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

  • run_and_watchruns code / shell
  • start_serverruns code / shell
  • verify_buildruns code / shell
  • verify_mcpruns code / shell
  • acknowledge_errorno sensitive capability
  • check_driftno sensitive capability
  • check_portno sensitive capability
  • clear_errorsno sensitive capability
  • correlate_with_diffno sensitive capability
  • free_portno sensitive capability
Show 34 more tools ↓
  • get_audit_trailno sensitive capability
  • get_bug_patternsno sensitive capability
  • get_build_errorsno sensitive capability
  • get_correlated_errorsno sensitive capability
  • get_cross_layer_diagnosisno sensitive capability
  • get_error_clustersno sensitive capability
  • get_error_contextno sensitive capability
  • get_error_trendsno sensitive capability
  • get_errorsno sensitive capability
  • get_health_summaryno sensitive capability
  • get_infra_detailno sensitive capability
  • get_infra_statusno sensitive capability
  • get_migration_statusno sensitive capability
  • get_new_errorsno sensitive capability
  • get_perf_baselineno sensitive capability
  • get_project_healthno sensitive capability
  • get_prompt_contextno sensitive capability
  • get_requestsno sensitive capability
  • get_runtime_statusno sensitive capability
  • get_server_logsno sensitive capability
  • get_session_impactno sensitive capability
  • get_session_insightsno sensitive capability
  • get_session_summaryno sensitive capability
  • get_timelineno sensitive capability
  • list_probesno sensitive capability
  • list_servicesno sensitive capability
  • register_probeno sensitive capability
  • restart_serverno sensitive capability
  • stop_serverno sensitive capability
  • verify_fixno sensitive capability
  • verify_loopno sensitive capability
  • wait_for_buildno sensitive capability
  • wait_for_eventno sensitive capability
  • watch_for_errorsno 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
v0.9.31 latest A 93/100 15 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 · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/tracepulse/badge.svg)](https://mcptrustchecker.com/registry/tracepulse)
HTML
<a href="https://mcptrustchecker.com/registry/tracepulse"><img src="https://mcptrustchecker.com/registry/tracepulse/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/tracepulse/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 tracepulse --online

Use the free API → How scoring works

More in Developer Tools