Skip to main content
Glama

Server Details

MyVariant.info MCP. Aggregated human genetic-variant annotation: dbSNP, ClinVar clinical…

The last two health checks of this connector failed. 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
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-myvariant
GitHub Stars
0
Server Listing
mcp-myvariant
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 47 tools

Disambiguation3/5

The descriptions are unusually explicit about boundaries (ask_pipeworx vs _grounded vs _beta vs deep_research, entity_profile vs company_facts vs recent_changes), which does a lot of work here. But the set contains dense clusters of near-neighbors — 13 prediction-market tools (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker, bet_research, kalshi_weather_edge, release_calendar_markets, updown_venue_compare, updown_divergence_rate, prediction_calibration, resolution_audit/diff) — where an agent choosing between 'edges' and 'arbitrage' or 'fill_risk' for the same question is a real coin flip. Five company-research tools that all answer 'tell me about X' (entity_profile, company_facts, compare_entities, resolve_entity, validate_claim) compound this.

Naming Consistency3/5

The dominant pattern is snake_case verb_noun (list_subscriptions, validate_claim, resolve_entity, research_row, scan_dependency, generate_llms_txt), and casing is uniformly snake_case throughout — no camelCase mixing. But the family structure breaks down: bare nouns and verbless names (query, variant, metadata, kalshi_weather_edge, prediction_calibration, polymarket_edges), noun+_check suffixes (ai_visibility_check), and prefixed namespaces (polymarket_*, ask_pipeworx_*, archive_*) mean the convention is readable but not predictable.

Tool Count2/5

47 tools is far past the point where an agent can hold the option set in mind, and the surface spans at least eight unrelated domains (genomics, prediction markets, SEC/XBRL company data, AI brand marketing, subscriptions, agent memory, archives, dev dependency scanning). Many are meta-routers (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions, validate_claim) that internally route to 7,212 tools, which makes the explicit surface feel redundant rather than scoped.

Completeness3/5

Judged against the server's own name and stated purpose (MyVariant.info), query + variant + metadata mirror the upstream API's query/variant/metadata endpoints, so the genomics core is arguably complete — though batch lookup and assembly-conversion helpers are absent. Judged as the gateway it actually is, coverage is deep but lopsided: prediction markets and company research are exhaustively tooled while other advertised packs (FRED, FDA, patents, weather) are reachable only through routing meta-tools, and there is no way to enumerate what the gateway offers beyond discover_tools/suggest_questions.

Tool Schema Changelog

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

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.