weatherinfohttpstreammcpserver

A named MCP server package intended to provide weather information via the Model Context Protocol (MCP), likely by streaming HTTP responses from an external weather source and exposing them as MCP tools to an agent.

Evaluated Apr 04, 2026 (17d ago)
Homepage ↗ API Gateway mcp weather http ai-agents tooling
⚙ Agent Friendliness
28
/ 100
Can an agent use this?
🔒 Security
32
/ 100
Is it safe for agents?
⚡ Reliability
21
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
30
Documentation
20
Error Messages
0
Auth Simplicity
60
Rate Limits
10

🔒 Security

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

No documentation/details were provided about how authentication, API keys, TLS, or secret handling are implemented in this MCP server. If it proxies to an external weather API, ensure upstream keys are stored securely and not logged; ensure HTTPS is enforced end-to-end and that agent-visible errors do not leak credentials.

⚡ Reliability

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

Use Cases

  • Agent-driven weather lookups for chatbots or automation workflows
  • Real-time or near-real-time weather data retrieval during tasks (e.g., planning, routing)
  • Building agent toolchains that need weather context without writing custom HTTP integration logic

Not For

  • High-assurance or regulated meteorological forecasting use where audit-grade provenance is required
  • Environments that require strict compliance guarantees (not stated)
  • Use cases needing authentication/authorization to be handled by the provider (not described)

Interface

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

Authentication

OAuth: No Scopes: No

Pricing

Free tier: No
Requires CC: No

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Weather lookups may be dependent on external HTTP APIs; failures or rate limits from the upstream provider may surface to the agent
  • “Streaming” responses can be harder for agents to parse deterministically if the MCP tool returns partial chunks without a clear final schema
  • If the MCP tool expects specific input formats (city, lat/lon, units), agents may frequently send mismatched parameters unless the tool schema is explicit

Alternatives

Full Evaluation Report

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

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