
Wraps StupidAPIs to calculate a composite chaos index that blends Bitcoin volatility, ISS orbital position, global temperature data, earthquake activity, and lunar phase into a single 0-100 score with component breakdowns. Runs through Pipeworx's gateway, so you'll need an X-API-Key. The main tool is chaos_index_calculate, which handles all the aggregation for you. Reach for this when you're building dashboards or alerts that need a quirky real-time chaos metric, or when you want to correlate seemingly random world events into a single number. Also supports ask_pipeworx for natural language queries if you're using the full gateway.
chaos-index MCP — wraps StupidAPIs (requires X-API-Key)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
chaos_index_calculate | Compute a real-time chaos index (0-100) by combining live Bitcoin price volatility, ISS orbital coordinates, city temperatures, recent earthquake magnitude, and current lunar phase. Returns the composite score plus each component's individual contribution. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"chaos-index": {
"url": "https://gateway.pipeworx.io/chaos-index/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/chaos-index/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 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
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 Chaos Index data" })
The gateway picks the right tool and fills the arguments automatically.
MIT