com.veterans-rights/bva-corpus
com.veterans-rights/bva-corpus · 1.1.0
900,000+ Board of Veterans' Appeals decisions: VA outcomes, grant rates, PACT Act, ratings.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://www.veterans-rights.com/api/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 10 tools.
- Protocol
- 2025-06-18
- Calls itself
- veterans-rights-hub 1.1.0
- Handshake time
- 167 ms
- HTTP status
- 200
The tools it lists (10, as of 2 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
search_bva_decisionsSearch real U.S. Board of Veterans’ Appeals (BVA) decisions by keyword, claimed condition, disposition (granted/denied/remanded), toxic-exposure basis, service-connection theory, PACT Act, and date. Returns vetted decisions with a plain-English summary, the deciding factor, and a link to the full decision. Use to ground any claim about how VA appeals have actually been decided.
find_similar_appealsFind 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.
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 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.
explain_appeal_optionsExplain a veteran’s options after a VA decision under the Appeals Modernization Act (AMA): the three review lanes — Higher-Level Review, Supplemental Claim, and Board Appeal — and the three Board dockets (Direct Review, Evidence Submission, Hearing). Returns what each is, whether new evidence is allowed, who reviews it, when each is the best fit, and the general 1-year deadline. Optionally tailors a suggested starting point based on whether new evidence exists or a hearing is wanted. Educational only, not legal advice.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.veterans-rights/bva-corpus, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 75 days ago. The registry entry · www.veterans-rights.com