Home / MCP registry index / app.veteranhq/va-disability-benefits
VeteranHQ
app.veteranhq/va-disability-benefits in the official MCP registry.
Endpoint https://api.veteranhq.app/mcp.
The registry describes it as: Veterans benefits and VA claims reference: VA disability ratings, compensation rates, 38 CFR search
We read its 14 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
calculate_combined_rating compare_rating_criteria analyze_rating_gap calculate_rolling_window find_secondary_conditions check_presumptive_eligibility search_legal_authority prepare_cp_exam lookup_compensation_rate compute_retroactive_pay find_claim_help search_guides get_guide find_veteran_benefits
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-veteranhq-va-disability-benefits)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.