Skills/PyPI/qweather-mcp

qweather-mcp@0.2.12

VERIFIED· not started

Publisher claims: "和风天气查询API服务,支持MCP接口可被AI助手直接调用" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher zishu.co-huqi1024 · publishing for 544 daysInstalls 72Last detonated 13 min ago
$claude mcp add qweather-mcp -- uvx qweather-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
TOKEN_CACHE_ENABLEDWEATHER_BEARER_TOKENWEATHER_PRIVATE_KEYConfiguration, not credentials: JWT_DEFAULT_EXPIRY, WEATHER_API_HOST, WEATHER_KEY_ID, WEATHER_PROJECT_ID
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 TOKEN_CACHE_ENABLED, WEATHER_BEARER_TOKEN, WEATHER_PRIVATE_KEY 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 qweather-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-15 and scored it 88/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.2sprocessdependency install exit 1 ·
0.2sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.2sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsqweather_mcp/config.py:3 · 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 pathsqweather_mcp/config.py:10 · 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

Cost to the agent

Instructions loaded
≈44 tok
1 file · 9 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

Not checked against OSV yet; the weekly check has not reached this version.