data_freshness

Pack: pipeworx-catalog · Endpoint: https://gateway.pipeworx.io/pipeworx-catalog/mcp

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 source (forgiving match, e.g. “portwatch”, “digitraffic ais”, “polymarket”, “kalshi”, “gdelt”, “cpi”) or category (“maritime”, “markets”, “news”, “economics”) to scope the probe, or omit both to probe every curated source. Lag is measured at call time and can vary between calls — this tool never reports a lag it did not just observe.

Parameters

NameTypeRequiredDescription
sourcestringnoForgiving name match against one curated source, e.g. “portwatch”, “polymarket”, “kalshi”, “digitraffic”, “gdelt”, “cpi”. Omit to probe everything.
categorystringnoFilter to one category: maritime | markets | news | economics. Omit to probe everything.

Example call

curl -X POST https://gateway.pipeworx.io/pipeworx-catalog/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"data_freshness","arguments":{}}}'

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx-catalog": {
      "url": "https://gateway.pipeworx.io/pipeworx-catalog/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

Regenerated from source · build July 29, 2026