yesterdays-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
Descriptions are unusually verbose and explicitly tell the agent when to prefer each tool, but the set contains several overlapping entry points: ask_pipeworx, ask_pipeworx_beta (currently identical to stable), ask_pipeworx_grounded, deep_research, bet_research, validate_claim, compare_entities, entity_profile and recent_changes all answer questions from Pipeworx data with only subtle boundary differences. Polymarket tools (edges vs arbitrage vs edge_tracker vs bet_research) and ai_visibility_check vs scan_competitor_ai_presence also overlap. An agent can usually pick correctly, but misselection is plausible.
Every tool uses snake_case and follows recognizable prefix families (ask_pipeworx_*, polymarket_*, pipeworx_*, scan_*), which reads consistently. The verb_noun pattern is not universal — many are noun-first (entity_profile, ai_visibility_check, bet_research, recent_changes) — but the convention is coherent rather than chaotic.
32 tools is well above the 3-15 well-scoped range and past the 25+ 'too many' threshold, even for a broad data gateway. Several slots are near-duplicates (ask_pipeworx_beta identical to ask_pipeworx) or tangential outliers (yesterdays_number_get, generate_llms_txt), so not every tool clearly earns its place.
Across its apparent domains the surface is strong: memory has remember/recall/forget, subscriptions have subscribe/list/recent_alerts/unsubscribe, entity work has resolve/profile/compare/change-feed, and Polymarket betting is covered from research through arbitrage, edges, decay telemetry, fill risk and cross-venue spreads. Gaps are minor (e.g. no direct low-level record-fetch or update primitives outside the routers), which agents can work around.
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)
ship-on-friday MCP — wraps StupidAPIs (keyless — no credential needed)
iss-number MCP — wraps StupidAPIs (keyless — no credential needed)
always-seven MCP — wraps StupidAPIs (keyless — no credential needed)
Add one secure layer between your agents and this server.