shanghai-library-open-data-mcp@1.3.2
VERIFIED· not startedPublisher claims: "上海图书馆开放数据 MCP 服务:纪年/家谱/建筑/红色事件/古籍/书目/诗词等开放数据的 Model Context Protocol 服务(stdio + Streamable HTTP,纯标准库零依赖)" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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
SLC_API_KEY- Where it talks to
- no vendor host named in the codeAlso sh.cn, sou-yun.cn — 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 sh.cn, sou-yun.cn as well as its own vendor. The guard injects SLC_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
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-18 and scored it 82/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 deviationsStatic findings
# 或经统一入口: python slc_mcp_server.py --transport http --port 8080Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.env_path = os.path.join(os.path.dirname(os.path.abspath(__file__)), ".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""从脚本同目录的 .env 读取 SLC_API_KEY(仅当环境变量未设置时)。Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.额外支持脚本同目录 .env 文件作为本地 Key 来源。"""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.p = subprocess.Popen([PY, "-u", "slc_mcp_server.py"],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.p = subprocess.Popen([PY, "-u", "slc_mcp_server.py"],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.纯标准库实现,零第三方依赖;.env 已被 .gitignore 忽略,不会入库泄露。"""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
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 shanghai-library-open-data-mcp@1.3.2 as of 1 h ago. This is the package itself, not its dependencies.