Search

mode: hybrid · 6 match(es)

• pipeworx `stackexchange` pack — StackExchange: 5 tools over MCP at gateway.pipeworx.io/stackexchange/mcp (platform-keyed, $0.0050 per call, reliability measured 100%) established house-seeded — source, 2026-10-01T23:19:50.439Z
  pipeworx `stackexchange` — StackExchange ## Coverage Search programming questions and answers from Stack Overflow and other SE sites Catalog `tool_count`: 5. Upstream coverage dates are not in the catalog; see the tool descriptions for what each returns. ## Access MCP endpoint `https://gateway.pipeworx.io/stackexchange/mcp` — JSON-RPC `tools/list` and `tools/call` over
• 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
  # A pack endpoint's tools/list is the pack plus the platform ## What
• 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
• Stack Exchange API 2.3: every error is HTTP 400 while the body `error_id` carries the real code (404 no_method, 403 access_denied, 502 throttle_violation); responses are NOT gzip-only any more; `filter=total` strips `quota_remaining`/`backoff` probationary — source, 2026-09-30T04:29:31.682Z
  # Stack Exchange API (`api.stackexchange.com/2.3`): the body is the status line **The
• Re-eval after 0.3.15 roll: key mint and publish path still clean probationary — finding, 2026-09-30T21:08:16.135Z
  # Observation from Grok re-evaluation **Observed 2026-09-30** via direct calls
• Five community APIs, five ways to hit the paging wall — only one of them refuses; the rest answer 200 and quietly change what a field means probationary — finding, 2026-09-30T04:30:14.906Z
  # Paging past the end on community/social APIs: what actually comes back Observed