Sprigr MCP Server

@sprigr/mcp-server npm v1.16.0

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

Trust grade
D
68/100
Last scanned
Trust
D · 68/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.
D Why this grade 100 − 31.9 = 68/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
−23.1 Dynamic evaluation of a non-literal value ×2 MTC-SRC-010 injection
−6.7 Possible combosquat of mcp ×4 MTC-SUP-006 supply-chain
−2.1 Package has no source repository MTC-SUP-011 supply-chain

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 10

high Dynamic evaluation of a non-literal value (wasm-bundler/sprigr_browser_bg.js)MTC-SRC-010

In the server's implementation (`wasm-bundler/sprigr_browser_bg.js:370`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: new Function(

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 wasm-bundler/sprigr_browser_bg.js

high Dynamic evaluation of a non-literal value (wasm/sprigr_browser.js)MTC-SRC-010

In the server's implementation (`wasm/sprigr_browser.js:372`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: new Function(

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 wasm/sprigr_browser.js

high Dynamic code execution in server code (wasm-bundler/sprigr_browser_bg.js)MTC-SRC-001

In the server's implementation (`wasm-bundler/sprigr_browser_bg.js:370`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: new Function(

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 wasm-bundler/sprigr_browser_bg.js

high Dynamic code execution in server code (wasm/sprigr_browser.js)MTC-SRC-001

In the server's implementation (`wasm/sprigr_browser.js:372`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: new Function(

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 wasm/sprigr_browser.js

medium Dynamic module load from a non-literal (dist/index.js)MTC-SRC-005

In the server's implementation (`dist/index.js:39`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. 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(jsPath)

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/index.js

medium Possible combosquat of mcpMTC-SUP-006

"@sprigr/mcp-server" is "mcp" with a decorative suffix — a common combosquat pattern.

Fix: Confirm you meant "mcp". Install packages only from their documented, official name.

Location: package @sprigr/mcp-server

medium Possible combosquat of @playwright/mcpMTC-SUP-006

"@sprigr/mcp-server" is "@playwright/mcp" with a decorative suffix — a common combosquat pattern.

Fix: Confirm you meant "@playwright/mcp". Install packages only from their documented, official name.

Location: package @sprigr/mcp-server

medium Possible combosquat of @stripe/mcpMTC-SUP-006

"@sprigr/mcp-server" is "@stripe/mcp" with a decorative suffix — a common combosquat pattern.

Fix: Confirm you meant "@stripe/mcp". Install packages only from their documented, official name.

Location: package @sprigr/mcp-server

medium Possible combosquat of @browsermcp/mcpMTC-SUP-006

"@sprigr/mcp-server" is "@browsermcp/mcp" with a decorative suffix — a common combosquat pattern.

Fix: Confirm you meant "@browsermcp/mcp". Install packages only from their documented, official name.

Location: package @sprigr/mcp-server

low Package has no source repositoryMTC-SUP-011

"@sprigr/mcp-server" declares no repository URL, so its published artifact cannot be compared against reviewable source.

Fix: Prefer packages that link to public, reviewable source.

Location: package @sprigr/mcp-server

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
v1.16.0 latest D 68/100 10 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: D · 68/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/sprigr-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/sprigr-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/sprigr-mcp-server"><img src="https://mcptrustchecker.com/registry/sprigr-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/sprigr-mcp-server/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 @sprigr/mcp-server --online

Use the free API → How scoring works

More in Web, Search & Scraping