mcp-registry/io.github.darshan0548/weather-mcp
Also listed as glama/darshan0548/weather-mcp
As of 2026-10-16 20:54 UTC, the Darshan0548 Weather MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 218.2 hours.
MCP server for weather with reasoning — umbrella advice, outdoor checks, city comparisons.
Point your MCP client at this streamable-http endpoint: https://weather-mcp-2yhb.onrender.com/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST.
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.
5 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.
Handshake + tools/list takes ~1,810 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.darshan0548%2Fweather-mcp/fixes
{
"name": "compare_weather",
"description": "Compare current weather between two cities.",
"inputSchema": {
"type": "object",
"title": "compare_weatherArguments",
"required": [
"city_a",
"city_b"
],
"properties": {
"city_a": {
"type": "string",
"title": "City A"
},
"city_b": {
"type": "string",
"title": "City B"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_weather",
"description": "Get the current weather and today's forecast for a city.",
"inputSchema": {
"type": "object",
"title": "get_weatherArguments",
"required": [
"city"
],
"properties": {
"city": {
"type": "string",
"title": "City"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.darshan0548/weather-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.darshan0548/weather-mcp"}) over MCP.
compare_weather ~80 tokensshould_i_carry_umbrella ~77 tokensis_good_for_outdoors ~75 tokensget_weather ~65 tokensabout ~45 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.darshan0548%2Fweather-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.darshan0548%2Fweather-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.darshan0548%2Fweather-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.darshan0548%2Fweather-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.darshan0548%2Fweather-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:bcb3856b3c50b9a7…, first seen 2026-10-17, included at leaf 10129 of 17,717. Version history · verify what your client received.
Compare: most reliable other servers · most reliable weather servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-16 20:54 UTC, the Darshan0548 Weather MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 218.2 hours.
Darshan0548 Weather MCP server advertises 5 tools, including about, compare_weather, get_weather, is_good_for_outdoors, should_i_carry_umbrella.
Point your MCP client at this streamable-http endpoint: https://weather-mcp-2yhb.onrender.com/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.