Sap Gui MCP Server

mcp-sap-gui PyPI v0.3.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP Server for SAP GUI Scripting automation

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 92/100

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:

PointsAdoption-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 3

high Tool "sap_read_shell_content" exposes command/code executionMTC-CAP-001

Tool "sap_read_shell_content" appears to run shell commands or evaluate code (keyword "shell" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool sap_read_shell_content

low Mutating tool "sap_read_shell_content" declares no destructiveHintMTC-CAP-005

Tool "sap_read_shell_content" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool sap_read_shell_content

low Dynamic module load from a non-literal in packaging/dev tooling (tests/test_server.py)MTC-SRC-005

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_server.py:1546`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: return __builtins__.__import__(name, *args, **kwargs) with patch("builtins.__import__", side_effect=_import

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 tests/test_server.py

Tools 59

Each tool and what it can reach — statically extracted from the published source.

  • sap_read_shell_contentruns code / shell
  • sap_click_tree_linkno sensitive capability
  • sap_collapse_tree_nodeno sensitive capability
  • sap_connectno sensitive capability
  • sap_connect_existingno sensitive capability
  • sap_disconnectno sensitive capability
  • sap_double_click_cellno sensitive capability
  • sap_double_click_tree_itemno sensitive capability
  • sap_double_click_tree_nodeno sensitive capability
  • sap_execute_transactionno sensitive capability
Show 49 more tools ↓
  • sap_expand_tree_nodeno sensitive capability
  • sap_find_tree_node_by_pathno sensitive capability
  • sap_get_alv_toolbarno sensitive capability
  • sap_get_cell_infono sensitive capability
  • sap_get_column_infono sensitive capability
  • sap_get_combobox_entriesno sensitive capability
  • sap_get_current_cellno sensitive capability
  • sap_get_popup_windowno sensitive capability
  • sap_get_screen_elementsno sensitive capability
  • sap_get_screen_infono sensitive capability
  • sap_get_session_infono sensitive capability
  • sap_get_table_control_row_infono sensitive capability
  • sap_get_toolbar_buttonsno sensitive capability
  • sap_get_transaction_guideno sensitive capability
  • sap_get_tree_node_childrenno sensitive capability
  • sap_get_workflow_guideno sensitive capability
  • sap_handle_popupno sensitive capability
  • sap_list_connectionsno sensitive capability
  • sap_modify_cellno sensitive capability
  • sap_press_alv_toolbar_buttonno sensitive capability
  • sap_press_buttonno sensitive capability
  • sap_press_column_headerno sensitive capability
  • sap_previewno sensitive capability
  • sap_read_fieldno sensitive capability
  • sap_read_tableno sensitive capability
  • sap_read_texteditno sensitive capability
  • sap_read_treeno sensitive capability
  • sap_screenshotno sensitive capability
  • sap_scroll_table_controlno sensitive capability
  • sap_search_tree_nodesno sensitive capability
  • sap_select_all_rowsno sensitive capability
  • sap_select_all_table_control_columnsno sensitive capability
  • sap_select_alv_context_menu_itemno sensitive capability
  • sap_select_checkboxno sensitive capability
  • sap_select_combobox_entryno sensitive capability
  • sap_select_menuno sensitive capability
  • sap_select_multiple_rowsno sensitive capability
  • sap_select_radio_buttonno sensitive capability
  • sap_select_tabno sensitive capability
  • sap_select_table_rowno sensitive capability
  • sap_select_tree_nodeno sensitive capability
  • sap_send_keyno sensitive capability
  • sap_set_batch_fieldsno sensitive capability
  • sap_set_confirmation_pointsno sensitive capability
  • sap_set_current_cellno sensitive capability
  • sap_set_fieldno sensitive capability
  • sap_set_focusno sensitive capability
  • sap_set_policy_profileno sensitive capability
  • sap_set_texteditno sensitive capability

What this scan could not see

Versions 2

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.

VersionScoreFindingsEngineScanned
v0.3.0 latest A 92/100 3 1.13.0 2026-08-30
v0.2.2 A 92/100 3 1.13.0 2026-08-25

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.

MCP Trust Score: A · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-sap-gui/badge.svg)](https://mcptrustchecker.com/registry/mcp-sap-gui)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-sap-gui"><img src="https://mcptrustchecker.com/registry/mcp-sap-gui/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-sap-gui/badge.json via https://img.shields.io/endpoint?url=…

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 mcp-sap-gui --online --registry pypi

Use the free API → How scoring works

More in Productivity & Workflow