weatherwork-consumer-mcp@0.3.4
VERIFIED· not startedPublisher claims: "WeatherWork Consumer MCP Server — 基于 weathercn API 的消费者天气工具集" 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
WEATHERCN_API_KEYWEATHERCN_API_SECRETWEATHERCN_OPENAPI_KEYConfiguration, not credentials: WEATHERCN_DOMAIN, WEATHERCN_OPENAPI_DOMAIN, WEATHERCN_PROTOCOL, WEATHERWORK_SKIP_VSCODE_AUTO_SYNC- Where it talks to
- no vendor host named in the codeAlso weathercn.com — not the publisher's domain; check what for before connecting.
- 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, and read the third-party hosts first. The code names weathercn.com as well as its own vendor. The guard injects WEATHERCN_API_KEY, WEATHERCN_API_SECRET, WEATHERCN_OPENAPI_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-21 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 deviationsStatic findings
"envFile": "${workspaceFolder}/.env.mcp.local",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose._ENV_REL = Path(".env.mcp.local")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose." 2. 配置密钥:复制 .env.mcp.local.example → .env.mcp.local",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."[weatherwork-consumer-mcp] 提示:尚未发现 .env.mcp.local,请配置 WEATHERCN_OPENAPI_KEY。"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 weatherwork-consumer-mcp@0.3.4 as of 54 min ago. This is the package itself, not its dependencies.