Pipeworx Faq
Server Details
Pipeworx FAQ MCP — curated answers to questions ABOUT Pipeworx itself
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-pipeworx-faq
- GitHub Stars
- 0
- Server Listing
- pipeworx-faq
TDQS
Scored across 33 tools
The router family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) and the entity tools (entity_profile, compare_entities, recent_changes, resolve_entity) overlap heavily, and validate_claim vs ask_pipeworx_grounded is a close call. Extremely detailed descriptions do most of the disambiguation work and mostly succeed, but boundaries like beta-vs-stable routing and grounded-vs-validate are genuinely blurry.
Names are uniformly snake_case and readable, with sensible prefix grouping (polymarket_*, pipeworx_*). The verb_noun convention is not fully consistent though — some tools are bare verbs (remember, recall, subscribe), others noun-first (entity_profile, recent_changes), so the pattern is only mostly predictable.
33 tools is heavy and pushes past the comfortable 3-15 band, and the 'Faq' label understates what is really a sprawling gateway with several distinct sub-surfaces. The breadth (routing, memory, subscriptions, prediction markets, meta) justifies most tools, but it is borderline over-scoped.
Coverage is broad and largely closed-loop: memory has remember/recall/forget, subscriptions have subscribe/unsubscribe/list_subscriptions/recent_alerts, and research, entity, and Polymarket surfaces are rich. Minor gaps remain (e.g. no record-management operations, limited non-npm dependency ecosystems), but no major dead ends.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
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": "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 (\"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."
- 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
Public Cannon Studio MCP for product, pricing, workflow, model, and API answers.
Ninebix: the site's own MCP server — dataset; every answer cites the site.
Public remote MCP server for Walnai AI Consulting services, pricing, calculator, FAQs, and adoption.
HomeCover HQ: the site's own MCP server — dataset; every answer cites the site.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for US workplace-safety standards (OSHA 29 CFR parts 1900–1990). Enables querying safety regulations via natural language through the Pipeworx gateway.8 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server providing access to US FCC regulations (47 CFR) via Pipeworx gateway. Enables AI agents to query FCC rules and data sources using natural language.4 npm1MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server for accessing the UK's official legislation database (legislation.gov.uk), enabling natural language queries via Pipeworx's AI gateway.3 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables querying plant data from Plants of the World Online (Kew) via natural language using the Pipeworx MCP gateway.3 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.