Node Huckleberry MCP Server
node-huckleberry-mcp
npm
v0.7.0
Source verified
Published by kenlsm — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Node.js MCP server for Huckleberry baby tracker. Expose sleep, feeding, growth, diapers, and solids data to Claude and other AI applications.
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 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Hardcoded Google API key in server code MTC-SRC-008 | exfiltration |
2. Client adoption risk — 99 − 0 = 99. 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:
✓ No adoption-risk deductions — minimal blast radius, verified enough, and fully inspected.
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 Hardcoded Google API key in server code (dist/config.js)MTC-SRC-008
A hardcoded Google API key (a public Firebase/web API key) appears in `dist/config.js:3`. Verify whether this is a real credential; if so, remove and rotate it.
Evidence: Google API key: AIza…(redacted)
Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.
Location: server dist/config.js
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 3
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.7.0 latest |
A 99/100 | 1 | 1.13.0 | 2026-09-07 |
v0.6.0 |
A 99/100 | 1 | 1.12.1 | 2026-08-19 |
v0.5.0 |
A 99/100 | 1 | 1.12.1 | 2026-08-10 |
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 node-huckleberry-mcp --onlineMore in API Development
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.