@zeph-to/mcp-server
npm
v2.3.1
Published by @zeph-to — 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.
Zeph MCP server — AI agent notifications, prompts, and input via MCP protocol
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 − 37.8 = 62. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −31.5 | Compound tool-poisoning pattern MTC-INJ-POISON | injection |
| −6.3 | Concealment directive aimed at the assistant MTC-INJ-SEM-1 | injection |
2. Client adoption risk — 62 − 7 = 55. 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 |
Grade capped: a critical finding is present → 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 a deduction.
Multiple tool-poisoning signals co-occur in a single field (secrecy, exfil-param), including a concealment / override / sensitive-target directive. Together they form an instruction aimed at the model — the canonical tool-poisoning shape, not ordinary documentation.
Evidence: Ask the user a question with quick-reply buttons and a text input field. Combines prompt (buttons) and input (text) in a single notification. The user can either tap a button or type a response. `acti
Fix: Do not install this server; the metadata is engineered to manipulate the assistant.
Location: tool zeph_ask · description
In the server's implementation (`dist/config.js:7`): 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: equire("crypto"); const child_process_1 = require("child_process"); const path_1 = require("path"); const DEFAULT_BASE_U
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/config.js
The description of tool "zeph_ask" combines a negation or stealth marker with a disclosure verb and a reference to the user — "keep this from the person" expressed as a shape rather than a fixed phrase, so it is detected regardless of wording or language. Metadata that tells the assistant what to withhold from its operator is not documentation.
Evidence: ike zeph notify and zeph file this tool is never end to
Fix: Tool metadata must not instruct the assistant to withhold anything from the user. Describe what the tool does; leave disclosure to the client.
Location: tool zeph_ask · description
Each tool and what it can reach — statically extracted from the published source.
zeph_inputnetwork egresszeph_askno sensitive capabilityzeph_broadcastno sensitive capabilityzeph_clipboardno sensitive capabilityzeph_dismissno sensitive capabilityzeph_dismiss_allno sensitive capabilityzeph_fileno sensitive capabilityzeph_listno sensitive capabilityzeph_notifyno sensitive capabilityzeph_promptno sensitive capabilityzeph_session_renameno sensitive capabilityScan 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 |
|---|---|---|---|---|
v2.3.1 latest |
F 55/100 | 3 | 1.13.0 | 2026-09-07 |
v2.3.0 |
F 55/100 | 3 | 1.13.0 | 2026-09-06 |
v2.2.0 |
F 55/100 | 3 | 1.12.1 | 2026-08-16 |
v2.1.0 |
F 55/100 | 3 | 1.12.1 | 2026-08-10 |
v2.0.0 |
A 93/100 | 1 | 1.12.1 | 2026-08-07 |
v1.16.0 |
A 93/100 | 1 | 1.12.1 | 2026-08-05 |
v1.15.2 |
A 93/100 | 1 | 1.12.1 | 2026-08-04 |
v1.15.1 |
A 93/100 | 1 | 1.12.1 | 2026-07-29 |
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 @zeph-to/mcp-server --online
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.