Skip to main content
Glama

Myvariant

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

MyVariant.info 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
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-myvariant
GitHub Stars
0
Server Listing
mcp-myvariant

TDQS

A4.1/5.0

Scored across 34 tools

Disambiguation3/5

Descriptions are extraordinarily detailed and explicitly rank tools, which mitigates a lot, but genuine overlap remains: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded differ only in confidence/beta status, and there are six Polymarket tools (arbitrage, edges, fill_risk, kalshi_spread, edge_tracker, bet_research) where arbitrage/edges/bet_research all 'find opportunities.' The ai_visibility_check / scan_competitor_ai_presence pair also overlaps closely.

Naming Consistency4/5

Names are uniformly snake_case with a mostly verb_noun or noun_phrase shape (ask_pipeworx, compare_entities, resolve_entity, polymarket_fill_risk), so patterns are readable. Minor deviations: bare nouns (metadata, variant, query) and bare verbs (remember, recall, forget) sit alongside the verb_noun style, and the ask_pipeworx beta/grounded suffixes vary the base name.

Tool Count3/5

34 tools is heavy and above the comfortable 3-15 band, and the sheer breadth (entity research, Polymarket betting, memory, subscriptions, AI visibility, npm checks, genomics) makes the surface sprawling. It is defensible for an aggregator router of this scope, but the count strains discoverability.

Completeness4/5

Coverage is broad and lifecycle-ish: discovery, entity resolution, deep research, grounded verification, memory (remember/recall/forget), and full subscription management (subscribe/unsubscribe/list/recent_alerts) are all present. Gaps are minor — e.g. no subscription update/edit, and the genomics variant/query/metadata subset is thin relative to the rest, but no obvious dead ends for the stated research purpose.

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."
  2. 2 tool updates
    • Changedquery1 field changed
      • addedInput schema / properties / assembly
        Added value: +{
+  "description": "Genome build for the coordinates you pass AND the ids you get back: \"hg19\" (GRCh37, the default) or \"hg38\" (GRCh38). gnomAD and Ensembl coordinates are GRCh38.",
+  "type": "string"
+}
    • Changedvariant3 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "id": "chr7:g.140453136A>T"
-  },
-  {
-    "fields": "clinvar,gnomad_genome.af,cadd.phred",
-    "id": "chr1:g.218631822G>A"
-  }
-]New value: +[
+  {
+    "id": "chr7:g.140453136A>T"
+  },
+  {
+    "fields": "clinvar,gnomad_genome.af,cadd.phred",
+    "id": "chr1:g.218631822G>A"
+  },
+  {
+    "assembly": "hg38",
+    "fields": "dbsnp.rsid,clinvar",
+    "id": "chr1:g.11796321G>A"
+  }
+]
      • addedInput schema / properties / assembly
        Added value: +{
+  "description": "Genome build for the coordinates you pass AND the ids you get back: \"hg19\" (GRCh37, the default) or \"hg38\" (GRCh38). gnomAD and Ensembl coordinates are GRCh38.",
+  "type": "string"
+}
      • changedInput schema / properties / id / description
        Previous value: -"An HGVS variant id, e.g. \"chr7:g.140453136A>T\"."New value: +"An HGVS variant id, e.g. \"chr7:g.140453136A>T\" (hg19 unless you set assembly)."

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