Skip to content

VetAid — VA Claim Intelligence MCP server

ai.vetaid/vetaidvetaid.aistreamable-httpv1.0.0Scanned

Real Board of Veterans' Appeals outcome data for VA disability claims. No key needed.

9 tools: 6 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 6 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the VetAid — VA Claim Intelligence MCP server can do

The VetAid — VA Claim Intelligence MCP server is published by vetaid.ai, a domain the MCP Registry verified. It has 9 tools. It can create or change data (6 tools: va_denial_stats, va_condition_intelligence, va_top_authorities, va_evidence_that_wins and 2 more), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 6Claude Code: ask
  • run_my_case_analysisRUN the full VetAid (the veterans claims tool) analysis pipeline on one of the veteran's OWN cases, ON THE VETERAN'S BEHALF.No findings

    Why it is in this group

    • The name "run_my_case_analysis" says "run": a word for a change.
    Description, as the server wrote it
    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 poll get_my_case_analysis(case_id) for the results. Requires a WRITE-scoped agent key: the veteran must have created the key with the 'Allow running analyses' (read_write) scope. A read-only key returns a 'read-only key' error; the daily limit returns 'rate limited'; a case the key owner does not own returns 'not found' (no cross-user access). Args: case_id: The id of one of the veteran's own cases (from list_my_va_cases).

    Annotations the server declares

    • title: Run my case analysis
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
  • va_condition_intelligenceReal 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 / DE…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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, so they sum to 100%; complete years, with an all-years block labelled separately), the year-by-year trend, which kinds of evidence went with a grant versus without, the denial reasons tagged in a smaller hand-tagged sample (labelled with its own n), and the legal authorities most cited. Aggregate data only — no PII, and a base rate for appealed cases, not a prediction for one veteran. Args: condition: VA condition keyword, e.g. 'ptsd', 'tinnitus', 'sleep apnea', 'back', 'knee', 'depression', 'gerd', 'migraines'. An unmatched value returns the list of valid condition keys.

    Annotations the server declares

    • title: BVA outcomes by condition
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
  • va_denial_statsCorpus-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 …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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, and the most-litigated conditions with their own shares. Rates are shares of ALL decided issues, so they sum to 100%, and they use complete crawl years only (an all-years block is included and labelled). Aggregate data only — contains no individual veteran's information.

    Annotations the server declares

    • title: VA appeal denial statistics
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
  • va_evidence_that_winsMEASURED 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 priv…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 treatment records that document the condition (or are silent), a Board hearing, and how the Board read the record (credibility, benefit of the doubt, inadequate exam) — how often the issue was GRANTED when the record had it versus when it did not, with the raw fractions. Single-issue decisions only, so each evidence flag attaches to exactly one decided issue. Use this to say which missing evidence has historically mattered most and by how much; it is an association in appealed cases, not a prediction. Aggregate data only — no PII. Args: condition: VA condition keyword, e.g. 'ptsd', 'sleep apnea', 'back', 'knee', 'tinnitus'. benefit: 'service_connection' (default), 'increased_rating', 'tdiu', 'effective_date', or 'all'.

    Annotations the server declares

    • title: Evidence vs. outcome by condition
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
  • va_manual_changesRecent changes to the VA M21-1 adjudication manual and its sibling VBA manuals — the changelog VA does not publish.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 was added and removed, a link to the current official article, and the conditions and claim topics it touches. Use this when asked whether a VA rule changed recently, or when a claim's stage (exams, nexus, TDIU, SMC, effective dates, Higher-Level Review, Supplemental Claims, Board appeals) may be affected. Args: condition: optional condition keyword to filter by (e.g. 'ptsd', 'hearing'). topic: optional claim topic: tdiu, smc, effective_date, cue, hlr, supplemental_claim, board_appeal, intent_to_file, presumption, secondary, exams, nexus, lay_evidence, strs, dic, pension, pact, reduction, duty_to_assist, rating_schedule. since: optional ISO date (YYYY-MM-DD); only changes whose new version is dated on/after it.

    Annotations the server declares

    • title: VA M21-1 manual change log
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
  • va_top_authoritiesThe 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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, Sharp), 38 C.F.R. regulations, or 38 U.S.C. statutes — ranked by the number of DISTINCT decisions that cite them. Useful for explaining which precedents actually carry VA appeals. The response carries a 'basis' string saying exactly what was counted and over how many decisions; read it before quoting a number. Aggregate data only — no PII. Args: kind: 'cases' (default), 'regulations', or 'statutes'. condition: optional condition keyword (e.g. 'ptsd', 'tinnitus', 'back') to rank authorities within that condition's decisions only. limit: how many to return, 1-100 (default 25).

    Annotations the server declares

    • title: Most-cited VA legal authorities
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
Only reads 3Show 3 read-only tools
  • get_my_case_analysisGet a per-stage analysis SUMMARY for one of the veteran's OWN cases (read-only; never starts an analysis).No findings

    Why it is in this group

    • The name "get_my_case_analysis" says "get": a word for reading.
    Description, as the server wrote it
    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 any case the key owner does not own — no cross-user access. Args: case_id: The id of one of the veteran's own cases (from list_my_va_cases).

    Annotations the server declares

    • title: Get my case analysis
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
  • get_my_vetaid_accountCheck the veteran's VetAid account (plan and the legacy credits field).No findings

    Why it is in this group

    • The name "get_my_vetaid_account" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: My VetAid account and credits
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
  • list_my_va_casesList the veteran's OWN VA cases (read-only).No findings

    Why it is in this group

    • The name "list_my_va_cases" says "list": a word for reading.
    Description, as the server wrote it
    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. Only ever returns the key owner's data.

    Annotations the server declares

    • title: List my VA cases
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:28 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://vetaid.ai/mcp: tools/list returned 9 tools to an anonymous client, including va_denial_stats (write), va_condition_intelligence (write), va_top_authorities (write), va_evidence_that_wins (write), va_manual_changes (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http vetaid https://vetaid.ai/mcp
claude mcp add --transport http vetaid https://vetaid.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__vetaid__list_my_va_cases",
      "mcp__vetaid__get_my_case_analysis",
      "mcp__vetaid__get_my_vetaid_account"
    ],
    "ask": [
      "mcp__vetaid__va_denial_stats",
      "mcp__vetaid__va_condition_intelligence",
      "mcp__vetaid__va_top_authorities",
      "mcp__vetaid__va_evidence_that_wins",
      "mcp__vetaid__va_manual_changes",
      "mcp__vetaid__run_my_case_analysis"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as vetaid. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.vetaid/vetaid/verify?hash=561d5428d55196a8a466bfd1fe70bebdb9e139fc1b376939613ca9f0e8d0a93b" | jq -e '.changed == false'

Pinned hash 561d5428d551, from Nov 11, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.vetaid/vetaid/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.vetaid/vetaid
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.vetaid/vetaid.svg)](https://radar.anlyon.com/servers/ai.vetaid/vetaid)

Source: MCP Registry. Synced Oct 21, 2026, 17:43 UTC.

VetAid — VA Claim Intelligence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the VetAid — VA Claim Intelligence MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the VetAid — VA Claim Intelligence MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the VetAid — VA Claim Intelligence MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the VetAid — VA Claim Intelligence MCP server have?

9 tools: 6 write, 3 read. va_denial_stats, va_condition_intelligence, va_top_authorities, va_evidence_that_wins, va_manual_changes, run_my_case_analysis, list_my_va_cases, get_my_case_analysis and 1 more.

Does the VetAid — VA Claim Intelligence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the VetAid — VA Claim Intelligence MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the VetAid — VA Claim Intelligence MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.