# VetAid — VA Claim Intelligence (remote · vetaid.ai)

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

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `vetaid.ai`: 80/100 (this document), [markdown](https://verifymcp.io/servers/ai-vetaid-vetaid/vetaid.md), [page](https://verifymcp.io/servers/ai-vetaid-vetaid/vetaid)
- remote · `vetaid-mcp.onrender.com`: 23/100, [markdown](https://verifymcp.io/servers/ai-vetaid-vetaid/vetaid-mcp.md), [page](https://verifymcp.io/servers/ai-vetaid-vetaid/vetaid-mcp)

## Channel facts

- Endpoint: `https://vetaid.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1690 tokens (~187/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the VetAid — VA Claim Intelligence MCP server?

VetAid — VA Claim Intelligence is a hosted endpoint at https://vetaid.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "ai-vetaid-vetaid": {
      "url": "https://vetaid.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-vetaid-vetaid": {
      "type": "http",
      "url": "https://vetaid.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-vetaid-vetaid]
url = "https://vetaid.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-vetaid-vetaid": {
      "type": "remote",
      "url": "https://vetaid.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-vetaid-vetaid --url 'https://vetaid.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-vetaid-vetaid:
    url: "https://vetaid.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-vetaid-vetaid": {
      "Transport": "http",
      "Url": "https://vetaid.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-vetaid-vetaid -t streamable-http -u 'https://vetaid.ai/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-24 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (9)

### `va_denial_stats` (~131 tokens)

VA appeal denial statistics

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.

### `va_condition_intelligence` (~235 tokens)

BVA outcomes by condition

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.

Input parameters:

- `condition` (string, required)

### `va_top_authorities` (~247 tokens)

Most-cited VA legal 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, 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).

Input parameters:

- `condition` (string)
- `kind` (string)
- `limit` (integer)

### `va_evidence_that_wins` (~271 tokens)

Evidence vs. outcome by condition

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'.

Input parameters:

- `benefit` (string)
- `condition` (string, required)

### `va_manual_changes` (~269 tokens)

VA M21-1 manual change log

Recent changes to the VA M21-1 adjudication manual and its sibling VBA
    manuals — the changelog VA does not publish. VetAid 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.

Input parameters:

- `condition` (string)
- `since` (string)
- `topic` (string)

### `list_my_va_cases` (~74 tokens)

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. Only ever returns the key owner's data.

### `get_my_case_analysis` (~115 tokens)

Get my case analysis

Get a per-stage analysis SUMMARY for one of the veteran's OWN cases
    (read-only; never runs a paid 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).

Input parameters:

- `case_id` (string, required)

### `get_my_vetaid_account` (~59 tokens)

My VetAid account and credits

Check the veteran's VetAid plan and remaining analysis credits BEFORE
    running an analysis (so you can tell them if they need to buy a credit).
    Requires the veteran's personal agent key (Bearer vak_...). Read-only.

### `run_my_case_analysis` (~215 tokens)

Run my case analysis (uses a credit)

RUN the full VetAid analysis pipeline on one of the veteran's OWN cases,
    ON THE VETERAN'S BEHALF. This SPENDS one of the veteran's analysis credits
    (free plan: first 2 free, then $9.99 each) and 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; out of credits returns 'no credits'; a case the key
    owner does not own returns 'not found' (no cross-user access). Consider
    calling get_my_vetaid_account() first to confirm a credit is available.

    Args:
        case_id: The id of one of the veteran's own cases (from list_my_va_cases).

Input parameters:

- `case_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-vetaid-vetaid/vetaid#diagnostics

## Score history

- 2026-09-24: 80
- 2026-09-23: 79
- 2026-09-22: 79
- 2026-09-21: 78
- 2026-09-20: 78
- 2026-09-19: 77
- 2026-09-18: 77
- 2026-09-17: 76
- 2026-09-16: 76
- 2026-09-15: 75
- 2026-09-14: 75
- 2026-09-13: 74
- 2026-09-12: 74
- 2026-09-11: 74
- 2026-09-10: 73
- 2026-09-09: 73
- 2026-09-08: 72
- 2026-09-07: 72
- 2026-09-06: 71
- 2026-09-05: 71
- 2026-09-04: 70
- 2026-09-03: 71

## Common questions

### What is the VetAid — VA Claim Intelligence MCP server?

VetAid — VA Claim Intelligence is an MCP server listed in the public MCP registry as ai.vetaid/vetaid. Real Board of Veterans' Appeals outcome data for VA disability claims. No key needed. This page covers its hosted endpoint (https://vetaid.ai/mcp).

### Is the VetAid — VA Claim Intelligence MCP server safe to use?

VetAid — VA Claim Intelligence scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

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

VetAid — VA Claim Intelligence exposes 9 tools: va_denial_stats, va_condition_intelligence, va_top_authorities, va_evidence_that_wins, va_manual_changes, and 4 more. Their descriptions and schemas cost roughly 1,616 tokens of context every time the server is loaded.

### Does the VetAid — VA Claim Intelligence MCP server require authentication?

No. We connected to VetAid — VA Claim Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the VetAid — VA Claim Intelligence MCP server still maintained?

VetAid — VA Claim Intelligence is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://vetaid.ai/mcp
- Website: https://vetaid.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-vetaid-vetaid/vetaid.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-vetaid-vetaid/vetaid.json
- HTML version of this page: https://verifymcp.io/servers/ai-vetaid-vetaid/vetaid