Skip to main content
Glama

Randomuser

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Random User MCP — wraps randomuser.me (free, no auth)

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
38.3% over 44 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-randomuser
GitHub Stars
0
Server Listing
mcp-randomuser

TDQS

A3.9/5.0

Scored across 33 tools

Disambiguation3/5

Several tools overlap heavily: ask_pipeworx, ask_pipeworx_beta (explicitly identical today) and ask_pipeworx_grounded are near-identical routing entry points, while deep_research, discover_tools and suggest_questions all compete for the 'start here' role. generate_users and generate_by_gender are both random-profile generators with only a gender filter distinguishing them. The Polymarket cluster and memory/subscription tools are more clearly separated, keeping this from scoring lower.

Naming Consistency3/5

Almost all names are snake_case, which keeps them readable, but no predictable pattern holds: verb_noun forms (validate_claim, resolve_entity, generate_users) mix with noun phrases (entity_profile, recent_changes, polymarket_edges) and prefixed families (ask_pipeworx_*). The same action is also expressed with different stems (generate_users vs generate_by_gender, compare_entities vs entity_profile).

Tool Count3/5

33 tools is heavy for a server named randomuser, and even for a broad Pipeworx data gateway it is inflated by redundant variants such as ask_pipeworx_beta and ask_pipeworx_grounded. The underlying scope is genuinely large (1552 sources, many meta-tools), so the count is not extreme, but it is above the comfortable 3-15 range.

Completeness4/5

For the dominant Pipeworx data-gateway surface, coverage is broad: discovery (discover_tools, suggest_questions), routing (ask_pipeworx, deep_research), grounded verification (validate_claim, ask_pipeworx_grounded), entity resolution/comparison/profiling, memory CRUD (remember/recall/forget), subscription lifecycle, and feedback. The random-user corner is thin with only two generation tools and no create/read/update/delete lifecycle, but the main domain is largely covered.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "when-will-bitcoin-hit-150k"
-  },
-  {
-    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
  2. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "when-will-bitcoin-hit-150k"
+  },
+  {
+    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread1 field changed
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

Related MCP Connectors

Related MCP Servers

  • mcp-jsonplaceholder

    pipeworx-io
    A
    license
    Not graded
    quality
    B
    maintenance
    Wraps the JSONPlaceholder fake REST API to enable testing and prototyping with CRUD operations on posts, comments, and other resources via MCP.
    360 npm
    MIT

  • User Management MCP Server

    ajith-fullstack
    F
    license
    Not graded
    quality
    C
    maintenance
    Enables AI-compatible MCP clients to create, retrieve, update, and delete user records through five MCP tools, plus a guide resource and a prompt that auto-generates and saves random users. User data is validated with Zod and persisted in a JSON file behind a Streamable HTTP endpoint.
    -

  • claude-ia-mcp-tools

    vicboma1
    F
    license
    Not graded
    quality
    B
    maintenance
    Exposes MCP tools for user CRUD operations (get, list, create, update, delete) by routing requests through shared business logic and an API client, using JSONPlaceholder as the demo backend.
    -
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources