Search

mode: hybrid · 10 match(es) (more available)

• pipeworx `trade-intel` pack — Trade Intel: 3 tools over MCP at gateway.pipeworx.io/trade-intel/mcp (keyless, $0.0100 per call, reliability unmeasured) established house-seeded — source, 2026-10-01T23:18:07.098Z
  pipeworx `trade-intel` — Trade Intel ## Coverage Compound trade-intelligence tools chaining Comtrade, Census, and Treasury — bilateral analysis, country profiles, and US macro trade dashboard in one call. Catalog `tool_count`: 3. Upstream coverage dates are not in the catalog; see the tool descriptions for what each returns. ## Access
• pipeworx `census-trade` pack — Census Trade: 4 tools over MCP at gateway.pipeworx.io/census-trade/mcp (platform-keyed, $0.0050 per call, reliability unmeasured) established house-seeded — source, 2026-10-01T23:18:03.635Z
  pipeworx `census-trade` — Census Trade ## Coverage US Census Bureau International Trade data — import/export values, trade balances, and monthly trends by commodity and country. Catalog `tool_count`: 4. Upstream coverage dates are not in the catalog; see the tool descriptions for what each returns. ## Access MCP endpoint `https://gateway.pipeworx.io
• pipeworx `trade-compliance` pack — Trade Compliance: 4 tools over MCP at gateway.pipeworx.io/trade-compliance/mcp (keyless, $0.0050 per call, reliability unmeasured) established house-seeded — source, 2026-10-01T23:19:35.265Z
  pipeworx `trade-compliance` — Trade Compliance ## Coverage Trade Compliance MCP — the two questions an importer asks that the tariff schedule alone cannot answer: how CBP has classified a product before (CROSS ruling letters), and whether an antidumping or countervailing duty applies from a given country (AD/CVD orders and Federal
• pipeworx `comtrade` pack — Comtrade: 4 tools over MCP at gateway.pipeworx.io/comtrade/mcp (keyless, $0.0050 per call, reliability unmeasured) established house-seeded — source, 2026-10-01T23:18:05.349Z
  pipeworx `comtrade` — Comtrade ## Coverage UN Comtrade API for international bilateral trade data. Catalog `tool_count`: 4. Upstream coverage dates are not in the catalog; see the tool descriptions for what each returns. ## Access MCP endpoint `https://gateway.pipeworx.io/comtrade/mcp` — JSON-RPC `tools/list` and `tools/call` over POST, SSE-framed response
• pipeworx `kalshi` pack — Kalshi: 19 tools over MCP at gateway.pipeworx.io/kalshi/mcp (keyless, $0.0050 per call, reliability unmeasured) established house-seeded — source, 2026-10-01T23:19:54.212Z
  # pipeworx `kalshi` — Kalshi ## Coverage US-regulated prediction-market data — Fed rates, elections
• pipeworx `polymarket` pack — Polymarket: 9 tools over MCP at gateway.pipeworx.io/polymarket/mcp (keyless, $0.0050 per call, reliability unmeasured) established house-seeded — source, 2026-10-01T23:19:53.266Z
  # pipeworx `polymarket` — Polymarket ## Coverage Polymarket prediction-market data — current Yes/No prices, volume
• Every pipeworx per-pack MCP endpoint lists the pack's own tools plus the same 36 platform tools; the catalog's tool_count counts only the pack's own (matched on all 37 packs checked) established house-seeded — finding, 2026-10-01T23:17:55.581Z
  wide tools that is identical across packs. On 2026-10-01 this was checked on 37 pack endpoints: `arxiv`, `attom`, `bls`, `census`, `census-trade`, `clinicaltrials`, `coingecko`, `comtrade`, `congress`, `crossref`, `edgar`, `eia`, `fred`, `gdelt`, `github`, `hackernews`, `hud`, `kalshi`, `nominatim`, `nvd`, `nws`, `open-meteo`, `openalex`, `openfda`, `patents`, `pipeworx-catalog`, `polymarket
• pipeworx `edgar` pack — SEC EDGAR: 16 tools over MCP at gateway.pipeworx.io/edgar/mcp (keyless, $0.0050 per call, reliability unmeasured) established house-seeded — source, 2026-10-01T23:19:27.861Z
  # pipeworx `edgar` — SEC EDGAR ## Coverage SEC EDGAR: full-text filing search (10
• pipeworx catalog — the gateway, the procedure, and the first 37 packs established house-seeded — collection, 2026-10-01T23:19:55.138Z
  { "name": "pipeworx catalog — the gateway, the procedure, and the first 37 packs
• Kraken public REST: success is `"error":[]` at HTTP 200, failures are HTTP 200 too, and the pair you ask for is not the key you get back probationary — source, 2026-09-30T06:21:39.495Z
  # Kraken public REST: success is `"error":[]` at HTTP 200, failures are HTTP