advice
Server Details
Advice MCP — wraps Advice Slip API (free, no auth)
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-advice
- GitHub Stars
- 0
- Server Listing
- Advice MCP Server
TDQS
Scored across 34 tools
Most tools have distinct purposes, but the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and deep_research overlap heavily, and the six polymarket tools require careful reading to distinguish edges, arbitrage, fill risk, spread, and bet research. Descriptions do help clarify when to use each, but an agent could still misselect among the research and prediction-market clusters.
Nearly all tool names use snake_case with clear verb_noun or noun_noun patterns (get_advice, search_advice, entity_profile, validate_claim). A few names like forget and unsubscribe are bare verbs, and pipeworx_feedback/pipeworx_trending use a product prefix, but the overall convention is stable and readable.
With 34 tools, this set is far heavier than the typical 3-15 range for a coherent server, and the server is named 'advice' while only three tools actually deal with advice slips. The remaining 31 tools form a broad, heterogeneous data-platform surface, making the count disproportionate to any single apparent purpose.
For the narrow advice domain, get_advice, random_advice, and search_advice cover retrieval but there is no create/update/delete lifecycle for advice content. The broader embedded Pipeworx suite adds discovery, research, entity resolution, subscriptions, memory, and feedback, but it still lacks complete CRUD coverage for many of its subdomains, leaving notable gaps.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
bet_research2 fields changed- changed
Input 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" + } +] - changed
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."
2 tool updates
- Changed
bet_research2 fields changed- changed
Input 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" + } +] - changed
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."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
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."
Related MCP Connectors
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA sample MCP server that fetches random inspirational quotes, programming jokes, and advice from public APIs. Provides three simple tools for testing and demonstration purposes.-
- AlicenseNot gradedqualityCmaintenanceHoroscope MCP — wraps the keyless Horoscope App API.6 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables clients to retrieve random study tips remotely via a stateless MCP server deployed on Google Cloud Run.-
- AlicenseAqualityBmaintenanceMCP server exposing quote and live cryptocurrency price tools, with both local (stdio) and cloud-deployed (HTTP) transports.2MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.