Skills/PyPI/mcp-yashan

mcp-yashan@2.1.0

VERIFIED· not started

Publisher claims: "MCP Server for YashanDB - Connect AI assistants to YashanDB databases" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher yourusername · publishing for 711 daysInstalls 17Last detonated 4d ago
$claude mcp add mcp-yashan -- uvx mcp-yashan
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
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
DB_PASSWORDConfiguration, not credentials: DB_HOST, DB_JDBC_URL, DB_NAME, DB_PORT, DB_USER, JAVA_HOME, SQL_TIMEOUT, YASHAN_JAVA_HOME, YASHAN_JDBC_JAR
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
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for DB_PASSWORD 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 mcp-yashan

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; not started: dependency install failed; the server itself was not observed) on 2026-11-10 and scored it 87/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.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsmcp_yashan/core/executor.py:73 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesPath.cwd() / ".env",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 pathsmcp_yashan/mcp_server.py:12 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files通过 .env 文件配置数据库连接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 pathsmcp_yashan/core/executor.py:69 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""从项目根目录加载 .env"""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 pathsmcp_yashan/core/executor.py:31 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# 项目根目录（用于查找 .env）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 pathsmcp_yashan/http_server.py:44 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv_file = os.path.join(os.path.dirname(os.path.dirname(__file__)), ".env")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 pathsmcp_yashan/core/executor.py:74 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesPath.home() / ".mcp_yashan" / ".env",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 pathsmcp_yashan/http_server.py:43 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""加载 .env 文件"""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 pathsmcp_yashan/core/executor.py:72 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesPROJECT_ROOT / ".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Python subprocess execution detectedmcp_yashan/core/executor.py:186 · Python subprocess execution detectedresult = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

Cost to the agent

Instructions loaded
≈53 tok
1 file · 28 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 mcp-yashan@2.1.0 as of 4d ago. This is the package itself, not its dependencies.