vweatherstation-mcp

MCPcommunity

v1.0.3io.github.vweatherstationMITUpdated 17d agonpm GitHub

Settlement-grade market weather + general current/forecast weather for any location, via x402.

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

248Downloads/wk

17d agoLast update

Package

Authorio.github.vweatherstation

LicenseMIT

Version1.0.3

Sourcenpm+mcp-registry

npmvweatherstation-mcp

GitHubvweatherstation/vweatherstation-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

B

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface8 tools · none privileged

Security scan✓ Cleanv1.0.3 · 16d agoHow well does this scan work?

EvalsNone

IndexedSep 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

8 tools · none privileged

Statically extracted from the published packagev1.0.3 · 16d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

get_weatherGeneral current weather and 7-day forecast for ANY latitude/longitude: temperature, feels-like, humidity, pressure, wind speed/gust/direction, precipitation, UV, sunrise/sunset and solar radiation. The everyday weather endpoint (not tied to prediction markets). $0.02/call.

General current weather and 7-day forecast for ANY latitude/longitude: temperature, feels-like, humidity, pressure, wind speed/gust/direction, precipitation, UV, sunrise/sunset and solar radiation. The everyday weather endpoint (not tied to prediction markets). $0.02/call.

No input schema was published for this tool.

get_temperatureSettlement-grade temperature at the exact stations Polymarket/Kalshi temperature markets resolve on (KNYC Central Park, EGLL Heathrow, etc.). Current temp, today's high/low (settlement number), forecast. $0.05/call.

Settlement-grade temperature at the exact stations Polymarket/Kalshi temperature markets resolve on (KNYC Central Park, EGLL Heathrow, etc.). Current temp, today's high/low (settlement number), forecast. $0.05/call.

No input schema was published for this tool.

get_all_market_weatherALL weather-market metrics for a city in one call: temperature, rain, wind, snow at the settlement station. The complete feed for prediction-market traders. $0.08/call.

ALL weather-market metrics for a city in one call: temperature, rain, wind, snow at the settlement station. The complete feed for prediction-market traders. $0.08/call.

No input schema was published for this tool.

get_rainRainfall at prediction-market settlement stations. Today's total + 7-day forecast. $0.04/call.

Rainfall at prediction-market settlement stations. Today's total + 7-day forecast. $0.04/call.

No input schema was published for this tool.

get_windWind speed and max gust at settlement stations, from live METAR. $0.04/call.

Wind speed and max gust at settlement stations, from live METAR. $0.04/call.

No input schema was published for this tool.

get_snowSnowfall at settlement stations. Today's total + 7-day forecast. $0.04/call.

Snowfall at settlement stations. Today's total + 7-day forecast. $0.04/call.

No input schema was published for this tool.

get_hurricanesActive tropical cyclones with NHC classification, category, position and intensity — the settlement source for hurricane markets. $0.05/call.

Active tropical cyclones with NHC classification, category, position and intensity — the settlement source for hurricane markets. $0.05/call.

No input schema was published for this tool.

get_forecast_confidenceMulti-model forecast confidence score (0-100) for a lat/lon, with per-day breakdown. How much to trust the forecast. $0.01/call.

Multi-model forecast confidence score (0-100) for a lat/lon, with per-day breakdown. How much to trust the forecast. $0.01/call.

No input schema was published for this tool.

8 of 8 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Settlement-grade market weather + general current/forecast weather for any location, via x402.

Keywords

mcp

Alternatives

Comparing tool surfaces…

Tools exposed

8 tools · none privileged · observed 2026-09-26 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

get_weather
get_temperature
get_all_market_weather
get_rain
get_wind
get_snow
get_hurricanes
get_forecast_confidence

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-26 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

viem2.56.98 dependencies
- ox0.14.45+4 not drawn4 dependencies
  - @scure/bip321.7.0+2 not drawn1 dependency
    @noble/hashes1.8.0
  - @scure/bip391.6.0+1 not drawn1 dependency
    @noble/hashes1.8.0shown above
  - @noble/curves1.9.11 dependency
    @noble/hashes1.8.0shown above
  - @noble/hashes1.8.0shown above
- ws8.21.0
- isows1.0.7
- abitype1.2.3
- @scure/bip321.7.0shown above+2 not drawn
- @scure/bip391.6.0shown above+1 not drawn
- @noble/curves1.9.1shown above
- @noble/hashes1.8.0shown above
x402-fetch0.6.63 dependencies
- zod3.25.76
- viem2.56.9shown above
- x4020.6.6+7 not drawn2 dependencies
  - zod3.25.76shown above
  - viem2.56.9shown above
@modelcontextprotocol/sdk1.30.1+6 not drawn11 dependencies
- ajv8.20.0+4 not drawn
- zod4.6.5
- cors2.8.6+2 not drawn
- hono4.13.9
- jose6.2.12
- express5.2.1incomplete+19 not drawn
- raw-body3.0.2incomplete
- ajv-formats3.0.1incomplete
- cross-spawn7.0.6incomplete
- eventsource3.0.7incomplete
- content-type1.0.5

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

83 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 83

statuses ^2.0.1 — required by express@5.2.1package cap reached
encodeurl ^2.0.0 — required by express@5.2.1package cap reached
mime-types ^3.0.0 — required by express@5.2.1package cap reached
proxy-addr ^2.0.7 — required by express@5.2.1package cap reached
body-parser ^2.2.1 — required by express@5.2.1package cap reached
escape-html ^1.0.3 — required by express@5.2.1package cap reached
http-errors ^2.0.0 — required by express@5.2.1package cap reached
on-finished ^2.4.1 — required by express@5.2.1package cap reached
content-type ^1.0.5 — required by express@5.2.1package cap reached
finalhandler ^2.1.0 — required by express@5.2.1package cap reached
range-parser ^1.2.1 — required by express@5.2.1package cap reached
serve-static ^2.2.0 — required by express@5.2.1package cap reached

+71 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.