Home / MCP registry index / org.plantdatabases/askwheat
askWheat
org.plantdatabases/askwheat in the official MCP registry.
Endpoint https://askwheat.plantdatabases.org/mcp.
The registry describes it as: Wheat genes, Watkins pangenome, EMS mutants, expression, genotypes, germplasm and papers (WheatIS)
We read its 54 tools on 2026-11-14. 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 about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http askwheat https://askwheat.plantdatabases.org/mcp{
"mcpServers": {
"askwheat": {
"url": "https://askwheat.plantdatabases.org/mcp"
}
}
}code --add-mcp '{"name":"askwheat","type":"http","url":"https://askwheat.plantdatabases.org/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.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
search_data find_germplasm data_sources resolve_gene gene_function genes_in_region find_marker wheat_homologues wheat_mutants wheat_variants_in_region wheat_mutant_line wheat_knockout_screen watkins_gene_presence watkins_gene_accessions watkins_compare_groups watkins_find_genes watkins_accession watkins_phenotypes watkins_gene_trait watkins_populations watkins_population_phenotypes watkins_trait_genes watkins_nil_genes watkins_gene_haplotypes watkins_haplotype_trait watkins_lof_alleles watkins_accession_lof expression_experiments gene_expression expression_genes wheat_homoeologue_expression snp_lines snp_genotypes snp_compare_lines snp_haplotype_carriers snp_markers snp_phenotypes ozwheat_mtas ozwheat_lines genebank_phenotypes brapi_germplasm_studies brapi_observations wheat_gene_catalogue search_literature get_paper gene_pathways pathway_genes trait_hits genes_with_annotation gene_neighbourhood gene_papers annotate_genes blast_sequence wheat_gene_view
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-11-14):
ff573898ec11d227. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/org-plantdatabases-askwheat)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. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.