Fiori MCP Server
@sap-ux/fiori-mcp-server
npm
v1.12.2
Source verified
Published by sap — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
SAP Fiori - Model Context Protocol (MCP) server
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 − 6 = 94. 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 |
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 2
high Dynamic evaluation of a non-literal value (dist/ort-wasm-simd-threaded.jsep.mjs)MTC-SRC-010
In the server's implementation (`dist/ort-wasm-simd-threaded.jsep.mjs:51`): 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: rgs) {\n ${l}\n }`;d=(new Function(Object.keys(k),l))(...Object.values(k));l=`methodCaller<(${e.map(n=>n.name)}) => ${
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/ort-wasm-simd-threaded.jsep.mjs
high Dynamic code execution in server code (dist/ort-wasm-simd-threaded.jsep.mjs)MTC-SRC-001
In the server's implementation (`dist/ort-wasm-simd-threaded.jsep.mjs:51`): 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: rgs) {\n ${l}\n }`;d=(new Function(Object.keys(k),l))(...Object.values(k));l=`methodCaller<(${e.map(n=>n.name)}) => ${
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/ort-wasm-simd-threaded.jsep.mjs
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Versions 10
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.12.2 latest |
A 94/100 | 2 | 1.13.0 | 2026-09-06 |
v1.12.0 |
A 94/100 | 2 | 1.13.0 | 2026-09-01 |
v1.11.18 |
A 94/100 | 2 | 1.13.0 | 2026-08-31 |
v1.11.15 |
A 94/100 | 2 | 1.13.0 | 2026-08-27 |
v1.11.13 |
A 94/100 | 2 | 1.13.0 | 2026-08-25 |
Show 5 more versions ↓
v1.11.12 |
A 94/100 | 2 | 1.12.1 | 2026-08-20 |
v1.11.9 |
A 94/100 | 2 | 1.12.1 | 2026-08-19 |
v1.11.7 |
A 94/100 | 2 | 1.12.1 | 2026-08-10 |
v1.11.6 |
A 94/100 | 2 | 1.12.1 | 2026-08-06 |
v1.11.5 |
A 94/100 | 2 | 1.12.1 | 2026-08-05 |
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 @sap-ux/fiori-mcp-server --onlineMore in API Development
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.