Manna Family MCP Server
manna-family-mcp
npm
v1.3.0
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
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 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 8 = 92. 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 |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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
high Shell/command execution in server code (dist/index.js)MTC-SRC-002
In the server's implementation (`dist/index.js:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: port { execSync } from "child_process"; import { Server } from "@modelcontextprotocol/sdk/server/index.js"; import { Std
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
Tools 36
Each tool and what it can reach — statically extracted from the published source.
get_recordingests untrusted inputadd_commentno sensitive capabilityapprove_pto_requestno sensitive capabilitycomplete_taskno sensitive capabilitycreate_recordno sensitive capabilitycreate_taskno sensitive capabilitydelete_recordno sensitive capabilityfind_personno sensitive capabilityfind_recordsno sensitive capabilityget_active_timerno sensitive capability
Show 26 more tools ↓
get_calendar_eventsno sensitive capabilityget_current_userno sensitive capabilityget_daily_digestno sensitive capabilityget_holidaysno sensitive capabilityget_initiativesno sensitive capabilityget_missionsno sensitive capabilityget_my_tasksno sensitive capabilityget_my_time_summaryno sensitive capabilityget_org_contextno sensitive capabilityget_overdue_tasksno sensitive capabilityget_projectsno sensitive capabilityget_pto_balanceno sensitive capabilityget_pto_policyno sensitive capabilityget_task_detailno sensitive capabilityget_team_workloadno sensitive capabilityget_time_reportno sensitive capabilityget_weekly_digestno sensitive capabilitylog_timeno sensitive capabilityreassign_taskno sensitive capabilityreject_pto_requestno sensitive capabilitysearch_tasksno sensitive capabilitystart_timerno sensitive capabilitystop_timerno sensitive capabilitysubmit_pto_requestno sensitive capabilityupdate_recordno sensitive capabilityupdate_task_statusno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (36 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
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 |
|---|---|---|---|---|
v1.3.0 latest |
A 92/100 | 1 | 1.9.0 | 2026-07-24 |
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 manna-family-mcp --onlineMore in Productivity & Workflow
Security scan results for the Agentchat MCP server.
Security scan results for the Airthings Consumer MCP server.
Security scan results for the Anki MCP server.
Security scan results for the Apple Notes Ts MCP server.
Appointment booking platform letting agents check provider availability and create bookings.
Book, reschedule and cancel appointments at any business on the BookingMaven marketplace.