Skip to content

bva-corpus MCP server

com.veterans-rights/bva-corpusveterans-rights.comstreamable-httpv1.2.0Scanned

VA disability claims and appeals, grounded in Board of Veterans' Appeals decisions.

10 tools: 2 change things and 8 only read.

Tools: 0 delete, 0 irreversible, 2 write, 8 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the bva-corpus MCP server can do

The bva-corpus MCP server is published by veterans-rights.com, a domain the MCP Registry verified. It has 10 tools. It can create or change data (2 tools: check_presumptive_conditions and estimate_combined_rating), but cannot delete data. 8 tools only read.

2 tools read private data (get_claim_process and get_corpus_stats); 1 tool brings in text other people can write (get_claim_process).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 1.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Changes things 2Claude Code: ask
  • check_presumptive_conditionsCheck whether a condition may be a PRESUMPTIVE service connection for a veteran — meaning VA presumes it is service-connected for qualifying service/exposure, so no medical nexus n…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check whether a condition may be a PRESUMPTIVE service connection for a veteran — meaning VA presumes it is service-connected for qualifying service/exposure, so no medical nexus needs to be proven. Covers Agent Orange/herbicides, PACT Act burn pits & airborne hazards, Camp Lejeune water, ionizing radiation, and Gulf War illness. Returns who qualifies, the legal basis, representative conditions, and how many vetted BVA decisions granted on this basis. Lists are representative, not exhaustive; educational only.

    Annotations the server declares

    • title: Check presumptive conditions
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • estimate_combined_ratingCalculate a veteran’s VA combined disability rating from individual ratings, using the official whole-person formula (38 CFR § 4.25) — ratings do NOT add (e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Calculate a veteran’s VA combined disability rating from individual ratings, using the official whole-person formula (38 CFR § 4.25) — ratings do NOT add (e.g. 50% + 30% combines to 65% and rounds to 70%, not 80%). Supports the bilateral factor for paired-limb disabilities (§ 4.26). Returns the exact combined value, the final rating rounded to the nearest 10, and a step-by-step breakdown. Deterministic estimate for education; VA controls the official rating.

    Annotations the server declares

    • title: Estimate combined rating
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
Only reads 8Show 8 read-only tools
  • explain_appeal_optionsExplains the VA review options for a decision stage.No findings

    Why it is in this group

    • The name "explain_appeal_options" says "explain": a word for reading.
    Description, as the server wrote it
    Explains the VA review options for a decision stage. Initial/Supplemental, Higher-Level Review and final Board decisions have different options, and a preference for a hearing or new evidence does not establish eligibility. Tailored options are returned only when the decision stage and ordinary modernized-review eligibility are confirmed; unknown, legacy, contested, remand-only and pending-review contexts return general information without tailored lanes. Does not calculate personal deadlines. Educational only.

    Annotations the server declares

    • title: Explain appeal options
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • find_accredited_repFinds VA-accredited representatives for a disability claim or appeal, filtered by state, city and type.No findings

    Why it is in this group

    • The name "find_accredited_rep" says "find": a word for reading.
    Description, as the server wrote it
    Finds VA-accredited representatives for a disability claim or appeal, filtered by state, city and type. Results list free Veterans Service Organization (VSO) representatives first, then accredited claims agents and attorneys. Attorneys and agents may generally charge for work after notice of the initial VA decision, subject to VA fee rules and a written agreement. Not legal advice; not affiliated with the VA.

    Annotations the server declares

    • title: Find an accredited representative
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • find_similar_appealsFind source-linked recent Board decisions mentioning one or more canonical conditions.No findings

    Why it is in this group

    • The name "find_similar_appeals" says "find": a word for reading.
    Description, as the server wrote it
    Find source-linked recent Board decisions mentioning one or more canonical conditions. Resolves exact names, slugs and aliases; inspects at most the 50 most recent indexed decisions per condition, then applies optional decision-level filters. Results are research examples, not a representative sample, complete filtered cohort, condition-specific outcomes or chances of winning. Grant rates are withheld. Verify each issue against the original Board decision.

    Annotations the server declares

    • title: Find similar appeals
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_claim_processPlain-English guide to the 8 stages of a VA disability claim, from Intent to File through the C&P exam, the rating decision, the three AMA review lanes, the Board of Veterans’ Appe…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_claim_process" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    • untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
    Description, as the server wrote it
    Plain-English guide to the 8 stages of a VA disability claim, from Intent to File through the C&P exam, the rating decision, the three AMA review lanes, the Board of Veterans’ Appeals, and the 120-day deadline to appeal to the Court of Appeals for Veterans Claims. With no arguments, returns an overview of all stages with typical durations; with a stage number (1–8), returns that stage in depth: what to expect, typical timing, a key tip, and do/don’t guidance. Covers what happens after filing, what a C&P exam is, and what each stage involves. Educational only, not legal advice.

    Annotations the server declares

    • title: VA claim process guide
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_condition_reportFor a single condition (by slug like "ptsd" or "sleep-apnea", or by common name/alias like "PTSD", "acid reflux", "ringing in the ears"), return a full corpus-grounded report: how …No findings

    Why it is in this group

    • The name "get_condition_report" says "get": a word for reading.
    Description, as the server wrote it
    For a single condition (by slug like "ptsd" or "sleep-apnea", or by common name/alias like "PTSD", "acid reflux", "ringing in the ears"), return a full corpus-grounded report: how Board decisions mentioning it turned out (whole-decision granted / partly granted / remanded / denied), decision-level service-connection theory labels, an explicit decision-level attribution limitation and a notice that unverified extracted ratings are withheld, and — when available — a plain-English, source-cited summary of how the VA defines and rates the condition. Educational statistics, not a prediction or legal advice.

    Annotations the server declares

    • title: Condition report
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_corpus_statsReturns current statistics about the Veterans’ Rights archive: the number of vetted Board of Veterans’ Appeals decisions, the distribution of outcomes (granted / denied / remanded …Reads private dataNo findings

    Why it is in this group

    • The name "get_corpus_stats" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "directory": it reads files.
    Description, as the server wrote it
    Returns current statistics about the Veterans’ Rights archive: the number of vetted Board of Veterans’ Appeals decisions, the distribution of outcomes (granted / denied / remanded / mixed), the date range the decisions cover, and the number of accredited representatives in the directory. Shows how much data the archive holds and how current it is. Counts reflect only quality-filtered, publicly visible decisions.

    Annotations the server declares

    • title: Corpus statistics
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • list_conditionsLists the standardized conditions the Veterans’ Rights archive organizes Board of Veterans’ Appeals decisions under, each with its slug, body-system category and full-archive count…No findings

    Why it is in this group

    • The name "list_conditions" says "list": a word for reading.
    Description, as the server wrote it
    Lists the standardized conditions the Veterans’ Rights archive organizes Board of Veterans’ Appeals decisions under, each with its slug, body-system category and full-archive counts of vetted decisions, grants and remands. Counts describe whole decisions mentioning each condition, not condition-specific wins or individual chances. Counts reflect only quality-filtered, publicly visible decisions.

    Annotations the server declares

    • title: List conditions
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • search_bva_decisionsSearch the incomplete historical Board of Veterans’ Appeals archive using English full-text websearch over summaries, reasoning and condition text, with exact condition and optiona…No findings

    Why it is in this group

    • The name "search_bva_decisions" says "search": a word for reading.
    Description, as the server wrote it
    Search the incomplete historical Board of Veterans’ Appeals archive using English full-text websearch over summaries, reasoning and condition text, with exact condition and optional disposition, exposure, theory, PACT Act and date filters. Full-text matching is not literal substring matching. Returns up to 25 recent matching decisions, not a total count. New imports are paused; archive ends April 30, 2026. Summaries are AI-assisted; verify each issue against the original VA source.

    Annotations the server declares

    • title: Search BVA decisions
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:49 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.veterans-rights.com/api/mcp: tools/list returned 10 tools to an anonymous client, including check_presumptive_conditions (write), estimate_combined_rating (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools7 changed.~7 changedView diff

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http bva-corpus https://www.veterans-rights.com/api/mcp
claude mcp add --transport http bva-corpus https://www.veterans-rights.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__bva-corpus__search_bva_decisions",
      "mcp__bva-corpus__find_similar_appeals",
      "mcp__bva-corpus__explain_appeal_options",
      "mcp__bva-corpus__find_accredited_rep",
      "mcp__bva-corpus__get_claim_process",
      "mcp__bva-corpus__get_corpus_stats",
      "mcp__bva-corpus__list_conditions",
      "mcp__bva-corpus__get_condition_report"
    ],
    "ask": [
      "mcp__bva-corpus__check_presumptive_conditions",
      "mcp__bva-corpus__estimate_combined_rating"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bva-corpus. Review it before you use it.

Capability tags behind 2 rules
  • mcp__bva-corpus__get_claim_process private-data, untrusted-input
  • mcp__bva-corpus__get_corpus_stats private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.veterans-rights/bva-corpus/verify?hash=7b7c6f6ab1f7260e21faa0cce2794a29bdebd31399b0895c4b423346a6360f77" | jq -e '.changed == false'

Pinned hash 7b7c6f6ab1f7, from Nov 14, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.veterans-rights/bva-corpus/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.veterans-rights/bva-corpus
[![Anlyon Radar](https://radar.anlyon.com/badge/com.veterans-rights/bva-corpus.svg)](https://radar.anlyon.com/servers/com.veterans-rights/bva-corpus)

Source: MCP Registry. Synced Nov 14, 2026, 00:17 UTC.

bva-corpus MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the bva-corpus MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the bva-corpus MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the bva-corpus MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the bva-corpus MCP server have?

10 tools: 2 write, 8 read. check_presumptive_conditions, estimate_combined_rating, search_bva_decisions, find_similar_appeals, explain_appeal_options, find_accredited_rep, get_claim_process, get_corpus_stats and 2 more.

Does the bva-corpus MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the bva-corpus MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the bva-corpus MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.