Reveldigital MCP Server
@reveldigital/reveldigital-mcp-server
npm
v1.0.20
Published by @reveldigital — 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.
MCP Server generated from OpenAPI spec for revel-digital-rest-api
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.
Findings 4
high Dynamic evaluation of a non-literal value (build/index.js)MTC-SRC-010
In the server's implementation (`build/index.js:1227`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const zodSchema = eval(zodSchemaString); if (typeof zodSchema?.parse !== 'function') { throw n
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 build/index.js
high Dynamic evaluation of a non-literal value (src/index.ts)MTC-SRC-010
In the server's implementation (`src/index.ts:1338`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const zodSchema = eval(zodSchemaString); if (typeof zodSchema?.parse !== 'function') { thro
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 src/index.ts
high Dynamic code execution in server code (build/index.js)MTC-SRC-001
In the server's implementation (`build/index.js:1227`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const zodSchema = eval(zodSchemaString); if (typeof zodSchema?.parse !== 'function') { throw n
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 build/index.js
high Dynamic code execution in server code (src/index.ts)MTC-SRC-001
In the server's implementation (`src/index.ts:1338`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const zodSchema = eval(zodSchemaString); if (typeof zodSchema?.parse !== 'function') { thro
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 src/index.ts
Tools 64
Each tool and what it can reach — statically extracted from the published source.
deletedeviceno sensitive capabilitydeletedevicegroupno sensitive capabilitydeletemediano sensitive capabilitydeletemediagroupno sensitive capabilitydeleteplaylistno sensitive capabilitydeleteplaylistgroupno sensitive capabilitydeletescheduleno sensitive capabilitydeleteschedulegroupno sensitive capabilitydeletetemplateno sensitive capabilitydeletetemplategroupno sensitive capability
Show 54 more tools ↓
getaccountno sensitive capabilitygetdevicebyidno sensitive capabilitygetdevicegroupsno sensitive capabilitygetdevicepingdatano sensitive capabilitygetdevicesno sensitive capabilitygetmediano sensitive capabilitygetmediabyidno sensitive capabilitygetmediagroupsno sensitive capabilitygetorganizationsno sensitive capabilitygetpingdatano sensitive capabilitygetplaylistbyidno sensitive capabilitygetplaylistgroupsno sensitive capabilitygetplaylistsno sensitive capabilitygetreportbyidno sensitive capabilitygetschedulebyidno sensitive capabilitygetschedulegroupsno sensitive capabilitygetschedulesno sensitive capabilitygetsnapshotno sensitive capabilitygettemplatebyidno sensitive capabilitygettemplategroupsno sensitive capabilitygettemplatesno sensitive capabilitygetuserbyidno sensitive capabilitygetusersno sensitive capabilitypatchdeviceno sensitive capabilitypatchmediano sensitive capabilitypatchplaylistno sensitive capabilitypatchscheduleno sensitive capabilitypostdeviceno sensitive capabilitypostdevicecommandsno sensitive capabilitypostdevicegroupno sensitive capabilitypostdevicescommandsno sensitive capabilityposteventno sensitive capabilitypostmediabyfilenameno sensitive capabilitypostmediagroupno sensitive capabilitypostmediaimportno sensitive capabilitypostmediamultipartno sensitive capabilitypostplaylistno sensitive capabilitypostplaylistgroupno sensitive capabilitypostreportadhawkno sensitive capabilitypostreportexportno sensitive capabilitypostscheduleno sensitive capabilitypostschedulegroupno sensitive capabilityposttemplategroupno sensitive capabilityputaccountno sensitive capabilityputdeviceno sensitive capabilityputdevicegroupno sensitive capabilityputmediano sensitive capabilityputmediagroupno sensitive capabilityputplaylistno sensitive capabilityputplaylistgroupno sensitive capabilityputscheduleno sensitive capabilityputschedulegroupno sensitive capabilityputtemplategroupno sensitive capabilityrevel-digital-assistantno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (64 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.0.20 latest |
A 93/100 | 4 | 1.13.0 | 2026-09-09 |
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 @reveldigital/reveldigital-mcp-server --onlineMore in Developer Tools
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.