
Wraps the randomuser.me API to generate fake user profiles on demand. You get one tool, generate_by_gender, that returns names, contact info, photos, and demographics for male or female profiles in whatever quantity you need. No authentication required since the underlying API is free and open. Useful when you need placeholder data for testing, demos, or prototyping without setting up mock databases. Hosted through Pipeworx's gateway, so you can either connect to this single server or hook into their full gateway for access to 600+ other data sources. The ask_pipeworx function lets you query in plain English instead of calling tools directly.
Random User MCP — wraps randomuser.me (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
generate_users | Generate random user profiles with names, addresses, emails, and photos. Filter by nationality (e.g., "US", "GB", "AU") and specify count for multiple profiles. |
generate_by_gender | Generate random user profiles by gender ("male" or "female"). Returns names, contact info, photos, and demographics. Specify count for multiple profiles. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"randomuser": {
"url": "https://gateway.pipeworx.io/randomuser/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/randomuser/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 Randomuser data" })
The gateway picks the right tool and fills the arguments automatically.
MIT