Skills/PyPI/sap-datasphere-mcp

sap-datasphere-mcp@2.0.3

VERIFIED· not started

Publisher claims: "Model Context Protocol server for SAP Datasphere — MCP SDK v2 / 2026-07-28 stateless spec, Streamable HTTP, per-asset capability discovery, and config-driven PII masking (fail-closed, audit-logged)." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher mariodefelipe · publishing for 397 daysInstalls 548Last detonated 1 h ago
$claude mcp add sap-datasphere-mcp -- uvx sap-datasphere-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
DATASPHERE_CLIENT_SECRETDATASPHERE_TOKEN_URLConfiguration, not credentials: DATASPHERE_BASE_URL, DATASPHERE_CLIENT_ID, DATASPHERE_PII_MODE, DATASPHERE_PII_POLICY, DATASPHERE_PII_SALT, MCP_ENVIRONMENT
Where it talks to
no vendor host named in the codeAlso sap.com, oasis-open.org, cloud.sap, ailien.studio, company.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names sap.com, oasis-open.org, cloud.sap, ailien.studio, company.com as well as its own vendor. The guard injects DATASPHERE_CLIENT_SECRET, DATASPHERE_TOKEN_URL only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx sap-datasphere-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-16 and scored it 85/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 3 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
0.0sprocessexited 1: ModuleNotFoundError: No module named 'setuptools'
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.2sprocessscript backend runs setup only
0.2sprocesssecond launch, clock +45 days, CI unset
0.2sprocessexited 1: ModuleNotFoundError: No module named 'setuptools'

Static findings

HIGH
Access to sensitive file pathsdatasphere_connector.py:824 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files+ ". Copy .env.example and fill in your own tenant's values."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathspyproject.toml:114 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"*" = ["*.md", "*.txt", "*.env.example", "*.yaml", "*.yml"]Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdatasphere_connector.py:812 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesand DATASPHERE_TOKEN_URL (see .env.example).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup.py:62 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"": ["*.md", "*.txt", ".env.example"],Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
File permission modification commandDockerfile:50 · File permission modification command — agent changes file ownership/permissionschown -R mcpuser:mcpuser /appFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
Access to sensitive file pathstests/README.md:252 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files**Solution**: Ensure `.env` file contains all required OAuth credentialsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathsdocker-compose.yml:14 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathsdocker-compose.yml:24 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- ./.env:/app/.env:ro # Read-only mount of .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/README.md:33 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesCreate a `.env` file with OAuth credentials:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathsDockerfile:30 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesCOPY .env.example .Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Destructive file system command detectedDockerfile:18 · Destructive file system command detected&& rm -rf /var/lib/apt/lists/*Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Access to sensitive file pathstests/conftest.py:17 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Load environment variables from .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathsdocker-compose.yml:12 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Environment variables from .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈89 tok
1 file · 81 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for sap-datasphere-mcp@2.0.3 as of 51 min ago. This is the package itself, not its dependencies.