VetAid — VA Claim Intelligence
REMOTE · VETAID-MCP.ONRENDER.COM · 2 COMPONENTS · SCANNED SEP 24
Real Board of Veterans' Appeals outcome data for VA disability claims. No key needed.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the VetAid — VA Claim Intelligence MCP server?
VetAid — VA Claim Intelligence is a hosted endpoint at https://vetaid-mcp.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · vetaid-mcp.onrender.com
claude mcp add --transport http ai-vetaid-vetaid 'https://vetaid-mcp.onrender.com/mcp'
{
"mcpServers": {
"ai-vetaid-vetaid": {
"url": "https://vetaid-mcp.onrender.com/mcp"
}
}
} {
"servers": {
"ai-vetaid-vetaid": {
"type": "http",
"url": "https://vetaid-mcp.onrender.com/mcp"
}
}
} [mcp_servers.ai-vetaid-vetaid] url = "https://vetaid-mcp.onrender.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-vetaid-vetaid": {
"type": "remote",
"url": "https://vetaid-mcp.onrender.com/mcp",
"enabled": true
}
}
} openclaw mcp add ai-vetaid-vetaid --url 'https://vetaid-mcp.onrender.com/mcp' --transport streamable-http
mcp_servers:
ai-vetaid-vetaid:
url: "https://vetaid-mcp.onrender.com/mcp" {
"McpServers": {
"ai-vetaid-vetaid": {
"Transport": "http",
"Url": "https://vetaid-mcp.onrender.com/mcp"
}
}
} assistant mcp add ai-vetaid-vetaid -t streamable-http -u 'https://vetaid-mcp.onrender.com/mcp'
{
"mcpServers": {
"ai-vetaid-vetaid": {
"type": "http",
"url": "https://vetaid-mcp.onrender.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 −51
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.47 → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +7
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Tool “va_denial_stats” rewrote its description, which is the text the model reads security
- Tool “va_condition_intelligence” rewrote its description, which is the text the model reads security
- Tool “va_top_authorities” rewrote its description, which is the text the model reads security
- Schema quality: 148 → 187 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- “va_top_authorities” added an optional parameter “condition” cosmetic
- “va_top_authorities” added an optional parameter “kind” cosmetic
- “va_top_authorities” added an optional parameter “limit” cosmetic
- Tool “get_my_case_analysis” changed its title: Get my case analysis cosmetic
- Tool “get_my_vetaid_account” changed its title: My VetAid account and credits cosmetic
- Tool “list_my_va_cases” changed its title: List my VA cases cosmetic
- Tool “run_my_case_analysis” changed its title: Run my case analysis (uses a credit) cosmetic
- Tool “va_condition_intelligence” changed its title: BVA outcomes by condition cosmetic
- Tool “va_denial_stats” changed its title: VA appeal denial statistics cosmetic
- Tool “va_evidence_that_wins” changed its title: Evidence vs. outcome by condition cosmetic
- Tool “va_manual_changes” changed its title: VA M21-1 manual change log cosmetic
- Tool “va_top_authorities” changed its title: Most-cited VA legal authorities cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://vetaid-mcp.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vetaid-mcp.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 503 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vetaid-mcp.onrender.com/mcp | HTTP error | 503 | |
| http (plaintext) | http://vetaid-mcp.onrender.com/mcp | HTTPS enforced | 301 | https://vetaid-mcp.onrender.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_my_case_analysis Get my case analysis ~115
Get a per-stage analysis SUMMARY for one of the veteran's OWN cases (read-only; never runs a paid 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).
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
No output schema declared.
No examples provided.
get_my_vetaid_account My VetAid account and credits ~59
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). Requires the veteran's personal agent key (Bearer vak_...). Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_my_va_cases List my VA cases ~74
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_my_case_analysis Run my case analysis (uses a credit) ~215
RUN the full VetAid analysis pipeline on one of the veteran's OWN cases, ON THE VETERAN'S BEHALF. This SPENDS one of the veteran's analysis credits (free plan: first 2 free, then $9.99 each) and 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; out of credits returns 'no credits'; a case the key owner does not own returns 'not found' (no cross-user access). Consider calling get_my_vetaid_account() first to confirm a credit is available. Args: case_id: The id of one of the veteran's own cases (from list_my_va_cases).
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
No output schema declared.
No examples provided.
va_condition_intelligence BVA outcomes by condition ~235
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.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | yes | – |
No output schema declared.
No examples provided.
va_denial_stats VA appeal denial statistics ~131
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
va_evidence_that_wins Evidence vs. outcome by condition ~271
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| benefit | string | – | – |
| condition | string | yes | – |
No output schema declared.
No examples provided.
va_manual_changes VA M21-1 manual change log ~269
Recent changes to the VA M21-1 adjudication manual and its sibling VBA manuals — the changelog VA does not publish. VetAid 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.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | – | – |
| since | string | – | – |
| topic | string | – | – |
No output schema declared.
No examples provided.
va_top_authorities Most-cited VA legal authorities ~247
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).
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | – | – |
| kind | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
What is the VetAid — VA Claim Intelligence MCP server?
VetAid — VA Claim Intelligence is an MCP server listed in the public MCP registry as ai.vetaid/vetaid. Real Board of Veterans' Appeals outcome data for VA disability claims. No key needed. This page covers its hosted endpoint (https://vetaid-mcp.onrender.com/mcp).
Is the VetAid — VA Claim Intelligence MCP server safe to use?
VetAid — VA Claim Intelligence scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the VetAid — VA Claim Intelligence MCP server expose?
VetAid — VA Claim Intelligence exposes 9 tools: va_denial_stats, va_condition_intelligence, va_top_authorities, va_evidence_that_wins, va_manual_changes, and 4 more. Their descriptions and schemas cost roughly 1,616 tokens of context every time the server is loaded.
Does the VetAid — VA Claim Intelligence MCP server require authentication?
No. We connected to VetAid — VA Claim Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the VetAid — VA Claim Intelligence MCP server still maintained?
VetAid — VA Claim Intelligence is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.