Koskamo

VetAid MCP

VetAid provides an MCP server that allows AI agents to access real Board of Veterans' Appeals (BVA) outcome data, analyze VA disability claims for errors or missed conditions, and retrieve adjudication manual changes. It supports tools for querying denial statistics, condition intelligence, and evidence success rates without requiring user authentication for public tools.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

VetAid MCP logo, by VetAidVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by VetAid
MCP endpoint (Streamable HTTP)
https://vetaid-mcp.onrender.com/mcp
Vendor documentation

What its tools do

9 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Can change data (1)

9 of 9 have a description · 9 of 9 declare behavior hints · 0 of 6 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to vetaid.ai ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Query corpus-wide BVA outcome rates and denial types
  • Analyze specific conditions for affirm/reverse/remind rates
  • Retrieve weekly changes to the M21-1 adjudication manual
  • Check evidence success rates for specific benefit types

Source and maintenance

Vendor evidenceRegistry 1.0.0

Protocol and capabilities

Server
vetaid-remote 1.30.0
MCP protocol negotiated in check
2025-11-25
Tools
9 advertised
Resources
0 advertised
Resource templates
0 advertised
Prompts
0 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  },
  "prompts": {
    "listChanged": false
  },
  "resources": {
    "subscribe": false,
    "listChanged": false
  },
  "experimental": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

VetAid, the veterans claims tool (vetaid.ai), remote MCP server: VA disability claims data for U.S. military veterans, not veterinary care. VetAid is a free veterans claims tool, not a VA-accredited representative — it does not file anything with VA for you, and it works alongside your accredited VSO, claims agent or attorney. Public tools expose aggregate Board of Veterans' Appeals outcome data (no PII). The PHI tools (list_my_va_cases, get_my_case_analysis) return ONLY the caller's own VA cases and require the veteran's personal agent key in the Authorization header (Bearer vak_...). VetAid is not legal or medical advice.

Tools

9 advertised

va_denial_stats — VA appeal denial statistics
Advertised by the server during the last successful anonymous check.
Advertised read-only

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_denial_stats input schema
{
  "type": "object",
  "title": "va_denial_statsArguments",
  "properties": {}
}
va_denial_stats annotations
{
  "title": "VA appeal denial statistics",
  "readOnlyHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
va_condition_intelligence — BVA outcomes by condition
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

va_condition_intelligence input schema
{
  "type": "object",
  "title": "va_condition_intelligenceArguments",
  "required": [
    "condition"
  ],
  "properties": {
    "condition": {
      "type": "string",
      "title": "Condition"
    }
  }
}
va_condition_intelligence annotations
{
  "title": "BVA outcomes by condition",
  "readOnlyHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
va_top_authorities — Most-cited VA legal authorities
Advertised by the server during the last successful anonymous check.
Advertised read-only

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

va_top_authorities input schema
{
  "type": "object",
  "title": "va_top_authoritiesArguments",
  "properties": {
    "kind": {
      "type": "string",
      "title": "Kind",
      "default": "cases"
    },
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 25
    },
    "condition": {
      "type": "string",
      "title": "Condition",
      "default": ""
    }
  }
}
va_top_authorities annotations
{
  "title": "Most-cited VA legal authorities",
  "readOnlyHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
va_evidence_that_wins — Evidence vs. outcome by condition
Advertised by the server during the last successful anonymous check.
Advertised read-only

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

va_evidence_that_wins input schema
{
  "type": "object",
  "title": "va_evidence_that_winsArguments",
  "required": [
    "condition"
  ],
  "properties": {
    "benefit": {
      "type": "string",
      "title": "Benefit",
      "default": "service_connection"
    },
    "condition": {
      "type": "string",
      "title": "Condition"
    }
  }
}
va_evidence_that_wins annotations
{
  "title": "Evidence vs. outcome by condition",
  "readOnlyHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
va_manual_changes — VA M21-1 manual change log
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

va_manual_changes input schema
{
  "type": "object",
  "title": "va_manual_changesArguments",
  "properties": {
    "since": {
      "type": "string",
      "title": "Since",
      "default": ""
    },
    "topic": {
      "type": "string",
      "title": "Topic",
      "default": ""
    },
    "condition": {
      "type": "string",
      "title": "Condition",
      "default": ""
    }
  }
}
va_manual_changes annotations
{
  "title": "VA M21-1 manual change log",
  "readOnlyHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
list_my_va_cases — List my VA cases
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

list_my_va_cases input schema
{
  "type": "object",
  "title": "list_my_va_casesArguments",
  "properties": {}
}
list_my_va_cases annotations
{
  "title": "List my VA cases",
  "readOnlyHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
get_my_case_analysis — Get my case analysis
Advertised by the server during the last successful anonymous check.
Advertised read-only

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

get_my_case_analysis input schema
{
  "type": "object",
  "title": "get_my_case_analysisArguments",
  "required": [
    "case_id"
  ],
  "properties": {
    "case_id": {
      "type": "string",
      "title": "Case Id"
    }
  }
}
get_my_case_analysis annotations
{
  "title": "Get my case analysis",
  "readOnlyHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
get_my_vetaid_account — My VetAid account and credits
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

get_my_vetaid_account input schema
{
  "type": "object",
  "title": "get_my_vetaid_accountArguments",
  "properties": {}
}
get_my_vetaid_account annotations
{
  "title": "My VetAid account and credits",
  "readOnlyHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
run_my_case_analysis — Run my case analysis
Advertised by the server during the last successful anonymous check.

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

run_my_case_analysis input schema
{
  "type": "object",
  "title": "run_my_case_analysisArguments",
  "required": [
    "case_id"
  ],
  "properties": {
    "case_id": {
      "type": "string",
      "title": "Case Id"
    }
  }
}
run_my_case_analysis annotations
{
  "title": "Run my case analysis",
  "readOnlyHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}

Prompts

0 advertised

No prompt definitions available.

Resources

0 advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
657 ms
95th percentile latency
657 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 657 ms · metadata changed · 9 tool(s), 0 resource(s), 0 resource template(s), 0 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http vetaid-mcp https://vetaid-mcp.onrender.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add vetaid-mcp --url https://vetaid-mcp.onrender.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable vetaid-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "vetaid-mcp": {
      "url": "https://vetaid-mcp.onrender.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "vetaid-mcp": {
      "type": "streamableHttp",
      "url": "https://vetaid-mcp.onrender.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start vetaid-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "vetaid-mcp": {
      "type": "http",
      "url": "https://vetaid-mcp.onrender.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http vetaid-mcp https://vetaid-mcp.onrender.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://vetaid-mcp.onrender.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "vetaid-mcp": {
      "serverUrl": "https://vetaid-mcp.onrender.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like VetAid MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run VetAid MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing