
Wraps StupidAPIs to give yes/no questions a quantum superposition treatment, returning both true and false simultaneously with wave function interpretations. You get one tool, schrodingers_boolean_evaluate, which supports an optional cat mode for more absurdist responses. This is novelty API territory, useful if you're building something that needs deliberately indeterminate answers or want to add some quantum humor to your agent's decision making. Requires an X-API-Key for authentication. Part of the Pipeworx gateway ecosystem, so you can access it standalone or through their unified endpoint alongside 250+ other data sources.
schrodingers-boolean MCP — wraps StupidAPIs (requires X-API-Key)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
schrodingers_boolean_evaluate | Ask a yes/no question and get a quantum superposition answer (both true and false simultaneously). Supports cat mode for absurdist responses. Returns the answer state and wave function interpretation. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"schrodingers-boolean": {
"url": "https://gateway.pipeworx.io/schrodingers-boolean/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/schrodingers-boolean/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 Schrodingers Boolean data" })
The gateway picks the right tool and fills the arguments automatically.
MIT