Skills/PyPI/wems-mcp-server

wems-mcp-server@1.13.6

VERIFIED· not started

Publisher claims: "World Event Monitoring System - MCP server for natural hazard monitoring" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher heliosarchitect · publishing for 280 daysInstalls 172Last detonated 1 h ago
$claude mcp add wems-mcp-server -- uvx wems-mcp-server
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
GITEA_TOKEN_FILESTRIPE_API_KEYSTRIPE_SECRET_KEYWEMS_API_KEYConfiguration, not credentials: WEMS_CONFIG, WEMS_LICENSE_EXPIRES, WEMS_LICENSE_TIER, WEMS_PREMIUM_KEYS, WEMS_STRIPE_BILLING_CONFIG, WEMS_STRIPE_BILLING_ENABLED
Where it talks to
wems.dev (its own)Also usgs.gov, noaa.gov, si.edu, tsunami.gov, weather.gov, arcgis.com, airnowtech.org, dhs.gov, state.gov, cisa.gov, unl.edu, stripe.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 usgs.gov, noaa.gov, si.edu, tsunami.gov, weather.gov, arcgis.com, airnowtech.org, dhs.gov, state.gov, cisa.gov, unl.edu, stripe.com as well as its own vendor. The guard injects GITEA_TOKEN_FILE, STRIPE_API_KEY, STRIPE_SECRET_KEY, WEMS_API_KEY only into requests to wems.dev (and its subdomains) and refuses the rest.

$vet-skills run --secrets GITEA_TOKEN_FILE=wems.dev,STRIPE_API_KEY=wems.dev,STRIPE_SECRET_KEY=wems.dev,WEMS_API_KEY=wems.dev -- uvx wems-mcp-server

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 89/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

MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_drought_status.py:10 · MCP server using network transport (SSE/HTTP) — data sent over networkfrom wems_mcp_server import WemsServerFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_solar.py:10 · MCP server using network transport (SSE/HTTP) — data sent over networkfrom wems_mcp_server import WemsServerFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_configure_alerts.py:8 · MCP server using network transport (SSE/HTTP) — data sent over networkfrom wems_mcp_server import WemsServerFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_space_weather_alerts.py:10 · MCP server using network transport (SSE/HTTP) — data sent over networkfrom wems_mcp_server import WemsServerFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_server.py:13 · MCP server using network transport (SSE/HTTP) — data sent over networkfrom wems_mcp_server import WemsServerFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_air_quality.py:10 · MCP server using network transport (SSE/HTTP) — data sent over networkfrom wems_mcp_server import WemsServerFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_floods.py:10 · MCP server using network transport (SSE/HTTP) — data sent over networkfrom wems_mcp_server import WemsServerFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_earthquakes.py:10 · MCP server using network transport (SSE/HTTP) — data sent over networkfrom wems_mcp_server import WemsServerFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_threat_advisories.py:10 · MCP server using network transport (SSE/HTTP) — data sent over networkfrom wems_mcp_server import WemsServerFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_severe_weather.py:10 · MCP server using network transport (SSE/HTTP) — data sent over networkfrom wems_mcp_server import WemsServerFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_hurricanes.py:10 · MCP server using network transport (SSE/HTTP) — data sent over networkfrom wems_mcp_server import WemsServerFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_confidence_fusion.py:6 · MCP server using network transport (SSE/HTTP) — data sent over networkfrom wems_mcp_server import WemsServerFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_tsunamis.py:10 · MCP server using network transport (SSE/HTTP) — data sent over networkfrom wems_mcp_server import WemsServerFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_volcanoes.py:10 · MCP server using network transport (SSE/HTTP) — data sent over networkfrom wems_mcp_server import WemsServerFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_wildfires.py:10 · MCP server using network transport (SSE/HTTP) — data sent over networkfrom wems_mcp_server import WemsServerFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
LOW
URL to a private-network addressconfig/wems_alert_config.json:37 · URL to a private-network address — a LAN or development target"webhook_url": "http://192.168.10.104:5678/webhook/wems-event",Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.
AST07

Cost to the agent

Instructions loaded
≈56 tok
1 file · 38 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 wems-mcp-server@1.13.6 as of 37 min ago. This is the package itself, not its dependencies.