zheng-mcp-gaodeweather-server

MCP server that provides Gaode (AMap) weather functionality to agents via Model Context Protocol tools (exact weather endpoints/fields are not provided in the supplied prompt).

Evaluated Apr 04, 2026 (17d ago)
Homepage ↗ Ai Ml mcp weather amap gaode tooling api-wrapper agent-integration
⚙ Agent Friendliness
36
/ 100
Can an agent use this?
🔒 Security
38
/ 100
Is it safe for agents?
⚡ Reliability
6
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
35
Error Messages
0
Auth Simplicity
40
Rate Limits
20

🔒 Security

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

No repository code/logs were provided in the prompt, so security properties (TLS enforcement, secret handling, dependency CVE hygiene, and auth scope granularity) cannot be verified. Scores are conservative due to missing evidence.

⚡ Reliability

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

Best When

You have an agent runtime that can connect to an MCP server and you want weather data as a tool.

Avoid When

You need strict compliance guarantees, strong auth controls, or well-documented operational limits not evidenced by the provided information.

Use Cases

  • • Agent-driven weather lookups for a given location
  • • Augmenting chat/agent responses with localized weather context
  • • Building workflows that react to weather (e.g., travel planning)

Not For

  • • High-volume production weather data pipelines without rate/usage documentation
  • • Use as a general-purpose data platform beyond weather queries

Interface

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

Authentication

Methods: Unverified from provided prompt; MCP likely requires configuration/env vars
OAuth: No Scopes: No

The supplied content does not include auth details (e.g., API key mechanism, whether requests are signed, or whether users manage credentials). Score reflects lack of evidence, not confirmed insecure design.

Pricing

Free tier: No
Requires CC: No

No pricing/billing information provided in the prompt.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • ⚠ Weather APIs commonly have rate limits and location/address normalization requirements; if the MCP server does not surface provider errors clearly, the agent may misinterpret failures.
  • ⚠ Agents may retry automatically; without documented retry/idempotency semantics this can amplify rate-limit pressure.

Alternatives

Direct calls to a weather API (e.g., AMap/AMap Weather API or other providers) from your application Use an existing weather SDK/library for your language/runtime Build a thin MCP wrapper around the provider’s documented REST API with your own auth/rate-limit handling

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for zheng-mcp-gaodeweather-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
API endpoint ↗ Agent guide ↗ Report inaccuracy

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

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