Pipeworx
Server Details
Live data gateway for AI — 3,300+ tools across 750+ sources, with citations
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
- Uptime
- 34.1% over 39 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-pipeworx-catalog
- GitHub Stars
- 0
- Server Listing
- Pipeworx
TDQS
Scored across 38 tools
Multiple query tools overlap in purpose (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, validate_claim, entity_profile, compare_entities, recent_changes, bet_research), and the beta variant is explicitly identical to the stable one right now—making selection ambiguous. Descriptions do provide strong routing hints, but the sheer number of research entry points still creates confusion.
All names are lowercase snake_case with no camelCase mixing, and patterns like ask_*, polymarket_*, scan_*, and search_* are predictable. Some names are noun-first (data_freshness, entity_profile, ai_visibility_check) rather than strict verb_noun, which is a minor deviation.
38 tools far exceeds the typical 3-15 well-scoped range and lands in the 'too many' bracket. While the server spans many domains (research, prediction markets, platform meta, memory, subscriptions), the volume still imposes high cognitive load and increases misselection risk.
The surface covers research, discovery, memory, subscriptions, platform status, prediction-market analytics, AI visibility, and utility functions—a broad and fairly complete set for a data aggregator. Minor gaps remain (e.g., no direct resource-reading tool, and some meta capabilities rely entirely on ask_pipeworx), but agents can work around them.
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
Give your agent live data from Twitter, Reddit, the web and GitHub. No API keys, no scraping stack.
AI Agent Source Registry. 288K+ curated sources for agentic search and discovery.
Free public MCP for AI agents — 193 tools, 44 workflows. No API key.
Verified data on 8,000+ AI tools: live status, pricing, sentiment, alternatives. Free, read-only.
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceSearch and discover 500+ tools, APIs, and services for AI agents. Browse 15 categories, get recommendations, and access structured metadata including auth methods, free tiers, and example calls.1-
- AlicenseAqualityBmaintenanceEnables AI assistants to search a curated database of 200+ AI tool cards with pricing, platforms, use cases, and source links, so users can ask which tool to use for a task and get grounded recommendations.15 npm1MIT
- FlicenseNot gradedqualityBmaintenance23 research tools for AI agents: web search, social media, academic papers, SEC filings, citation verification, reliability scoring. Pay-per-call from $0.01.-
- AlicenseAqualityAmaintenanceGive your AI agent access to 8,400+ software tools — search, compare, get pricing, find alternatives, and discover the best tool for any use case.835 npm4MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.