mcpServer

Provides an MCP server implementation (based on mcp-go) that currently exposes weather-related capabilities backed by the HeFeng (和风天气) API. Includes a custom JSON unmarshal approach to transfer annotation tags into each result field's description to improve AI interpretability of responses.

Evaluated Apr 04, 2026 (16d ago)
Repo ↗ Ai Ml mcp mcp-server weather go sse stdio ai-tools
⚙ Agent Friendliness
39
/ 100
Can an agent use this?
🔒 Security
25
/ 100
Is it safe for agents?
⚡ Reliability
19
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

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

🔒 Security

TLS Enforcement
20
Auth Strength
20
Scope Granularity
0
Dep. Hygiene
40
Secret Handling
50

README does not document whether SSE endpoints use TLS, how private_key.pem is protected, or whether clients must authenticate. It also does not describe how errors are sanitized/logged or how secrets are handled at runtime. Using HTTP SSE on localhost is low risk but still not explicitly secured; verify transport security and access control in implementation.

⚡ Reliability

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

Best When

You want a lightweight MCP weather tool for local or LAN/localhost agent setups and can supply the required config and private key files.

Avoid When

You need fine-grained authentication/authorization, documented rate limits, or enterprise-ready operational/reliability documentation.

Use Cases

  • Letting an AI agent query weather data via MCP tool calls
  • Embedding a weather tool into agent workflows using local stdio or remote SSE transport
  • Improving LLM consumption of structured tool results through enriched descriptions

Not For

  • General-purpose MCP framework with many tools beyond weather
  • Production deployments that require explicit auth, strong access control, and documented operational guarantees
  • Use cases needing REST/GraphQL/SDK integrations

Interface

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

Authentication

OAuth: No Scopes: No

README does not describe client authentication for MCP usage. It mentions config/private_key.pem and config/config.yaml, implying some internal credentialing, but no access-control mechanism (e.g., API keys, OAuth scopes) is documented for agent clients.

Pricing

Free tier: No
Requires CC: No

No pricing information is provided (appears to be a self-hosted open-source-style component).

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Only weather functionality is described; tool coverage may be limited.
  • Transport choice matters: stdio requires building and configuring a local executable path; SSE requires running the server with appropriate flags.
  • Authentication/access control behavior is not documented; agent systems should not assume any security controls unless verified in code/config.

Alternatives

Full Evaluation Report

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

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