Home / MCP registry index / io.github.vitalsvault/vitals-vault
Vitals Vault
io.github.vitalsvault/vitals-vault in the official MCP registry.
Endpoint https://mcp.vitalsvault.com/mcp.
The registry describes it as: Find public biomarker education, available blood tests, panels, and budget-aware starting points.
We read its 17 tools on 2026-10-22. 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.
Tools it advertises
list_biomarker_categories get_biomarker_category search_biomarkers get_biomarker browse_biomarkers get_biomarkers list_lab_packages get_lab_package search_lab_catalog get_lab_catalog_item recommend_panel start_guided_panel_builder create_checkout_link compare_blood_testing_services get_page_as_markdown search fetch
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-vitalsvault-vitals-vault)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.