Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
SureForge CFR (Title 38) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Self-hosted, searchable index of US Title 38 CFR (veterans' benefits rules) built from eCFR.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user sureforge-cfr-title-38-mcp '--' npx -y cfr-free mcp
# 2 — ask your agent for something these tools do
# search_regulations, get_section, browse_title38 and 7 more
SureForge CFR (Title 38) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts SureForge CFR (Title 38) as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user sureforge-cfr-title-38-mcp '--' npx -y cfr-free mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Full-text search across the local Title 38 (VA) CFR index using ranked keyword matching.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | search terms, e.g. "traumatic brain injury compensation" |
| page | integer | no | 1-based result page (default 1) |
| per_page | integer | no | results per page (default 10, max 20) |
| part | string | no | restrict to one CFR part number |
| kind | string | no | restrict to one provision kind: section or appendix |
| chapter | string | no | restrict to one chapter, exact case-sensitive Roman numeral (e.g. "I") |
Fetch the full text of one Title 38 CFR section or appendix as markdown. Accepts flexible citations:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| citation | string | yes | the citation to read, e.g. "38 CFR 4.125" |
Navigate the Title 38 hierarchy (title → chapter → part → subpart → subject group) and list what exists at a level.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chapter | string | no | chapter identifier, e.g. "I" |
| part | string | no | part number, e.g. "4" |
| subpart | string | no | subpart letter, e.g. "B" (requires part) |
| subject_group | string | no | subject-group identifier, e.g. "ECFRd158704dcab040e" (requires part) |
Report how current the local Title 38 index is: eCFR issue date, last sync time, row counts, the
No parameter schema on file.
Enumerate every Title 38 CFR part present in the local index, with its structure-tree title
No parameter schema on file.
One-call readiness verdict for the local index: "ready" (query away), "stale" (older than
No parameter schema on file.
Offline comparison of two STORED snapshots of the Title 38 index (SQLite files, typically
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_snapshot | string | yes | path to the earlier stored snapshot, e.g. "snapshots/2026-01-01.sqlite" |
| to_snapshot | string | yes | path to the later stored snapshot, e.g. "snapshots/2026-06-01.sqlite" |
| part | string | no | restrict the comparison to one CFR part number |
One Title 38 provision as it stood at a requested date (YYYY-MM-DD, required).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| at_date | string | yes | eCFR issue date, YYYY-MM-DD |
| citation | string | yes | the citation to read, e.g. "38 CFR 4.130" |
Provision-level diff of Title 38 between two eCFR issue dates: which citations changed,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_date | string | yes | eCFR issue date, YYYY-MM-DD |
| to_date | string | yes | eCFR issue date, YYYY-MM-DD |
Line-level redline of one Title 38 provision between two eCFR issue dates: which lines of
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_date | string | yes | eCFR issue date, YYYY-MM-DD |
| to_date | string | yes | eCFR issue date, YYYY-MM-DD |
| citation | string | yes | the citation to redline, e.g. "38 CFR 4.125" (≤ 120 chars) |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install SureForge CFR (Title 38) or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (9 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
3 of the 9 recovered tools are registered only when ecfr !== undefined holds (dist/mcp/tools.js:449) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 6.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
6 tools are registered unconditionally · 3 more only when ecfr !== undefined holds (dist/mcp/tools.js:449) — typically when a key or option is configured. All 9 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_regulations | untrusted-input | untrusted-input: keyword "fetch" |
| get_section | untrusted-input | untrusted-input: keyword "fetch" |
| browse_title38 | untrusted-input | untrusted-input: keyword "browse" |
| index_status | no tags | |
| list_parts | no tags | |
| health | no tags | |
| get_section_at conditional | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| diff_issues conditional | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| redline conditional | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.2. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish SureForge CFR (Title 38) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.