Analytics

vetaid.ai

Provides analytical data and intelligence on VA appeals, conditions, legal authorities, evidence outcomes, and manual changes.

2 endpoints18 known toolsFirst detected September 3, 2026Last detected September 3, 2026

ENDPOINT 1

https://vetaid.ai/mcp

No auth detected

MCP server metadata

Name: vetaid-remote
Version: 1.26.0

Capabilities

experimentalpromptsresourcestools

Server instructions

VetAid remote MCP server. 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.

Known tools 9

va_denial_stats

Corpus-wide VA appeal statistics from 1.

Inferred read-only

va_condition_intelligence

Real Board of Veterans' Appeals outcome data for one VA condition, from 1.

Inferred read-only

va_top_authorities

The legal authorities most frequently cited across the public Board of Veterans' Appeals corpus (1.

Inferred read-only

va_evidence_that_wins

MEASURED evidence-vs-outcome data for one VA condition, from the full text of the public BVA archive (1.

Inferred read-only

va_manual_changes

Recent changes to the VA M21-1 adjudication manual and its sibling VBA manuals — the changelog VA does not publish.

Potential side effects

list_my_va_cases

List the veteran's OWN VA cases (read-only).

Inferred read-only

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

Inferred read-only

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

Inferred read-only

run_my_case_analysis

RUN the full VetAid analysis pipeline on one of the veteran's OWN cases, ON THE VETERAN'S BEHALF.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.vetaid-remote]
url = "https://vetaid.ai/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: vetaid-remote
Remote MCP URL: https://vetaid.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "vetaid-remote",
  "transport": "streamable-http",
  "url": "https://vetaid.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://vetaid-mcp.onrender.com/mcp

No auth detected

MCP server metadata

Name: vetaid-remote
Version: 1.26.0

Capabilities

experimentalpromptsresourcestools

Server instructions

Known tools 9

va_denial_stats

Corpus-wide VA appeal statistics from 1.

Inferred read-only

va_condition_intelligence

Real Board of Veterans' Appeals outcome data for one VA condition, from 1.

Inferred read-only

va_top_authorities

The legal authorities most frequently cited across the public Board of Veterans' Appeals corpus (1.

Inferred read-only

va_evidence_that_wins

MEASURED evidence-vs-outcome data for one VA condition, from the full text of the public BVA archive (1.

Inferred read-only

va_manual_changes

Recent changes to the VA M21-1 adjudication manual and its sibling VBA manuals — the changelog VA does not publish.

Potential side effects

list_my_va_cases

List the veteran's OWN VA cases (read-only).

Inferred read-only

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

Inferred read-only

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

Inferred read-only

run_my_case_analysis

RUN the full VetAid analysis pipeline on one of the veteran's OWN cases, ON THE VETERAN'S BEHALF.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.vetaid-remote]
url = "https://vetaid-mcp.onrender.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "vetaid-remote": {
      "type": "http",
      "url": "https://vetaid-mcp.onrender.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: vetaid-remote
Remote MCP URL: https://vetaid-mcp.onrender.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "vetaid-remote": {
      "url": "https://vetaid-mcp.onrender.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "vetaid-remote": {
      "type": "http",
      "url": "https://vetaid-mcp.onrender.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "vetaid-remote",
  "transport": "streamable-http",
  "url": "https://vetaid-mcp.onrender.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.