Bioregistry
Server Details
Bioregistry — meta-registry of biomedical identifier prefixes
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
- 46.8% over 38 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-bioregistry
- GitHub Stars
- 0
- Server Listing
- mcp-bioregistry
TDQS
Scored across 40 tools
Several tools have overlapping or easily confused purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical variants, and the polymarket_* family plus bet_research and resolution_* tools heavily overlap in scope. resolve vs resolve_entity and prefix vs prefixes also create boundary confusion. Detailed descriptions help, but the set as a whole has unclear tool boundaries.
Naming is a mix of bare verbs/nouns (prefix, resolve, search, remember), verb_noun constructions (compare_entities, validate_claim), noun phrases (polymarket_arbitrage, resolution_audit), and platform variants (ask_pipeworx_beta, ask_pipeworx_grounded). No predictable convention holds across the set.
40 tools is too many and badly misaligned with the server name: only a handful (prefix, prefixes, search, resolve) belong to Bioregistry, while the rest span Pipeworx querying, prediction markets, memory, subscriptions, and AI visibility. The count is not justified by a coherent purpose.
There is no coherent domain to assess completeness against. The Bioregistry portion is a minimal read/resolution surface, while the Pipeworx and prediction-market portions include many analysis tools but lack obvious lifecycle operations like trade execution or source management. The surface is sprawling yet incomplete for any single purpose.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
6 tool updates
- Added
company_facts - Added
kalshi_weather_edge - Added
release_calendar_markets - Added
resolution_audit - Added
resolution_diff - Changed
search2 fields changed- changed
Output schema / properties / results / items / properties / description / typePrevious value: -"string"New value: +[ + "string", + "null" +] - changed
Output schema / properties / results / items / properties / name / typePrevious value: -"string"New value: +[ + "string", + "null" +]
1 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious 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" + } +] - changed
Input schema / properties / market / descriptionPrevious 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."
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious 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" + } +] - changed
Input schema / properties / market / descriptionPrevious 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."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious 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
Research Organization Registry (ROR) — canonical org IDs
EBI Ontology Lookup Service — 250+ biomedical ontologies
Monarch biomedical knowledge graph — diseases, phenotypes, genes, variants
Diagnoses, drugs & lab codes: ICD-11, SNOMED, LOINC, RxNorm, MeSH, ATC, CID-10. 33 tools, MIT.
Related MCP Servers
- FlicenseAqualityDmaintenanceProvides access to bioRxiv and medRxiv preprints via a unified tool with seven methods, including keyword search, metadata retrieval, and statistics.1-
- AlicenseAqualityAmaintenanceGrounds gene-nomenclature work in the HUGO Gene Nomenclature Committee (HGNC) dataset, enabling resolution of gene symbols and IDs to canonical HGNC identifiers, plus cross-references and batch operations.9MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for assisting users in registering their MCP servers, knowledge graph components, and other biomedical tools to the BioContextAI registry.MIT
- FlicenseBqualityDmaintenanceA production-ready Model Context Protocol (MCP) server that provides comprehensive access to the BioOntology API for searching, annotating, and exploring over 1,200 biological ontologies.109-
Glama MCP Gateway
Add one secure layer between your agents and this server.