Skip to main content
Glama

Useragent

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

User-Agent parser MCP.

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
44.0% over 39 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-useragent
GitHub Stars
0
Server Listing
mcp-useragent

TDQS

A3.8/5.0

Scored across 37 tools

Disambiguation2/5

Multiple tools have heavily overlapping purposes: ask_pipeworx and ask_pipeworx_beta are explicitly identical, ask_pipeworx vs deep_research vs validate_claim all handle natural-language research lookups, and company_facts/entity_profile/compare_entities/recent_changes all describe company data retrieval. The prediction-market set (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_kalshi_spread, polymarket_edge_tracker, polymarket_fill_risk) also has fuzzy boundaries that descriptions only partially clarify.

Naming Consistency3/5

Most tools follow snake_case, and the polymarket_* family is nicely consistent, but verb patterns are mixed: ask_*, scan_*, resolve_*, validate_*, generate_*, parse_*, plus noun-style names like company_facts, entity_profile, recent_changes, and release_calendar_markets. There is no single predictable verb_noun convention across the set.

Tool Count2/5

37 tools is well beyond the 16-25 'heavy' range and feels bloated for a single server, especially since the server name 'Useragent' only relates to one tool (parse_user_agent). Many tools serve a vast Pipeworx data platform plus prediction markets plus memory plus misc utilities, which is too much surface area for coherent agent selection.

Completeness4/5

Within its actual sprawling scope, the surface is thorough: lookups (ask_pipeworx variants), research (deep_research, entity_profile), verification (validate_claim, resolution_audit/diff), discovery (discover_tools, suggest_questions), prediction-market analysis, subscriptions, and memory all have full lifecycle coverage. Minor gaps exist (e.g. no way to generate user-agent strings despite the server name, no direct PR/comment-style operations here) but they are not agent-blocking.

Tool Schema Changelog

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

  1. 5 tool updates
    • Addedcompany_facts
    • Addedkalshi_weather_edge
    • Addedrelease_calendar_markets
    • Addedresolution_audit
    • Addedresolution_diff
  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": "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 (\"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 (\"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_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
      • 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

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