Excel Webview2 MCP Server

@dsbissett/excel-webview2-mcp npm v0.0.13

Published by @dsbissett — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
C
72/100
Last scanned
Trust
C · 72/100
How safe the published surface and source look. 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.
C Why this grade 100 − 28.3 = 72/100

Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:

PointsWhat was foundCategory
−22 Hardcoded Google API key in server code MTC-SRC-008 exfiltration
−6.3 Untrusted input concatenated into a command sink MTC-SRC-009 injection

Grade capped: 1 confirmed high finding → grade capped at C. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.

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 the deduction.

Findings 9

high Hardcoded Google API key in server code (build/src/tools/performance.js)MTC-SRC-008

A live-looking Google API key is hardcoded in `build/src/tools/performance.js:165`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: Google API key: AIza…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server build/src/tools/performance.js

high Shell/command execution in server code (build/src/browser.js)MTC-SRC-002

In the server's implementation (`build/src/browser.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: child_process

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 build/src/browser.js

high Shell/command execution in server code (build/src/daemon/client.js)MTC-SRC-002

In the server's implementation (`build/src/daemon/client.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: child_process

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 build/src/daemon/client.js

high Shell/command execution in server code (build/src/launch/forceShutdown.js)MTC-SRC-002

In the server's implementation (`build/src/launch/forceShutdown.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: child_process

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 build/src/launch/forceShutdown.js

high Shell/command execution in server code (build/src/launch/launchExcel.js)MTC-SRC-002

In the server's implementation (`build/src/launch/launchExcel.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: child_process

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 build/src/launch/launchExcel.js

high Shell/command execution in server code (build/src/telemetry/WatchdogClient.js)MTC-SRC-002

In the server's implementation (`build/src/telemetry/WatchdogClient.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: child_process

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 build/src/telemetry/WatchdogClient.js

high Shell/command execution in server code (build/src/utils/check-for-updates.js)MTC-SRC-002

In the server's implementation (`build/src/utils/check-for-updates.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: child_process

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 build/src/utils/check-for-updates.js

medium Hardcoded egress to an external endpoint (build/src/bin/check-latest-version.js)MTC-SRC-003

In the server's implementation (`build/src/bin/check-latest-version.js:7`): 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: fetch('https://registry.npmjs.org/@dsbissett%2fexcel-webview2-mcp/latest'

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 build/src/bin/check-latest-version.js

medium Untrusted input concatenated into a command sink (build/src/launch/launchExcel.js)MTC-SRC-009

In the server's implementation (`build/src/launch/launchExcel.js:268`): 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: spawn(`"${

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 build/src/launch/launchExcel.js

What this scan could not see

Versions

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.0.13 latest C 72/100 9 1.5.0 2026-07-22

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

Use the free API → How scoring works

More in Developer Tools