Skip to main content
Glama

Phoenix Number

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

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

TDQS

A3.7/5.0

Scored across 32 tools

Disambiguation3/5

Several tools have overlapping purposes, especially the query/routing tier (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) and entity-focused wrappers (compare_entities, entity_profile, recent_changes, validate_claim). Descriptions provide strong guidance and explicit 'prefer over' rules, but the boundaries remain fuzzy for a first-time agent. The beta variant currently duplicates the stable router, adding another source of misselection.

Naming Consistency3/5

All tool names use lowercase snake_case, which is readable and consistent at the separator level. However, the naming pattern is mixed: some are verb_noun (resolve_entity, validate_claim), some are noun phrases (entity_profile, recent_changes), some are prefixed families (ask_pipeworx*, polymarket_*), and a few are single verbs (remember, recall, forget). This makes the convention predictable only in style, not in structure.

Tool Count3/5

32 tools is heavy for an MCP server, even one acting as a gateway to a much larger data catalog. Many tools are specialized and earn their place (memory, subscriptions, prediction-market analytics), but several meta-query tools overlap and could be consolidated. The count is borderline rather than clearly excessive given the broad apparent scope.

Completeness4/5

The surface covers a wide range of needs—discovery, grounded answering, deep research, entity resolution, comparison, change tracking, prediction-market tools, memory, and subscriptions. Minor gaps include no explicit generic tool for directly invoking a discovered schema by name, and prediction-market coverage focuses on analysis rather than order placement. Overall the set is largely complete with workable paths for most tasks.

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."

Related MCP Connectors

Related MCP Servers

  • mcp-magic-8-ball

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    A Magic 8 Ball MCP server that wraps StupidAPIs to answer yes-or-no questions with mystical responses, supporting cynical and corporate modes.
    1 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.
    -

  • MCP Tool Server

    Akhiljoshi03
    F
    license
    Not graded
    quality
    C
    maintenance
    A production-oriented MCP server exposing tools for weather, currency conversion, text statistics, and server introspection, with auto-discovery, rate limiting, and API key auth.
    -

  • mcp-first-server

    JGPAS
    A
    license
    A
    quality
    B
    maintenance
    MCP server exposing quote and live cryptocurrency price tools, with both local (stdio) and cloud-deployed (HTTP) transports.
    2
    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