Skip to main content
Glama

Bioportal

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

BioPortal — NCBO's biomedical ontology repository (data.bioontology.org).

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

TDQS

A3.9/5.0

Scored across 40 tools

Disambiguation3/5

Most tools have recognizable purposes, but several clusters overlap: ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded, deep_research/discover_tools/suggest_questions, and multiple Polymarket opportunity scanners. The very detailed descriptions explicitly steer selection, but meaningful misselection risk remains.

Naming Consistency4/5

Every tool name uses snake_case, so the surface is superficially consistent. However, conventions vary between verb_noun (validate_claim), noun_phrase (entity_profile), bare verbs (forget), and domain-prefixed groups, so it is mostly rather than fully predictable.

Tool Count2/5

40 tools is heavy by the rubric, and the apparent BioPortal scope is represented by only four tools. Even if each has a role in a larger aggregator surface, the count is too large for a coherent BioPortal-focused set.

Completeness2/5

For BioPortal, the surface covers basic ontology list/search/class/mappings but omits batch annotation, deeper hierarchy traversal, ontology metadata/download, and instance/property endpoints. Significant gaps remain for a terminology-service domain.

Tool Schema Changelog

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

  1. 1 tool update
    • Changedrelease_calendar_markets2 fields changed
      • addedOutput schema / properties / empty_reason
        Added value: +{
+  "description": "Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure.",
+  "type": "string"
+}
      • addedOutput schema / properties / hint
        Added value: +{
+  "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).",
+  "type": "string"
+}
  2. 40 tool updates
    • First observedai_visibility_check
    • First observedask_pipeworx
    • First observedask_pipeworx_beta
    • First observedask_pipeworx_grounded
    • First observedbet_research
    • First observedbioportal_class
    • First observedbioportal_mappings
    • First observedbioportal_ontologies
    • First observedbioportal_search
    • First observedcompany_facts
    • First observedcompare_entities
    • First observeddeep_research
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedforget
    • First observedgenerate_llms_txt
    • First observedkalshi_weather_edge
    • First observedlist_subscriptions
    • First observedpipeworx_feedback
    • First observedpipeworx_trending
    • First observedpolymarket_arbitrage
    • First observedpolymarket_edge_tracker
    • First observedpolymarket_edges
    • First observedpolymarket_fill_risk
    • First observedpolymarket_kalshi_spread
    • First observedrecall
    • First observedrecent_alerts
    • First observedrecent_changes
    • First observedrelease_calendar_markets
    • First observedremember
    • First observedresolution_audit
    • First observedresolution_diff
    • First observedresolve_entity
    • First observedscan_competitor_ai_presence
    • First observedscan_dependency
    • First observedsearch_within
    • First observedsubscribe
    • First observedsuggest_questions
    • First observedunsubscribe
    • First observedvalidate_claim

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