Weather & Geo Intel MCP
REMOTE · WEATHER.DATAKOOT.COM · SCANNED SEP 21
US weather & geo for AI agents: forecasts, alerts, earthquakes, elevation, geocoding. No keys.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 743 tokens (~123/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Weather & Geo Intel MCP server?
Weather & Geo Intel MCP is a hosted endpoint at https://weather.datakoot.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · weather.datakoot.com
claude mcp add --transport http com-datakoot-us-weather-forecast-alerts 'https://weather.datakoot.com/mcp'
{
"mcpServers": {
"com-datakoot-us-weather-forecast-alerts": {
"url": "https://weather.datakoot.com/mcp"
}
}
} {
"servers": {
"com-datakoot-us-weather-forecast-alerts": {
"type": "http",
"url": "https://weather.datakoot.com/mcp"
}
}
} [mcp_servers.com-datakoot-us-weather-forecast-alerts] url = "https://weather.datakoot.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-datakoot-us-weather-forecast-alerts": {
"type": "remote",
"url": "https://weather.datakoot.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-datakoot-us-weather-forecast-alerts --url 'https://weather.datakoot.com/mcp' --transport streamable-http
mcp_servers:
com-datakoot-us-weather-forecast-alerts:
url: "https://weather.datakoot.com/mcp" {
"McpServers": {
"com-datakoot-us-weather-forecast-alerts": {
"Transport": "http",
"Url": "https://weather.datakoot.com/mcp"
}
}
} assistant mcp add com-datakoot-us-weather-forecast-alerts -t streamable-http -u 'https://weather.datakoot.com/mcp'
{
"mcpServers": {
"com-datakoot-us-weather-forecast-alerts": {
"type": "http",
"url": "https://weather.datakoot.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://weather.datakoot.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=datakoot.com | CN=WE1,O=Google Trust Services,C=US | 26 Jul 2026 | 24 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 58954db3a580c7f90e4d9eb7c98be951 |
| SANs: datakoot.com, weather.datakoot.com, *.weather.datakoot.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of weather.datakoot.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| datakoot.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://weather.datakoot.com/mcp | Verified | 200 | |
| http (plaintext) | http://weather.datakoot.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
earthquakes ~153
List recent earthquakes worldwide from the USGS feed. Filter by minimum magnitude, look-back window in days, and optionally a bounding box or a point+radius (km). Returns magnitude, place, time, depth and coordinates.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Look back this many days (default 7, max 30). |
| lat | number | – | Optional center latitude for a radius search. |
| limit | integer | – | Maximum number of quakes to return. |
| lon | number | – | Optional center longitude for a radius search. |
| min_magnitude | number | – | Only return quakes at or above this magnitude. |
| radius_km | number | – | Radius in km around lat/lon (requires lat+lon). |
No output schema declared.
No examples provided.
elevation ~90
Get the ground elevation at a latitude/longitude within the US, from the USGS Elevation Point Query Service. Returns elevation in feet and meters.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude in decimal degrees, e.g. 39.5883. US coverage only (USGS). |
| lon | number | yes | Longitude in decimal degrees, negative in the western hemisphere, e.g. -105.6438. |
No output schema declared.
No examples provided.
geocode ~120
Convert a US street address OR a city/town name into latitude/longitude coordinates, using US Census data. Accepts both '1600 Pennsylvania Ave NW, Washington DC' and 'Chicago, IL' - a place name returns the centroid of the city. Call this first whenever you have a location as text and need coordinates for the weather or elevation tools. US locations only.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | A US street address ('1600 Pennsylvania Ave NW, Washington DC') or a city or town ('Chicago, IL', 'Springdale, Arkansas') |
No output schema declared.
No examples provided.
weather_alerts ~83
List active NWS weather alerts (warnings, watches, advisories) for a US state or marine area. Pass a two-letter state code like CA, TX, FL. Returns event type, severity, headline, affected area and expiry.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | yes | Two-letter US state/territory code, e.g. CA, TX, FL, PR. |
No output schema declared.
No examples provided.
weather_current ~95
Get the latest observed weather conditions for a US location by latitude/longitude, from the nearest NWS observation station: temperature, humidity, wind, and text description.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude in decimal degrees, e.g. 36.1867. US coverage only (National Weather Service). |
| lon | number | yes | Longitude in decimal degrees, negative in the western hemisphere, e.g. -94.1288. |
No output schema declared.
No examples provided.
weather_forecast ~132
Get a multi-day weather forecast for a US location by latitude/longitude (National Weather Service). Returns named periods (Today, Tonight, ...) with temperature, wind, and a short + detailed forecast. Use geocode first if you only have an address.
| Name | Type | Req | Description |
|---|---|---|---|
| hourly | boolean | – | If true, return the hourly forecast instead of daily periods. |
| lat | number | yes | Latitude in decimal degrees, e.g. 36.1867. US coverage only (National Weather Service). |
| lon | number | yes | Longitude in decimal degrees, negative in the western hemisphere, e.g. -94.1288. |
No output schema declared.
No examples provided.
What is the Weather & Geo Intel MCP server?
Weather & Geo Intel MCP is listed in the public MCP registry as com.datakoot/us-weather-forecast-alerts. US weather & geo for AI agents: forecasts, alerts, earthquakes, elevation, geocoding. No keys. This page covers its hosted endpoint (https://weather.datakoot.com/mcp).
Is the Weather & Geo Intel MCP server safe to use?
Weather & Geo Intel MCP scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Weather & Geo Intel MCP server expose?
Weather & Geo Intel MCP exposes 6 tools: geocode, weather_forecast, weather_current, weather_alerts, earthquakes, elevation. Their descriptions and schemas cost roughly 673 tokens of context every time the server is loaded.
Does the Weather & Geo Intel MCP server require authentication?
No. We connected to Weather & Geo Intel MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Weather & Geo Intel MCP server still maintained?
Weather & Geo Intel MCP is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.