VetAid MCP server

Which servers in the official MCP registry are VetAid's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to VetAid

Whose server it is

Registry nameai.vetaid/vetaidverified in the MCP registry

The registry name sits under vetaid.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13

Stateanswerschecked 2026-10-13
Tools9
Server calls itselfvetaid-remote
Server version1.26.0
Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 52 ms.

Tools it offers9 tools · read 2026-10-13

va_denial_stats
Corpus-wide VA appeal statistics from 1.9 million public Board of Veterans' Appeals decisions, 1992 to present, updated nightly: how every decided issue came out (granted / denied / remanded / dismissed / other), the year-by-year trend…
va_condition_intelligence
Real Board of Veterans' Appeals outcome data for one VA condition, from 1.9 million public BVA decisions, 1992 to present, updated nightly: the share of decided issues GRANTED / DENIED / REMANDED / DISMISSED (shares of all decided issues…
va_top_authorities
The legal authorities most frequently cited across the public Board of Veterans' Appeals corpus (1.9 million decisions, 1992 to present, updated nightly) — case law (e.g. Gilbert v. Derwinski for benefit-of-the-doubt, DeLuca, Correia…
va_evidence_that_wins
MEASURED evidence-vs-outcome data for one VA condition, from the full text of the public BVA archive (1.8M+ decisions): for each kind of evidence — a positive nexus opinion, a private physician letter/DBQ, buddy statements, service…
va_manual_changes
Recent changes to the VA M21-1 adjudication manual and its sibling VBA manuals — the changelog VA does not publish. VetAid, the veterans claims tool, archives every KnowVA article version weekly and diffs them; each change carries what…
list_my_va_cases
List the veteran's OWN VA cases (read-only). Requires the veteran's personal VetAid agent key in the request's Authorization header (Bearer vak_...). Returns each case's id, status, timestamps, and its rated / denied / claimed conditions…
get_my_case_analysis
Get a per-stage analysis SUMMARY for one of the veteran's OWN cases (read-only; never starts an analysis). Requires the veteran's personal VetAid agent key in the request's Authorization header (Bearer vak_...). Returns 'not found' for…
get_my_vetaid_account
Check the veteran's VetAid account (plan and the legacy credits field). Analyses are free for veterans, so nothing needs to be bought before running one. Requires the veteran's personal agent key (Bearer vak_...). Read-only.
run_my_case_analysis
RUN the full VetAid (the veterans claims tool) analysis pipeline on one of the veteran's OWN cases, ON THE VETERAN'S BEHALF. Free for veterans (no credits spent); limited to 5 agent-run analyses per day. Takes ~5-8 minutes — afterward…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "vetaid": {
      "type": "http",
      "url": "https://vetaid.ai/mcp"
    }
  }
}

OpenAPI spec

233 paths, read 2026-10-13. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.