weatherstack-mcp-server

An MCP (Model Context Protocol) server intended to provide Weatherstack-based weather lookup capabilities to AI agents (e.g., fetch current conditions/forecasts for locations) via MCP tool calls.

Evaluated Apr 04, 2026 (17d ago)

Homepage ↗ API Gateway mcp weather data-integration api-wrapper ai-agents

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Likely uses a Weatherstack API key for upstream access, but the provided material does not confirm how secrets are stored/loaded or whether MCP transport is secured end-to-end. Scope granularity and secret-handling practices cannot be verified from the prompt.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Use Cases

• Agent-driven weather Q&A for specific locations
• Automating workflows that need current weather (e.g., triage, routing, scheduling assistance)
• Building an agent tool that wraps Weatherstack API data with structured responses

Not For

• Security-sensitive decisioning without additional validation (e.g., safety-critical automation)
• Use cases requiring high-assurance, auditable weather sourcing
• Clients that need REST/GraphQL/SDK-only integrations (without MCP support)

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: Weatherstack API key (typical for Weatherstack)

OAuth: No Scopes: No

Auth mechanism for the MCP server itself is not provided in the supplied data. Weatherstack-style API key usage is likely, but exact implementation details are unknown from the prompt.

Pricing

Free tier: No

Requires CC: No

Pricing not provided. If backed by Weatherstack, cost depends on Weatherstack plan and request volume.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Weather/forecast APIs are often rate-limited and may require retries with backoff; without documented retry/idempotency behavior, agents may fail on transient 429/5xx responses.
⚠ Location ambiguity (city names) can lead to unexpected results unless the tool accepts/returns deterministic location identifiers.
⚠ If the MCP server lacks structured output contracts, agents may need defensive parsing.

Alternatives

Weatherstack official API directly (REST) Other weather APIs with SDKs (e.g., Open-Meteo, WeatherAPI.com) Generic MCP wrappers around REST weather endpoints

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for weatherstack-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.