Skip to main content
Glama

Mercury Number

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

mercury-number MCP — wraps StupidAPIs (requires X-API-Key)

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-mercury-number
GitHub Stars
0
Server Listing
mercury-number

TDQS

A3.8/5.0

Scored across 32 tools

Disambiguation2/5

There are several near-duplicate tools: ask_pipeworx, ask_pipeworx_beta (explicitly identical to ask_pipeworx right now), ask_pipeworx_grounded, and deep_research all route questions to the same 5,961-tool catalog, and the prediction-market cluster (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, bet_research) heavily overlaps. Similarly discover_tools vs suggest_questions and validate_claim vs ask_pipeworx_grounded have blurry boundaries. Descriptions are extremely verbose and attempt to disambiguate, but the set genuinely has multiple tools that appear to do the same thing.

Naming Consistency4/5

Names are consistently snake_case verb_noun throughout (resolve_entity, compare_entities, recent_changes, list_subscriptions). Minor deviations exist in the suffix-based variants (ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded) and the anomalous mercury_number_generate, but overall the convention is predictable.

Tool Count2/5

32 tools is heavy and, combined with a sprawling platform surface, makes the set hard to hold in context. Multiple slots are consumed by overlapping router variants and a novelty tool, suggesting the count is inflated rather than each tool earning its place.

Completeness4/5

Across its actual purpose (universal data routing, entity resolution, comparison, monitoring, memory, prediction markets) the surface is broad and covers CRUD/lifecycle for memory (remember/recall/forget) and subscriptions (subscribe/list/unsubscribe/recent_alerts). Gaps are minor, e.g. no explicit update for stored memory keys.

Tool Schema Changelog

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

  1. 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": "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 (\"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."
    • 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."
  2. 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."
  3. 1 tool update
    • Changedresolve_entity1 field changed
      • changedInput schema / properties / value / description
        Previous 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."

Related MCP Connectors

Related MCP Servers

  • mcp-tarot-draw

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that draws tarot cards from the 78-card deck and interprets them for your situation, using StupidAPIs with an X-API-Key required.
    1 npm
    MIT

  • mcp-numbers

    pipeworx-io
    A
    license
    Not graded
    quality
    B
    maintenance
    Number utilities MCP server providing base conversion, Roman numeral conversion, and English word spelling of integers.
    4 npm
    MIT
  • oom-x402-mcp by OrdersOfMagnitudeLLC

    oom-x402-mcpofficial

    OrdersOfMagnitudeLLC
    F
    license
    Not graded
    quality
    B
    maintenance
    MCP server exposing 1,000+ pay-per-call API endpoints across agent infrastructure (memory, coordination, secrets, verification), data, compute, finance, weather, geography, and reference categories — payments via x402 protocol in USDC on Base.
    -
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