Magma Handbook MCP Server

mcp-magma-handbook npm v3.0.0

Published by legenai — 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
How safe the published surface and source look. 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 100 − 44.8 = 55/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
−38.5 Hardcoded JSON Web Token in server code ×3 MTC-SRC-008 exfiltration
−6.3 Package runs install-time scripts MTC-SUP-010 supply-chain

Grade capped: 3 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 the deduction.

Findings 4

high Hardcoded JSON Web Token in server code (dist/smithery-index-backup.js)MTC-SRC-008

A live-looking JSON Web Token is hardcoded in `dist/smithery-index-backup.js:21`. 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/smithery-index-backup.js

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

A live-looking JSON Web Token is hardcoded in `dist/smithery-index.js:21`. 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/smithery-index.js

high Hardcoded JSON Web Token in server code (dist/src/smithery-index.js)MTC-SRC-008

A live-looking JSON Web Token is hardcoded in `dist/src/smithery-index.js:21`. 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/src/smithery-index.js

medium Package runs install-time scripts (postinstall)MTC-SUP-010

"mcp-magma-handbook" executes postinstall script(s) at install time. The large majority of malicious packages abuse install hooks to run code before you ever import them.

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package mcp-magma-handbook

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

Use the free API → How scoring works

More in Learning & Documentation