phoenix-number MCP — wraps StupidAPIs (keyless — no credential needed)
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 32 tools
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.
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.
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.
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.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
bet_research2 fields changedInput schema / examplesPrevious 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"
+ }
+]Input schema / properties / market / descriptionPrevious 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."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": "when-will-bitcoin-hit-150k"
+ },
+ {
+ "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+ }
+]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 (\"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."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."mercury-number MCP — wraps StupidAPIs (keyless — no credential needed)
victorian-complaint MCP — wraps StupidAPIs (keyless — no credential needed)
ship-on-friday MCP — wraps StupidAPIs (keyless — no credential needed)
could-have-been-email MCP — wraps StupidAPIs (keyless — no credential needed)
Add one secure layer between your agents and this server.