vetaid-remote

endpoint

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

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is vetaid-remote live?

Yes — it answered the hub's last check (checked 6h ago). It answered 100% of checks over the last 30 days.

Is vetaid-remote free to use?

Yes — the hub reached it with no key and no payment.

What tools does vetaid-remote have?

9 tools: get_my_case_analysis, va_condition_intelligence, va_evidence_that_wins, run_my_case_analysis, va_top_authorities, va_denial_stats, list_my_va_cases, va_manual_changes, ….

Is vetaid-remote safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• va_top_authorities open 6h ago

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

  mcp-tool

  123456789101112131415161718192021

  {
    "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": ""
      }
    }
  }

  arguments 21 lines copy
• va_denial_stats open 30h ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "title": "va_denial_statsArguments",
    "properties": {}
  }

  arguments 5 lines copy
• list_my_va_cases open 30h ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "title": "list_my_va_casesArguments",
    "properties": {}
  }

  arguments 5 lines copy
• va_manual_changes open 6h ago

  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.

  mcp-tool

  123456789101112131415161718192021

  {
    "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": ""
      }
    }
  }

  arguments 21 lines copy
• get_my_vetaid_account open 6h ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "title": "get_my_vetaid_accountArguments",
    "properties": {}
  }

  arguments 5 lines copy
• get_my_case_analysis unknown never probed

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

  mcp-tool

  12345678910111213

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

  arguments 13 lines copy
• va_condition_intelligence unknown never probed

  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.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "title": "va_condition_intelligenceArguments",
    "required": [
      "condition"
    ],
    "properties": {
      "condition": {
        "type": "string",
        "title": "Condition"
      }
    }
  }

  arguments 13 lines copy
• va_evidence_that_wins unknown never probed

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

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "title": "va_evidence_that_winsArguments",
    "required": [
      "condition"
    ],
    "properties": {
      "benefit": {
        "type": "string",
        "title": "Benefit",
        "default": "service_connection"
      },
      "condition": {
        "type": "string",
        "title": "Condition"
      }
    }
  }

  arguments 18 lines copy
• run_my_case_analysis unknown never probed

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

  mcp-tool

  12345678910111213

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

  arguments 13 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.