Lafe Blog MCP Server
lafe-blog
npm
v0.1.0
Published by an unidentified publisher — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.
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 − 2.1 = 98. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −2.1 | Package has no source repository MTC-SUP-011 | supply-chain |
2. Client adoption risk — 98 − your exposure = 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:
| Points | Adoption-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 |
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 1
low Package has no source repositoryMTC-SUP-011
"lafe-blog" 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 lafe-blog
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.0 latest |
A 98/100 | 1 | 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.
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 lafe-blog --onlineMore in Developer Tools
Security scan results for the Apify MCP server.
Security scan results for the Basic React MCP server.
Security scan results for the Cloudflare MCP server.
Up-to-date, version-specific library documentation injected straight into prompts.
The official reference server exercising every MCP feature — tools, prompts, resources and sampling.
Security scan results for the Flint Chart MCP server.