Skip to main content
Glama

Pride

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

EBI PRIDE Archive MCP — proteomics (mass-spectrometry) data repository.

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

TDQS

A3.9/5.0

Scored across 33 tools

Disambiguation3/5

The descriptions do a lot of work to distinguish tools, but real overlap remains: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research form a four-way cluster where beta is admittedly identical to stable, and six polymarket_* tools (edges, edge_tracker, arbitrage, bet_research, fill_risk, kalshi_spread) all serve the 'find/validate an edge' purpose with fuzzy boundaries. Memory (remember/recall/forget) and subscription (subscribe/list/unsubscribe/recent_alerts) groups are cleanly distinct.

Naming Consistency4/5

All tools are snake_case and most follow a verb_noun or verb_noun_qualifier pattern (search_projects, compare_entities, validate_claim, list_subscriptions), with domain prefixes used consistently (polymarket_*, pipeworx_*, ask_pipeworx_*). Minor deviations exist in noun-only names (entity_profile, recent_alerts) and the suffix-based variants (ask_pipeworx_beta, _grounded), but the convention is predictable.

Tool Count2/5

33 tools is heavy, and several are redundant rather than additive — the ask_pipeworx trio plus deep_research, six polymarket tools, and three ai/scan-visibility tools inflate the surface beyond what the gateway needs. The redundant beta router is a clear example of a tool that does not earn its slot.

Completeness4/5

As a data-gateway surface it is broad and largely closed-loop: memory has full CRUD, subscriptions have create/list/cancel plus a delivery feed, entity identity/resolution/profile/comparison are covered, and prediction-market workflows span discovery, persistence, and fill risk. Gaps are minor (e.g. PRIDE coverage is limited to search/get with no richer proteomics operations, and no direct resource-read tool beyond search_within).

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

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