Flood MCP — wraps Open-Meteo Flood API (free, no auth)
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 33 tools
Most tools target distinct actions, but the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) and the six polymarket tools (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread, bet_research) heavily overlap in purpose and differ mainly by nuance. The highly detailed descriptions help, but an agent can easily misselect among 'router' variants and betting-analysis tools.
Nearly all tools use snake_case with a predictable verb_noun shape (get_flood_forecast, resolve_entity, validate_claim, list_subscriptions). Minor deviations exist (recent_alerts, recent_changes, entity_profile lack a leading verb, and ask_pipeworx uses a product name), but the overall pattern is consistent and readable.
33 tools is heavy, well above the 15-tool comfort zone, and spans many unrelated domains (AI visibility, flood forecasting, Polymarket betting, memory, subscriptions, generic data routing). For a broad data gateway the count is defensible, but it is bloated and each sub-domain competes for attention.
Coverage is broad and mostly self-contained: memory has full CRUD (remember/recall/forget), subscriptions have create/list/cancel plus an alerts feed, and identity/entity, research, claim-verification, and Polymarket surfaces are all deep. The only notable gaps are the thin flood surface (two read-only tools with no subscriptions/alerts of their own) and soft-failing patent sources.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
bet_research2 fields changedInput schema / examplesPrevious value: -[
- {
- "market": "will-bitcoin-reach-100k-in-july-2026"
- },
- {
- "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
- }
-]New value: +[
+ {
+ "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ },
+ {
+ "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ }
+]Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."polymarket_kalshi_spread2 fields changedInput schema / examplesPrevious value: -[
- {
- "topic": "fed"
- },
- {
- "topic": "btc"
- }
-]New value: +[
+ {
+ "topic": "fed"
+ },
+ {
+ "topic": "btc"
+ },
+ {
+ "topic": "bitcoin"
+ },
+ {
+ "topic": "fed rate decision"
+ }
+]Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."entity_profile3 fields changedInput schema / properties / type / descriptionPrevious value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."Input schema / properties / type / enumPrevious value: -[
- "company"
-]New value: +[
+ "company",
+ "ticker"
+]Input schema / properties / value / descriptionPrevious value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."resolve_entity1 field changedInput schema / properties / value / descriptionPrevious value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."Climate MCP — wraps Open-Meteo Climate API (free, no auth)
Open-Meteo MCP — weather forecast + historical reanalysis + sister APIs
Marine MCP — wraps marine-api.open-meteo.com (free, no auth)
OpenWeather MCP — wraps the OpenWeatherMap API (openweathermap.org)
Add one secure layer between your agents and this server.