Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@pipeworx-catalog how stale is Polymarket order flow compared to Kalshi?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Pipeworx Catalog MCP — Exposes the full Pipeworx platform to Claude
Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.
Tool | Description |
| Browse all available Pipeworx packs. Returns pack names, categories, tool counts, and gateway URLs. Use to discover data sources or explore what's available. |
| Get tool definitions for a specific pack (e.g., 'weather', 'polygon-io'). Returns tool names, descriptions, parameters, and requirements. Use before calling a tool to verify its interface. |
| Get MCP setup instructions for connecting to Pipeworx packs. Returns connection details and gateway URLs. Use to configure your environment. |
| Search Pipeworx packs by keyword or a plain question across pack names, descriptions and tool descriptions (e.g. "weather", "translate", "Colombia procurement contracts awarded to a supplier"). Returns matching packs ranked best-first with each one's matched terms, cost, auth and reliability. Use to find which pack covers a capability before connecting to it; question filler and proper names are ignored, so the subject words are what match. |
| Check Pipeworx platform health and availability. Returns pack count, active tool count, and any service alerts. Use to verify system status before operations. |
| Search thousands of MCP servers by use case (e.g., 'database', 'email', 'calendar'). Returns community and hosted servers. Use to find tools beyond Pipeworx. |
| MEASURES publication lag for a curated set of high-value live-data sources — how fresh is this data, how old is this number, is this feed real-time, what's the data staleness on X. Every entry is PROBED LIVE against its upstream (not read from a hardcoded table): fetches the newest available datapoint right now and reports the observed lag between that datapoint and this moment. Use before pricing or settling off a number ("can I trust this PortWatch chokepoint count as current", "how stale is Polymarket vs Kalshi order flow", "when did BLS last publish CPI"). Covers maritime chokepoint traffic (IMF PortWatch), vessel AIS positions (Digitraffic), prediction-market trade tape (Polymarket, Kalshi), global news event ingestion (GDELT), and US CPI (BLS) — pass |
Related MCP server: DataToronto MCP
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"pipeworx-catalog": {
"url": "https://gateway.pipeworx.io/pipeworx-catalog/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/pipeworx-catalog/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1679+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
curl -X POST https://gateway.pipeworx.io/v1/tools/list_packs \
-H 'Content-Type: application/json' \
-d '{}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/list_packs. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"pipeworx-catalog": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-pipeworx-catalog"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-pipeworx-catalogIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Pipeworx Catalog data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Discover, inspect and run 63,000+ agent tools from one balance. Pay per call, no subscriptions.
Live data gateway for AI — 3,300+ tools across 750+ sources, with citations
Live web access for agents: scrape, SERP search, crawl/map, 74 collectors, datasets, proxies.
Give your agent live data from Twitter, Reddit, the web and GitHub. No API keys, no scraping stack.
