VirtualFlyBrain
MCP server · mcp.virtualflybrain.org · found in a public list · checked since 2026-11-13
Live, handshake completed · latest check
Provides Drosophila neuroscience data: brain regions, cell types and their hierarchies.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/7). What this means
Placed in Life-science databases: Genes, proteins, molecular interactions, species names and occurrences, and genomics datasets.
https://mcp.virtualflybrain.org MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person. See 2 endpoints from virtualflybrain.org.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-11-13 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-11-13 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-11-13 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
combine_queriesget_hierarchyget_known_neurotransmittersget_predicted_neurotransmittersget_term_infolist_connectome_datasetslist_search_facetslookup_xrefquery_connectivityresolve_combinationresolve_entityrun_querysearch_terms
- Tools
- 13
- This list since
- 2026-11-13
- First listed to us
- 2026-11-13
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- tools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
Calls it declares
get_term_info id* force_refreshrun_query id query_type queries limit offset include_images force_refreshsearch_terms query* filter_types exclude_types boost_types demote_types unique start rows minimize_results auto_fetch_term_infolist_search_facets containsresolve_entity name*resolve_combination name*list_connectome_datasetsquery_connectivity upstream_type downstream_type weight group_by_class exclude_dbs limit offsetget_predicted_neurotransmitters neuron_type* aggregate split_by_dataset exclude_dbs min_confidenceget_known_neurotransmitters neuron_type*get_hierarchy id* relationship* direction max_depthlookup_xref id accession db
From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Links
What it states about itself, from its registry entry or package:
- Website: virtualflybrain.org
- Repository: github.com/VirtualFlyBrain/VFB3-MCP
Pages we read:
- Homepage: mcp.virtualflybrain.org, read
Links only (links/3): we follow none of them when showing this page, and a link is not a recommendation. How links are chosen.
Listing
In the capability tree: Search and information / Reference data / Life-science databases (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/7, tree/3) on 2026-11-13. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, handshake completed HTTP 200 | 827 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_233b9fd077e4aefa