mcp-server-tempest@0.12.0
VERIFIED· not startedPublisher claims: "MCP Server for Retrieving Tempest Weather Data" 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
WEATHERFLOW_API_TOKENConfiguration, not credentials: WEATHERFLOW_DISK_CACHE_TTL- Where it talks to
- no vendor host named in the codeAlso tempestwx.com — 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 tempestwx.com as well as its own vendor. The guard injects WEATHERFLOW_API_TOKEN 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-09 and scored it 85/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
…licitly and names residual risks (e.g., "bypass-actors probe could not be run — admin access unavailable" or "no live Actions run logs were inspected for secret exposure").…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.return subprocess.run([sys.executable, str(SCRIPT), *args], capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.chmod is a harmless best-effort.Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.patch("mcp_server_tempest.rest.aiohttp.ClientSession", return_value=mock_session),Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them."""Committed manifest.json byte-equals the generator output (regenerate andFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.result = disk_cache.get("../../etc/passwd", SampleModel)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.'(^|/)(\.env$|\.git/|\.github/|\.venv/|tests/|docs/|scripts/|Makefile$|prek\.toml$|NOTES\.md$|__pycache__/|\.coverage$|\.pytest_cache/|\.ruff_cache/)'; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…log excerpt — not in impressions. Where evidence is unavailable (e.g., you lack admin access to view ruleset bypass lists, or a feature is not applicable to the plan tier),…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.disk_cache.set("../../etc/passwd", model)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.the committed ``manifest.json`` matches this generator's output, so regenerateFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.by older versions may be world-readable, so we chmod explicitly. ThisFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.If the cache dir is itself a symlink we refuse to operate on it: chmodFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts."sk_live_4ec39hqlyjwdarjtt1zd",Fix: Never read or enumerate credential locations; accept a documented environment variable instead.- **`not-checked`** with a reason (e.g., "admin access not available," "no GitHub Actions configured," "private repo — requirement does not apply").Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.In a monorepo, add a nested `AGENTS.md` per subtree with meaningfully different rules.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…d` may use a different syntax — check the tool's documentation). In a monorepo, add a nested `AGENTS.md` per subtree that has meaningfully different branching, testing, or off-limits …Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.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 mcp-server-tempest@0.12.0 as of 5d ago. This is the package itself, not its dependencies.