Skills/PyPI/superset-mcp-server

superset-mcp-server@0.1.0a6

VERIFIED· install only

Publisher claims: "An MCP server for Apache Superset that dynamically exposes API endpoints as tools." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher ponderedw · publishing for 462 daysInstalls 643Last detonated 56 min ago
$claude mcp add superset-mcp-server -- uvx superset-mcp-server
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
3 of 3 bundled scripts run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

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
SUPERSET_PASSWORDTOKENConfiguration, not credentials: SAFE_MODE, SUPERSET_API_URL, SUPERSET_USERNAME, TRANSPORT_TYPE
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · no network
What we could not test
use of the skill by an agent

Connect it with a scoped credential, under the guard. It asks for SUPERSET_PASSWORD, TOKEN and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --net declared -- uvx superset-mcp-server

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 (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-19 and scored it 95/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 · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.0sprocessexited 1: ModuleNotFoundError: No module named 'mcp'
0.0sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.1sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.1sprocessexited 1: ModuleNotFoundError: No module named 'requests'
0.1sprocess3 of 3 bundled scripts run with no arguments
0.1sprocessscript backend runs setup only
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

No findings across 562 lines in 9 files.

Cost to the agent

Instructions loaded
≈61 tok
1 file · 9 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

No advisories in OSV for superset-mcp-server@0.1.0a6 as of 11 min ago. This is the package itself, not its dependencies.