Skills/PyPI/tiangong-mcp

tiangong-mcp@0.1.19

VERIFIED· not started

Publisher claims: "TianGong MCP - The Celestial Forge for AI Agents." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher jinning6 · publishing for 253 daysInstalls 52Last detonated 6 h ago
$claude mcp add tiangong-mcp -- uvx tiangong-mcp
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
GITHUB_TOKENConfiguration, not credentials: CYBERHUATUO_ENABLED, GITHUB_STEP_SUMMARY, GITHUB_USERNAME, NOOSPHERE_ENABLED, TIANGONG_AUTO_INSTALL, TIANGONG_CAVE_DIR, TIANGONG_DATA_DIR, TIANGONG_PYTHON_ENV, TIANGONG_REPO_NAME, TIANGONG_REPO_OWNER
Where it talks to
no vendor host named in the code
What we saw when it ran
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 GITHUB_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 tiangong-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 (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-19 and scored it 86/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 pathstiangong/config.py:11 · 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 pathstiangong/ecosystem.py:23 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesreturn "⚠️ 赛博华佗联动未启用。请在 .env 中设置 CYBERHUATUO_ENABLED=true"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Python subprocess execution detected.github/scripts/run_pytest_with_annotations.py:60 · Python subprocess execution detectedresult = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
LOW
Role reassignment attemptREADME.md:198 · Role reassignment attempt · informational: not an instruction fileThat's it. You are now a cultivator.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
MEDIUM
Python subprocess execution detectedtiangong/launch_assets.py:344 · Python subprocess execution detectedresult = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
HIGH
Access to sensitive file pathstiangong/ecosystem.py:53 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesreturn "⚠️ Noosphere 联动未启用。请在 .env 中设置 NOOSPHERE_ENABLED=true"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 pathstiangong/marketplace.py:331 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# 5. 检查 .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 pathstiangong/marketplace.py:332 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv_example = target_dir / ".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 pathstiangong/marketplace.py:337 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesf"请检查 `{target_dir}/.env.example` 并创建 `.env` 文件配置所需 API Key。"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 pathstiangong/mcp_server.py:1781 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"- 补全配置: 在 `.env` 配置 `GITHUB_TOKEN` 后重试公开命令",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 pathstiangong/marketplace.py:192 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"飞升上界需要 GitHub Token。请在 `.env` 中配置 GITHUB_TOKEN。"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 pathstiangong/mcp_server.py:1937 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"- 补全配置: 在 `.env` 配置 `GITHUB_TOKEN` 后重试验收",Fix: 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
≈49 tok
1 file · 77 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 tiangong-mcp@0.1.19 as of 6 h ago. This is the package itself, not its dependencies.