@tatine13/mcp-manager
npm
v1.0.1
Published by @tatine13 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Universal MCP Server for Multi-Account Email Management with Personas, Tasks, and FTS5 Local Memory
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 − 7 = 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 |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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.
In the server's implementation (`dist/bin/cli.js:21`): 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: t { spawn, exec } from 'child_process'; import { z } from 'zod'; var DEFAULT_DATA_DIR = path2.join(os.homedir(), ".mail
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/bin/cli.js
In the server's implementation (`dist/bin/server.js:20`): 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: t { spawn, exec } from 'child_process'; import { z } from 'zod'; var DEFAULT_DATA_DIR = path2.join(os.homedir(), ".mail
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/bin/server.js
In the server's implementation (`dist/index.js:19`): 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: t { spawn, exec } from 'child_process'; import { z } from 'zod'; // src/core/server.ts var DEFAULT_DATA_DIR = path2.joi
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
Untrusted-input tools ([read_email, download_attachment]) co-exist with external-action tools ([send_email, create_inbound_webhook, create_outbound_webhook, webhook_logs]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [read_email, download_attachment] → sinks [send_email, create_inbound_webhook, create_outbound_webhook, webhook_logs]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow read_email → send_email
Each tool and what it can reach — statically extracted from the published source.
create_inbound_webhooknetwork egresscreate_outbound_webhooknetwork egressdownload_attachmentingests untrusted inputread_emailingests untrusted inputsend_emailnetwork egresswebhook_logsnetwork egressadd_accountno sensitive capabilityadd_provider_presetno sensitive capabilitycreate_directiveno sensitive capabilitycreate_personano sensitive capabilitycreate_taskno sensitive capabilitydelete_directiveno sensitive capabilitydelete_emailno sensitive capabilitydelete_personano sensitive capabilitydelete_taskno sensitive capabilityexecute_taskno sensitive capabilityget_email_historyno sensitive capabilityget_server_infono sensitive capabilitylist_accountsno sensitive capabilitylist_directivesno sensitive capabilitylist_emailsno sensitive capabilitylist_personasno sensitive capabilitylist_provider_presetsno sensitive capabilitylist_tasksno sensitive capabilitylist_webhooksno sensitive capabilitymove_emailno sensitive capabilityremove_accountno sensitive capabilitysearch_emailsno sensitive capabilitysearch_local_emailsno sensitive capabilitysync_emailsno sensitive capabilitytest_connectionno sensitive capabilitytest_directiveno sensitive capabilityupdate_personano sensitive capabilityvault_statusno sensitive capabilityCross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
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.0.1 latest |
A 93/100 | 4 | 1.13.0 | 2026-09-07 |
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.
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 @tatine13/mcp-manager --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →
A manager for Model Context Protocol services.
MCP Manager is an open-source tool that provides a single control point to organize, activate, and dynamically manage groups of Model Context Protocol (MCP) services so users can quickly switch between clean, purpose-built environments for their different
MCP server health monitor, auto-restart daemon, and status dashboard
A CLI tool for managing Model Context Protocol (MCP) servers
MCP AgentChat - 让 AI Agent 通过 Telegram 与用户实时交互:发送消息、图片,等待用户回复
A Model Context Protocol (MCP) server for Airthings Air Quality Monitor devices.
MCP server for Anki
TypeScript package for reading and searching Apple Notes on macOS via direct SQLite access. Includes markdown conversion, attachment support, and offers a local MCP server!
Verified biotech catalyst calendar (PDUFA/AdComm/trial readouts) anchored to official sources.
Appointment booking platform letting agents check provider availability and create bookings.