
This is a lightweight wrapper around StupidAPIs' random number generation endpoint, exposing a single tool that returns numeric values on demand. You'd reach for it when testing workflows, generating placeholder data, or needing unpredictable numbers in your agent loops without writing your own randomization logic. It requires an X-API-Key for authentication and runs through the Pipeworx gateway, which offers streamable HTTP transport and a plain English query interface via ask_pipeworx if you don't want to call the generate tool directly. Part of a larger gateway system that connects to 250+ data sources, though this particular server does one simple thing: give you a random number when you ask for it.
phoenix-number MCP — wraps StupidAPIs (requires X-API-Key)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
phoenix_number_generate | Returns the current temperature in Phoenix, Arizona — presented as a random number. No inputs required. The number is hot, unjustified, and arrives with arid confidence. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"phoenix-number": {
"url": "https://gateway.pipeworx.io/phoenix-number/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/phoenix-number/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 Phoenix Number data" })
The gateway picks the right tool and fills the arguments automatically.
MIT