Skip to main content
Glama

fruityvice

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Fruityvice MCP — wraps Fruityvice API (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
50.9% over 36 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-fruityvice
GitHub Stars
0
Server Listing
mcp-fruityvice

TDQS

A3.8/5.0

Scored across 34 tools

Disambiguation2/5

The three ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and deep_research heavily overlap, with the description itself admitting beta 'currently matches ask_pipeworx exactly.' The Polymarket family (arbitrage, edges, fill_risk, kalshi_spread, edge_tracker) and the entity tools (entity_profile, compare_entities, recent_changes, resolve_entity) also have fuzzy boundaries, and the orphaned fruit tools (get_fruit, list_fruits, get_by_nutrition) have nothing to do with the Pipeworx set.

Naming Consistency4/5

Overwhelmingly snake_case with predictable verb_noun patterns (get_fruit, list_fruits, resolve_entity, validate_claim, compare_entities, scan_dependency). A few noun-phrase names (recent_alerts, recent_changes, suggest_questions, ai_visibility_check, pipeworx_feedback) deviate slightly but remain readable and consistent in style.

Tool Count2/5

34 tools is heavy for what is essentially a router gateway plus a handful of domain helpers. The count is inflated by near-duplicate entry points (three ask_pipeworx variants) and an entire overlapping Polymarket subsystem, making the surface feel bloated rather than well-scoped.

Completeness3/5

For a data-gateway the surface is broad — routing, discovery, grounding, entity resolution, subscriptions, memory, and feedback are all present. However the stated server is 'fruityvice' yet only three tools relate to fruit while 31 are Pipeworx meta-tools, so the set is incoherent rather than cleanly complete for any single domain.

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