Home / MCP registry index / io.github.cyanheads/brapi-mcp-server

io.github.cyanheads/brapi-mcp-server

io.github.cyanheads/brapi-mcp-server in the official MCP registry. Endpoint https://brapi.caseyjhand.com/mcp. Source: github.com/cyanheads/brapi-mcp-server.

The registry describes it as: Collaborative BrAPI v2.1 MCP workspace: studies, germplasm, genotypes across Breedbase, T3, more.

We read its 22 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http brapi-mcp-server https://brapi.caseyjhand.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "brapi-mcp-server": {
      "url": "https://brapi.caseyjhand.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"brapi-mcp-server","type":"http","url":"https://brapi.caseyjhand.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

brapi_connect brapi_build_phenotype_matrix brapi_server_info brapi_describe_filters brapi_find_studies brapi_get_study brapi_find_germplasm brapi_get_germplasm brapi_walk_pedigree brapi_germplasm_performance brapi_find_variables brapi_find_observations brapi_find_images brapi_get_image brapi_find_locations brapi_find_variants brapi_find_genotype_calls brapi_export_genotype_matrix brapi_dataframe_describe brapi_dataframe_query brapi_raw_get brapi_raw_search

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-cyanheads-brapi-mcp-server/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-cyanheads-brapi-mcp-server)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.