Skip to main content
Glama

Server Details

Gene expression experiments and the brain structure ontology from the Allen Institute's Brain…

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 20 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-allen-brain
GitHub Stars
0
Server Listing
allen-brain

TDQS

A3.9/5.0

Scored across 39 tools

Disambiguation3/5

Many tools are distinct, but several clusters overlap enough to risk misselection (ask_pipeworx vs ask_pipeworx_beta vs ask_pipeworx_grounded vs deep_research; polymarket_edges vs polymarket_arbitrage vs polymarket_fill_risk vs bet_research; entity_profile vs company_facts vs recent_changes). The three Allen-specific tools themselves are clearly distinct, but the broader set has blurred boundaries that only very long descriptions attempt to resolve.

Naming Consistency4/5

All tool names consistently use snake_case with no camelCase or mixed-style chaos. They are mostly noun or verb phrases rather than a strict verb_noun pattern, but the convention is readable and predictable.

Tool Count2/5

39 tools is far too many for a server named Allen Brain, where only three tools actually address Allen Brain Atlas data. The remaining 36 tools belong to a general Pipeworx data gateway, making the set feel bloated relative to its apparent Allen-specific scope.

Completeness2/5

For the Allen Brain domain, the surface is severely incomplete: it can resolve genes, list expression datasets, and query the structure ontology, but provides no tool to actually fetch expression values, images, connectivity, or reference-space data. Agents asking 'where is gene X expressed?' would hit a dead end after identifying the dataset.

Tool Schema Changelog

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

  1. 39 tool updates
    • First observedai_visibility_check
    • First observedallen_expression_datasets
    • First observedallen_search_genes
    • First observedallen_structures
    • First observedask_pipeworx
    • First observedask_pipeworx_beta
    • First observedask_pipeworx_grounded
    • First observedbet_research
    • 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

Glama MCP Gateway

Add one secure layer between your agents and this server.