A
licenseNot graded
qualityA
maintenanceGet US weather forecasts, active alerts, and current observations via the National Weather Service API.
393
1
Apache 2.0
noaa-cdo-mcp-server
Server Details
Search NOAA CDO stations and datasets, fetch historical weather observations.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- cyanheads/noaa-climate-mcp-server
- GitHub Stars
- 4
- Server Listing
- NOAA Climate MCP Server
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
noaa_find_locations1 field changed- changed
Input schema / properties / locationCategoryId / descriptionPrevious value: -"Category filter. Use ST for states (~52 entries), CNTY for counties, CITY for cities (large set — thousands of entries), CNTRY for countries, ZIP for zip codes, CLIM_REG for NOAA climate regions, CLIM_DIV for climate divisions, HYD_ACC/HYD_CAT/HYD_REG/HYD_SUB for hydrological categories. Optional — omit to return all location types."New value: +"Category filter. Use ST for states (51 entries), CNTY for counties, CITY for cities (large set — thousands of entries), CNTRY for countries, ZIP for zip codes, CLIM_REG for NOAA climate regions, CLIM_DIV for climate divisions, HYD_ACC/HYD_CAT/HYD_REG/HYD_SUB for hydrological categories. Optional — omit to return all location types."
6 tool updates
- Changed
noaa_fetch_data4 fields changed- added
Output schema / properties / effectiveQueryAdded value: +{ + "description": "Summary of the effective query: dataset, date range, units, and any station/location/datatype filters applied.", + "type": "string" +} - added
Output schema / properties / noticeAdded value: +{ + "description": "Guidance when no records were returned — echoes query parameters and suggests how to broaden.", + "type": "string" +} - added
Output schema / properties / totalCountAdded value: +{ + "description": "Total number of matching observation records before the page limit.", + "type": "number" +} - changed
Output schema / requiredPrevious value: -[ - "results" -]New value: +[ + "results", + "totalCount", + "effectiveQuery" +]
- Changed
noaa_find_locations3 fields changed- added
Output schema / properties / noticeAdded value: +{ + "description": "Guidance when no locations matched — echoes applied filters and suggests how to broaden.", + "type": "string" +} - added
Output schema / properties / totalCountAdded value: +{ + "description": "Total number of matching locations before the page limit.", + "type": "number" +} - changed
Output schema / requiredPrevious value: -[ - "results" -]New value: +[ + "results", + "totalCount" +]
- Changed
noaa_find_stations3 fields changed- added
Output schema / properties / noticeAdded value: +{ + "description": "Guidance when no stations matched — echoes applied filters and suggests how to broaden.", + "type": "string" +} - added
Output schema / properties / totalCountAdded value: +{ + "description": "Total number of matching stations before the page limit.", + "type": "number" +} - changed
Output schema / requiredPrevious value: -[ - "results" -]New value: +[ + "results", + "totalCount" +]
- Changed
noaa_list_data_categories3 fields changed- added
Output schema / properties / noticeAdded value: +{ + "description": "Guidance when no data categories matched — echoes applied filters and suggests how to broaden.", + "type": "string" +} - added
Output schema / properties / totalCountAdded value: +{ + "description": "Total number of matching data categories before the page limit.", + "type": "number" +} - changed
Output schema / requiredPrevious value: -[ - "results" -]New value: +[ + "results", + "totalCount" +]
- Changed
noaa_list_data_types3 fields changed- added
Output schema / properties / noticeAdded value: +{ + "description": "Guidance when no data types matched — echoes applied filters and suggests how to broaden.", + "type": "string" +} - added
Output schema / properties / totalCountAdded value: +{ + "description": "Total number of matching data types before the page limit.", + "type": "number" +} - changed
Output schema / requiredPrevious value: -[ - "results" -]New value: +[ + "results", + "totalCount" +]
- Changed
noaa_list_datasets3 fields changed- added
Output schema / properties / noticeAdded value: +{ + "description": "Guidance when no datasets matched — echoes applied filters and suggests how to broaden.", + "type": "string" +} - added
Output schema / properties / totalCountAdded value: +{ + "description": "Total number of matching datasets before the page limit.", + "type": "number" +} - changed
Output schema / requiredPrevious value: -[ - "results" -]New value: +[ + "results", + "totalCount" +]
7 tool updates
- First observed
noaa_fetch_data - First observed
noaa_find_locations - First observed
noaa_find_stations - First observed
noaa_get_station - First observed
noaa_list_data_categories - First observed
noaa_list_data_types - First observed
noaa_list_datasets
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Search NOAA climate stations and datasets, fetch historical weather observations.
Find air-quality stations and read pollutant observations from government monitors via OpenAQ v3.
Find NOAA tide stations and NDBC buoys, fetch tide predictions, currents, and live conditions.
Get US weather forecasts, active alerts, and current observations.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceFind air-quality monitoring stations, read latest sensor values, and pull historical pollutant series via MCP.2382Apache 2.0
- FlicenseNot gradedqualityDmaintenanceFetches and parses METAR/TAF aviation weather data from NOAA with caching and human-readable formatting.1-
- AlicenseNot gradedqualityAmaintenanceFind NOAA tide stations and NDBC buoys, fetch tide predictions, water levels, tidal currents, and live buoy conditions via MCP.2401Apache 2.0
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.7/5.0
Disambiguation5/5
Each tool targets a distinct aspect of the NOAA CDO API: data fetching, location searching, station searching, station details, data categories, datasets, and data types. There is no overlap in functionality.
Naming Consistency5/5
All tools follow a consistent pattern: 'noaa_' prefix with a verb_noun structure (fetch_data, find_locations, find_stations, get_station, list_data_categories, list_datasets, list_data_types).
Tool Count5/5
7 tools is well-scoped for a weather data retrieval server, covering discovery (datasets, categories, types, locations, stations) and data fetching without unnecessary bloat.
Completeness5/5
The tool surface covers the full discovery-to-data workflow: discover datasets, categories, types, locations, and stations, then fetch data and get station details. No obvious gaps for the read-only API domain.