General Tools
veterans-rights.com
Provides tools for searching VA disability appeal decisions, finding similar cases, checking presumptive conditions, explaining appeal options, and finding accredited representatives.
ENDPOINT 1
https://www.veterans-rights.com/api/mcp
MCP server metadata
- Name
- veterans-rights-hub
- Version
- 1.1.0
Known tools 10
find_similar_appealsGiven the facts of a VA disability appeal — claimed conditions, service-connection theory, toxic-exposure basis — analyze how similar real BVA decisions were decided: the grant / deny / remand breakdown, the grant rate, and representative example decisions.
Inferred read-onlycheck_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.
Inferred read-onlyexplain_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).
Inferred read-onlyfind_accredited_repFind a VA-accredited representative to help with a disability claim or appeal.
Inferred read-onlyestimate_combined_ratingCalculate a veteran’s VA combined disability rating from individual ratings, using the official whole-person formula (38 CFR § 4.
Inferred read-onlyget_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’ Appeals, and the 120-day CAVC court deadline.
Inferred read-onlyget_corpus_statsReturn live statistics about the Veterans’ Rights corpus: the number of vetted Board of Veterans’ Appeals decisions analyzed, the distribution of outcomes (granted / denied / remanded / mixed), the date range the decisions cover, and the number of accredited representatives in the directory.
Inferred read-onlylist_conditionsList the standardized conditions the Veterans’ Rights corpus organizes Board of Veterans’ Appeals decisions under, each with the number of vetted decisions, grants, and remands (full-corpus counts) and the body-system category.
Inferred read-onlyget_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 its real Board of Veterans’ Appeals appeals turned out (granted / partly granted / remanded / denied), the service-connection theories that most often won, the disability ratings most commonly assigned, recognized exposure / PACT-Act pathways, a few representative decisions, and — when available — a plain-English, source-cited summary of how the VA defines and rates the condition.
Inferred read-onlyCONNECT 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.veterans-rights-hub]
url = "https://www.veterans-rights.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"veterans-rights-hub": {
"type": "http",
"url": "https://www.veterans-rights.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: veterans-rights-hub
Remote MCP URL: https://www.veterans-rights.com/api/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": {
"veterans-rights-hub": {
"url": "https://www.veterans-rights.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"veterans-rights-hub": {
"type": "http",
"url": "https://www.veterans-rights.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "veterans-rights-hub",
"transport": "streamable-http",
"url": "https://www.veterans-rights.com/api/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.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.