Skip to main content
Glama

Visualcrossing

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Visual Crossing Weather MCP — wraps the Visual Crossing Weather Timeline API

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.

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-visualcrossing
GitHub Stars
0
Server Listing
visualcrossing

TDQS

A3.9/5.0

Scored across 34 tools

Disambiguation3/5

Several clusters overlap meaningfully: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-duplicate universal routers (beta is explicitly stated to be identical), and forecast vs weather_timeline both answer future weather. The Polymarket set and the entity-research set are mostly distinct, and the unusually detailed descriptions help an agent choose, but the three router variants and the discovery tools (discover_tools, suggest_questions) create genuine selection ambiguity.

Naming Consistency4/5

Nearly everything is lowercase snake_case, which keeps the surface readable and consistent. There is minor deviation in convention — mostly verb_noun (validate_claim, resolve_entity, scan_dependency), some noun phrases (entity_profile, current_conditions), and some bare verbs (forecast, remember, recall, forget) — but no camelCase/snake_case mixing.

Tool Count2/5

34 tools is heavy, and the set spans unrelated domains (weather, SEC/entity research, Polymarket arbitrage, AI-visibility audits, agent memory, subscriptions, dev-package scanning) rather than one coherent purpose. Each tool is elaborate, but the sheer breadth and the redundant router/weather variants make the surface larger than it needs to be for any single task.

Completeness4/5

Coverage is broad and lifecycle-aware within each sub-domain: memory has remember/recall/forget, subscriptions have subscribe/unsubscribe/list/recent_alerts, weather covers current/forecast/historical, and research spans profile, compare, changes, and validation, with a grounded-mode fallback for high-stakes answers. Minor gaps exist (no subscription update path, no explicit delete for some record types), but agents can work around them.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "when-will-bitcoin-hit-150k"
-  },
-  {
-    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
-  }
-]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"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), 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."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."
  2. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous 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": "when-will-bitcoin-hit-150k"
+  },
+  {
+    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+  }
+]
      • changedInput schema / properties / market / description
        Previous 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 (\"when-will-bitcoin-hit-150k\"), 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."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
      • changedInput schema / properties / topic / description
        Previous 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."
  3. 1 tool update
    • Changedentity_profile3 fields changed
      • changedInput schema / properties / type / description
        Previous 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."
      • changedInput schema / properties / type / enum
        Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]
      • changedInput schema / properties / value / description
        Previous 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."

Related MCP Connectors

Related MCP Servers

  • mcp-weather

    loickaczmarek
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables to interact with comprehensive weather data through the MCP protocol, including current conditions, multi-day forecasts, hourly forecasts, and geocoding.
    4 npm
    MIT

  • weather-mcp

    idrabenia
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server providing weather data via the Open-Meteo API, including geocoding, current conditions, daily and hourly forecasts, and city lookup. No API key required, with support for multiple units and transport types.
    1
    MIT

  • Weathersight MCP Connector

    greatsnakes
    A
    license
    Not graded
    quality
    C
    maintenance
    Connects MCP clients to Weathersight weather data APIs, enabling queries about historical observations, typical climate, extremes, degree days, and long-term trends for locations worldwide.
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources