Neos MCP Server
@upassist/neos-mcp
npm
v1.0.0
Published by @upassist — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP server for Neos CMS — connects AI assistants to any UpAssist.Neos.Mcp bridge
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 Dynamic code execution in server code (dist/index.js)MTC-SRC-001
In the server's implementation (`dist/index.js:2943`): 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 makeValidate = new Function(`${names_1.default.self}`, `${names_1.default.scope}`, sourceCode); const v
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 24
Each tool and what it can reach — statically extracted from the published source.
neos_get_page_contentingests untrusted inputneos_create_content_nodeno sensitive capabilityneos_create_document_nodeno sensitive capabilityneos_delete_nodeno sensitive capabilityneos_entity_actionno sensitive capabilityneos_entity_createno sensitive capabilityneos_entity_deleteno sensitive capabilityneos_entity_discoverno sensitive capabilityneos_entity_listno sensitive capabilityneos_entity_showno sensitive capability
Show 14 more tools ↓
neos_entity_updateno sensitive capabilityneos_get_document_propertiesno sensitive capabilityneos_get_preview_urlno sensitive capabilityneos_get_site_contextno sensitive capabilityneos_list_asset_tagsno sensitive capabilityneos_list_assetsno sensitive capabilityneos_list_node_typesno sensitive capabilityneos_list_pagesno sensitive capabilityneos_list_pending_changesno sensitive capabilityneos_move_nodeno sensitive capabilityneos_publish_changesno sensitive capabilityneos_restartno sensitive capabilityneos_setup_workspaceno sensitive capabilityneos_update_node_propertyno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (24 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.0 latest |
A 92/100 | 1 | 1.13.0 | 2026-09-07 |
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 @upassist/neos-mcp --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.