tc-weather-mcp-server

tc-weather-mcp-server is an MCP server intended to provide weather-related capabilities (typically backed by an external weather provider) to AI agents via the Model Context Protocol.

Evaluated Apr 04, 2026 (20d ago)
Homepage ↗ Repo ↗ Infrastructure mcp weather tooling ai-agents data-integration
⚙ Agent Friendliness
42
/ 100
Can an agent use this?
🔒 Security
46
/ 100
Is it safe for agents?
⚡ Reliability
28
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
35
Error Messages
0
Auth Simplicity
60
Rate Limits
25

🔒 Security

TLS Enforcement
70
Auth Strength
40
Scope Granularity
30
Dep. Hygiene
40
Secret Handling
50

Security posture cannot be fully assessed from the provided info. If it relies on external weather APIs, it should enforce HTTPS, keep API keys in environment variables, and avoid logging secrets; none of these are confirmed here.

⚡ Reliability

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

Best When

You need a lightweight MCP tool to fetch weather data inside an agent environment.

Avoid When

You require strict uptime/SLA, guaranteed response latency, or strong compliance/data residency guarantees that are not documented.

Use Cases

  • Let an AI assistant answer weather questions for a given location
  • Agent workflows that need current conditions or forecasts (e.g., planning outdoor activities)
  • Tool-using agents that need structured weather data in conversational flows

Not For

  • Use as a general-purpose weather data portal with complex querying unless explicitly supported
  • Mission-critical forecasting without validating source accuracy
  • High-compliance/regulated applications without confirmed vendor and data handling details

Interface

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

Authentication

OAuth: No Scopes: No

No auth details were provided in the supplied information, so authentication requirements (if any) cannot be confirmed.

Pricing

Free tier: No
Requires CC: No

No pricing information was provided in the supplied information.

Agent Metadata

Pagination
none
Idempotent
True
Retry Guidance
Not documented

Known Gotchas

  • Weather providers can rate-limit; agents should expect transient failures/429s and retry with backoff (not confirmed/documented).
  • Location inputs (city name vs coordinates) may be ambiguous; agents may need to pass lat/lon or disambiguate.

Alternatives

Full Evaluation Report

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

$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