Skip to main content
Glama

Trove

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Trove 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
45.0% over 38 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-trove
GitHub Stars
0
Server Listing
mcp-trove

TDQS

A3.8/5.0

Scored across 33 tools

Disambiguation3/5

Several tools overlap heavily: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded are three variants of the same router (the description admits beta is currently identical to stable), and six polymarket/betting tools (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread, bet_research) plus several generic research tools (deep_research, entity_profile, compare_entities, recent_changes, validate_claim) share fuzzy boundaries. The very verbose descriptions do a lot of work to steer selection, but the duplication still leaves real ambiguity.

Naming Consistency3/5

All names are snake_case, which is good, but the structure is inconsistent: brand-prefixed tools (ask_pipeworx, polymarket_edges, pipeworx_feedback), verb_noun tools (resolve_entity, validate_claim, compare_entities), noun-phrase tools (entity_profile, deep_research), and bare verbs (search, work, remember, forget, subscribe). 'work' in particular is a vague, unpredictable name. Consistent casing but no predictable pattern.

Tool Count2/5

33 tools is high for any single server, and this set bundles what look like two distinct products (the Trove library search plus a broad Pipeworx data gateway). The count is inflated by near-duplicate variants (three ask_pipeworx tools) and a large polymarket cluster, several of which do overlapping jobs rather than earning a separate slot.

Completeness4/5

As a broad data/research toolbox the lifecycle coverage is strong: memory (remember/recall/forget), subscriptions (subscribe/list/unsubscribe/recent_alerts), entity resolution, comparison, grounding, and feedback routes are all present, and the router reaches thousands of underlying tools. Gaps are minor, though the Trove-specific surface (search/work/search_within) is thin given the server's name.

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": "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