zhangyuepeng-mcp-weather-server

An MCP weather server that provides weather-related data/functions to AI agents via the Model Context Protocol, likely backed by an external weather provider API.

Evaluated Apr 04, 2026 (17d ago)
Homepage ↗ Infrastructure mcp weather api-integration ai-tools tooling
⚙ Agent Friendliness
34
/ 100
Can an agent use this?
🔒 Security
39
/ 100
Is it safe for agents?
⚡ Reliability
25
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
35
Documentation
30
Error Messages
0
Auth Simplicity
50
Rate Limits
20

🔒 Security

TLS Enforcement
60
Auth Strength
40
Scope Granularity
20
Dep. Hygiene
35
Secret Handling
40

No repository details were provided (e.g., TLS enforcement, auth method, logging behavior). Weather servers commonly use external API keys; secret handling and logging practices cannot be verified from the available input.

⚡ Reliability

Uptime/SLA
0
Version Stability
40
Breaking Changes
30
Error Recovery
30
AF Security Reliability

Best When

You want an MCP tool that weather-capable agents can call at runtime to fetch location-specific weather details.

Avoid When

You require strong contractual guarantees (SLA, versioning guarantees) or you need enterprise-grade security controls explicitly documented (e.g., audit logs, formal auth).

Use Cases

  • Agent-assisted retrieval of current weather or forecasts for a given location
  • Building chat/assistant experiences that answer weather questions
  • Automation workflows that need weather context (e.g., travel planning, alerting)

Not For

  • High-assurance, compliance-heavy decisioning without validation of data sources
  • Use as a general-purpose data platform beyond weather use cases

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

Authentication requirements are not provided in the supplied information.

Pricing

Free tier: No
Requires CC: No

Pricing information not provided.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Weather APIs often require an API key and may have quota/rate limits; agents may need to throttle or retry carefully.
  • Location/address formats can be ambiguous; agents may need to normalize inputs (city names vs lat/long).
  • Forecast endpoints may differ in units/time ranges; agents should request explicitly (e.g., units, timeframe).

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for zhangyuepeng-mcp-weather-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

$3

Score Monitoring

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

Continuous monitoring

$3/mo

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

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered