VetAid — VA Claim Intelligence

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

使うべきか

品質と安全性

A
説明の品質
100%
スキーマの完全性
61%
命名の品質
89%
ポイズニングのリスク
100%
権限の一致
100%
プロトコルへの準拠
100%

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~2,236トークン数(ツール定義)
~453 B一般的なレスポンスサイズ
注意への影響は中程度(128k コンテキストの 1.75%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

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

リモートエンドポイント

https://vetaid.ai/mcpstreamable-http
https://vetaid-mcp.onrender.com/mcpstreamable-http

できること

ツール一覧

ツール(9)

🟢 読み取り専用🟡 書き込み🔴 削除⚪ 不明
🟢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, 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.

入力スキーマ

{
  "type": "object",
  "properties": {},
  "title": "va_denial_statsArguments"
}
🟢va_condition_intelligence(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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "condition": {
      "title": "Condition",
      "type": "string"
    }
  },
  "required": [
    "condition"
  ],
  "title": "va_condition_intelligenceArguments"
}
🟢va_top_authorities(kind, condition, limit)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "kind": {
      "default": "cases",
      "title": "Kind",
      "type": "string"
    },
    "condition": {
      "default": "",
      "title": "Condition",
      "type": "string"
    },
    "limit": {
      "default": 25,
      "title": "Limit",
      "type": "integer"
    }
  },
  "title": "va_top_authoritiesArguments"
}
🟢va_evidence_that_wins(condition, benefit)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "condition": {
      "title": "Condition",
      "type": "string"
    },
    "benefit": {
      "default": "service_connection",
      "title": "Benefit",
      "type": "string"
    }
  },
  "required": [
    "condition"
  ],
  "title": "va_evidence_that_winsArguments"
}
🟢va_manual_changes(condition, topic, since)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "condition": {
      "default": "",
      "title": "Condition",
      "type": "string"
    },
    "topic": {
      "default": "",
      "title": "Topic",
      "type": "string"
    },
    "since": {
      "default": "",
      "title": "Since",
      "type": "string"
    }
  },
  "title": "va_manual_changesArguments"
}
🟢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.

入力スキーマ

{
  "type": "object",
  "properties": {},
  "title": "list_my_va_casesArguments"
}
🟢get_my_case_analysis(case_id)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "case_id": {
      "title": "Case Id",
      "type": "string"
    }
  },
  "required": [
    "case_id"
  ],
  "title": "get_my_case_analysisArguments"
}
🟢get_my_vetaid_account

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.

入力スキーマ

{
  "type": "object",
  "properties": {},
  "title": "get_my_vetaid_accountArguments"
}
🟡run_my_case_analysis(case_id)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "case_id": {
      "title": "Case Id",
      "type": "string"
    }
  },
  "required": [
    "case_id"
  ],
  "title": "run_my_case_analysisArguments"
}

推奨プロンプト

retrieve_data
Get details about [item] from VetAid — VA Claim Intelligence
想定されるツール: get_my_case_analysis
fetch_info
Fetch [information type] using VetAid — VA Claim Intelligence
想定されるツール: get_my_case_analysis
list_items
List all [items] available in VetAid — VA Claim Intelligence
想定されるツール: list_my_va_cases
browse_collection
Show me the [collection] from VetAid — VA Claim Intelligence
想定されるツール: list_my_va_cases
explore_workflow
List available [items], then get details for each one using VetAid — VA Claim Intelligence
想定されるツール: list_my_va_casesget_my_case_analysis

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 9 件
検証済みバージョンは記録されていませんツール 9 件
検証済みバージョンは記録されていませんツール 9 件