Savvyscratch MCP Server

@savvyscratch/mcp-server npm v1.0.1

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

Trust grade
F
55/100
Last scanned
Trust
F · 55/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
Minimal
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.
F Why this grade threat 60 − adoption risk = 55/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 − 39.7 = 60. What the published surface and source actually contain:

PointsWhat was foundCategory
−33 Hardcoded JSON Web Token in server code ×2 MTC-SRC-008 exfiltration
−6.7 Possible combosquat of mcp ×4 MTC-SUP-006 supply-chain

2. Client adoption risk — 60 − your exposure = 55. 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
0 capability blast radius (minimal) — client exposure if the model is manipulated
−5 publisher verification (none) — trust in the source of the package
0 inspection depth (source) — how much of the target the scan could see

Grade capped: 2 confirmed high findings → grade capped at D. 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 a deduction.

Findings 6

high Hardcoded JSON Web Token in server code (dist/lib/supabase.js)MTC-SRC-008

A live-looking JSON Web Token is hardcoded in `dist/lib/supabase.js:5`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: JSON Web Token: eyJh…(redacted)

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

Location: server dist/lib/supabase.js

high Hardcoded JSON Web Token in server code (src/lib/supabase.ts)MTC-SRC-008

A live-looking JSON Web Token is hardcoded in `src/lib/supabase.ts:7`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: JSON Web Token: eyJh…(redacted)

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

Location: server src/lib/supabase.ts

medium Possible combosquat of mcpMTC-SUP-006

"@savvyscratch/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 @savvyscratch/mcp-server

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

"@savvyscratch/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 @savvyscratch/mcp-server

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

"@savvyscratch/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 @savvyscratch/mcp-server

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

"@savvyscratch/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 @savvyscratch/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.0.1 latest D 60/100 6 1.5.0 2026-07-23

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

Use the free API → How scoring works

More in Gaming & Entertainment