Virga Weather
NPM · @VIRGA-MCP/SERVER · SCANNED SEP 25
Weather API tools — current, hourly, daily forecasts, and historical data.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 206 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 964 tokens (~48/item across 20 items; 14 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "revoke_api_key" implies "revoke" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Virga Weather MCP server?
Virga Weather runs locally as an npm package, launched with npx -y @virga-mcp/server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @virga-mcp/server
claude mcp add mcmurrym-virga-weather -- npx -y @virga-mcp/server
{
"mcpServers": {
"mcmurrym-virga-weather": {
"command": "npx",
"args": [
"-y",
"@virga-mcp/server"
]
}
}
} {
"servers": {
"mcmurrym-virga-weather": {
"command": "npx",
"args": [
"-y",
"@virga-mcp/server"
]
}
}
} codex mcp add mcmurrym-virga-weather -- npx -y @virga-mcp/server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mcmurrym-virga-weather": {
"type": "local",
"command": [
"npx",
"-y",
"@virga-mcp/server"
],
"enabled": true
}
}
} openclaw mcp add mcmurrym-virga-weather --command npx --arg -y --arg @virga-mcp/server
mcp_servers:
mcmurrym-virga-weather:
command: "npx"
args: ["-y", "@virga-mcp/server"] {
"McpServers": {
"mcmurrym-virga-weather": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@virga-mcp/server"
]
}
}
} assistant mcp add mcmurrym-virga-weather -t stdio -c npx -a -y @virga-mcp/server
{
"mcpServers": {
"mcmurrym-virga-weather": {
"command": "npx",
"args": [
"-y",
"@virga-mcp/server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 −4
- Stability: pass → 0.77 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/@virga-mcp/server@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
accept_terms ~49
Accept the Virga Weather API terms of service. Required before creating production keys.
| Name | Type | Req | Description |
|---|---|---|---|
| version | string | yes | Terms version to accept (get the current version from get_terms or the weather://terms resource) |
No output schema declared.
No examples provided.
activate_billing ~37
Set up a payment method via Stripe. Returns a checkout URL that must be opened in a browser to complete setup. Required before purchasing credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_account ~51
Create a new Virga Weather API account. Returns a stage API key for testing. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name for your account or agent (e.g. 'my-weather-bot') |
No output schema declared.
No examples provided.
create_api_key ~83
Create a new API key. Production keys require accepted terms, activated billing, and positive credit balance.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | Key environment: 'stage' (free, lower limits) or 'production' (uses credits, higher limits). Default: stage. |
| name | string | yes | Descriptive name for the key (e.g. 'production-bot') |
No output schema declared.
No examples provided.
get_billing_status ~27
Get current billing status including credit balance, spend caps, and auto-topup configuration.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_current_weather ~55
Get current weather conditions for a location. Returns temperature, humidity, wind, precipitation, and conditions.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude (-90 to 90) |
| lon | number | yes | Longitude (-180 to 180) |
No output schema declared.
No examples provided.
get_daily_forecast ~74
Get daily weather forecast for a location. Returns up to 16 days of forecast data.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Number of days to forecast (1-16, default 7) |
| lat | number | yes | Latitude (-90 to 90) |
| lon | number | yes | Longitude (-180 to 180) |
No output schema declared.
No examples provided.
get_historical_weather ~90
Get historical weather data for a location on a specific date. Returns temperature, humidity, wind, and conditions for that date.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date to retrieve weather for (ISO 8601 format, e.g. 2026-01-15) |
| lat | number | yes | Latitude (-90 to 90) |
| lon | number | yes | Longitude (-180 to 180) |
No output schema declared.
No examples provided.
get_hourly_forecast ~75
Get hourly weather forecast for a location. Returns up to 120 hours of forecast data.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | Number of hours to forecast (1-120, default 24) |
| lat | number | yes | Latitude (-90 to 90) |
| lon | number | yes | Longitude (-180 to 180) |
No output schema declared.
No examples provided.
get_usage ~64
Get API usage history for the account. Shows endpoint calls, credit costs, and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | – | End date for usage query (ISO 8601 format) |
| startDate | string | – | Start date for usage query (ISO 8601 format) |
No output schema declared.
No examples provided.
list_api_keys ~30
List all API keys for the account. Shows key prefix, environment, status, and last used timestamp.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
purchase_credits ~76
Purchase a credit bundle. Returns a Stripe checkout URL to complete the purchase. Bundles: 500 credits ($5), 2000 ($18), 10000 ($75).
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | string | yes | Credit bundle size: '500' ($5), '2000' ($18), or '10000' ($75) |
No output schema declared.
No examples provided.
revoke_api_key ~54
Revoke an API key. WARNING: This is a destructive operation — the key will immediately stop working and cannot be restored.
| Name | Type | Req | Description |
|---|---|---|---|
| keyId | string | yes | ID of the key to revoke (get from list_api_keys) |
No output schema declared.
No examples provided.
search_location ~71
Geocode a place name to latitude/longitude coordinates. Use this to convert city names, addresses, or landmarks into coordinates for weather queries.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Place name, city, or address to geocode (e.g. "New York", "Tokyo, Japan", "1600 Pennsylvania Ave") |
No output schema declared.
No examples provided.
What is the Virga Weather MCP server?
Virga Weather is an MCP server listed in the public MCP registry as io.github.mcmurrym/virga-weather. Weather API tools, current, hourly, daily forecasts, and historical data. This page covers its npm package (@virga-mcp/server).
Is the Virga Weather MCP server safe to use?
Virga Weather scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Virga Weather MCP server expose?
Virga Weather exposes 14 tools: get_current_weather, get_hourly_forecast, get_daily_forecast, get_historical_weather, search_location, and 9 more. Their descriptions and schemas cost roughly 836 tokens of context every time the server is loaded.
Is the Virga Weather MCP server still maintained?
Virga Weather is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Virga Weather MCP server under?
Virga Weather declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.