Sap Datasphere (MarioDeFelipe) MCP Server

sap-datasphere-mcp PyPI v2.0.3

Published by mariodefelipe — 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.

Model Context Protocol server for SAP Datasphere — 48 tools, Streamable HTTP, and built-in config-driven PII/sensitive-field masking (fail-closed, audit-logged).

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/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 = 93/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 − 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:

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

high Shell/command execution in server code (sap_datasphere_mcp_server.py)MTC-SRC-002

In the server's implementation (`sap_datasphere_mcp_server.py:3187`): 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: result = subprocess.run( ["datasphere", "dbusers", "list", "--space", space_id],

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 sap_datasphere_mcp_server.py

low Shell/command execution in packaging/dev tooling (tests/test_no_live_tenant_data.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_no_live_tenant_data.py:158`): 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: bprocess tracked = subprocess.run( ["git", "ls-files"], cwd=REPO, capture_output=True, text=True ).stdo

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_no_live_tenant_data.py

low Shell/command execution in packaging/dev tooling (tests/test_sdk_v2_protocol.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_sdk_v2_protocol.py:214`): 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: ckname()[1] proc = subprocess.Popen( [sys.executable, "-m", "sap_datasphere_mcp_server", "--transp

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_sdk_v2_protocol.py

Tools 49

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

  • browse_marketplaceingests untrusted input
  • execute_queryreads sensitive data
  • list_repository_objectsingests untrusted input
  • analyze_column_distributionno sensitive capability
  • create_database_userno sensitive capability
  • delete_database_userno sensitive capability
  • find_assets_by_columnno sensitive capability
  • get_analytical_metadatano sensitive capability
  • get_analytical_modelno sensitive capability
  • get_analytical_service_documentno sensitive capability
Show 39 more tools ↓
  • get_asset_by_compound_keyno sensitive capability
  • get_asset_detailsno sensitive capability
  • get_asset_variablesno sensitive capability
  • get_available_scopesno sensitive capability
  • get_catalog_metadatano sensitive capability
  • get_consumption_metadatano sensitive capability
  • get_current_userno sensitive capability
  • get_deployed_objectsno sensitive capability
  • get_object_definitionno sensitive capability
  • get_relational_entity_metadatano sensitive capability
  • get_relational_metadatano sensitive capability
  • get_relational_odata_serviceno sensitive capability
  • get_repository_search_metadatano sensitive capability
  • get_space_assetsno sensitive capability
  • get_space_infono sensitive capability
  • get_table_schemano sensitive capability
  • get_task_historyno sensitive capability
  • get_task_logno sensitive capability
  • get_task_statusno sensitive capability
  • get_tenant_infono sensitive capability
  • list_analytical_datasetsno sensitive capability
  • list_catalog_assetsno sensitive capability
  • list_connectionsno sensitive capability
  • list_database_usersno sensitive capability
  • list_relational_entitiesno sensitive capability
  • list_spacesno sensitive capability
  • query_analytical_datano sensitive capability
  • query_relational_entityno sensitive capability
  • reset_database_user_passwordno sensitive capability
  • run_task_chainno sensitive capability
  • search_catalogno sensitive capability
  • search_repositoryno sensitive capability
  • search_tablesno sensitive capability
  • smart_queryno sensitive capability
  • test_analytical_endpointsno sensitive capability
  • test_connectionno sensitive capability
  • test_phase67_endpointsno sensitive capability
  • test_phase8_endpointsno sensitive capability
  • update_database_userno sensitive capability

What this scan could not see

Versions 5

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
v2.0.3 latest A 93/100 3 1.13.0 2026-08-25
v2.0.2 A 93/100 2 1.12.1 2026-08-12
v2.0.1 A 93/100 2 1.12.1 2026-08-09
v1.5.2 A 93/100 1 1.12.1 2026-07-31
v1.5.1 A 93/100 1 1.12.1 2026-07-27

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 · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/sap-datasphere-mcp/badge.svg)](https://mcptrustchecker.com/registry/sap-datasphere-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/sap-datasphere-mcp"><img src="https://mcptrustchecker.com/registry/sap-datasphere-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/sap-datasphere-mcp/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 sap-datasphere-mcp --online --registry pypi

Use the free API → How scoring works

Other implementations of Sap Datasphere 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Business & CRM