lorem
Server Details
Lorem MCP — wraps loripsum.net (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
- 52.1% over 36 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-lorem
- GitHub Stars
- 0
- Server Listing
- mcp-lorem
TDQS
Scored across 33 tools
Most tools target distinct resources, but the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) has genuinely fuzzy boundaries—beta is admitted to currently behave identically to the base tool. The Polymarket cluster (5 tools) and the ai_visibility_check vs scan_competitor_ai_presence pair also require careful reading to separate, though the unusually detailed descriptions mostly disambiguate them.
Nearly everything is snake_case and readable, with a coherent verb_noun or noun_pattern style (resolve_entity, compare_entities, recent_changes, remember/recall/forget). Minor deviations exist—product-prefixed names (ask_pipeworx, polymarket_*, pipeworx_*) and the verb_prep_noun form generate_with_options—but nothing chaotic.
At 33 tools this sits well above the comfortable band for a single server. The breadth (research routing, entity resolution, memory, subscriptions, Polymarket analytics, meta) is real, but there is clear bloat: a 3-4 tool ask_pipeworx family, an out-of-place lorem generator pair, and two overlapping AI-visibility tools.
Coverage is broad and lifecycle-aware: entity resolution, profiling, comparison, claim validation, memory (remember/recall/forget), and subscription management (subscribe/list/unsubscribe/recent_alerts) are all present. Only minor gaps (e.g. no explicit quota/account introspection, some tools soft-fail by design) keep it from full marks.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious 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" + } +] - changed
Input schema / properties / market / descriptionPrevious 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."
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious 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" + } +] - changed
Input schema / properties / market / descriptionPrevious 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."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious 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
Random User MCP — wraps randomuser.me (free, no auth)
JSONPlaceholder MCP — wraps JSONPlaceholder fake REST API (free, no auth)
Related MCP Servers
- AlicenseAqualityAmaintenanceAn MCP server that returns random JSON things — people, words, values, coordinates, and an always-empty list.4MIT
- AlicenseNot gradedqualityDmaintenanceA simple MCP server that provides tools for generating unique IDs in several formats, useful for when you need an LLM to create data containing new IDs.Eclipse Public 2.0

@first-ch/tools-mcpofficial
AlicenseAqualityBmaintenanceMCP server exposing First CH Tools' free web-tool logic for WCAG contrast, JP character counting, WebP conversion, JSON-LD, and llms.txt generation to AI agents.6303 npmMIT- AlicenseNot gradedqualityDmaintenanceMCP server that provides tools to interact with the LiteLLM proxy API, enabling LLM completions, embeddings, image generation, and admin operations.11 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.