StandardsForge

The already-compressed MIL-STD library for fast, offline, source-linked engineering evidence.

Download one prepared archive and search 438 compiled MIL-STD packs locally. No Git clone, PDF acquisition, corpus compilation, network query, or model call is required to use the included snapshot.

Download the prepared library · SHA-256 · Wiki · Contributing

Use the prepared library with your model

The prepared release already contains the compressed standards packs. You do not need to clone this repository, download PDFs, or compile standards. Any model host that can launch a local stdio MCP server can use the library.

Windows: download, set up, connect

This MCP installation uses only bundled files and requires 64-bit Windows and CPython 3.12. Allow room for the approximately 1 GB download plus extracted and indexed local state.

1. Download and extract standardsforge-ready-0.1.0a6.zip to a permanent folder. Open PowerShell in that extracted folder.

2. Run the included core setup, then enable the bundled MCP runtime:

   python .\setup.py
   powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\setup.ps1
   

   The first command verifies and indexes the 438 prepared packs and runs full-integrity doctor. The second installs MCP dependencies from the archive without a package index and checks a real MCP query. Setup installs all 441 packages: 438 acquisition-pinned page packs, the 810H outline, and the two reviewed 1661 recovery packs. It replays 52 source-bound real-document checks before readiness. The MCP setup prints StandardsForge is ready. when complete.

3. Get the launcher path to use in your model host:

   (Resolve-Path .\standardsforge-mcp.ps1).Path
   

   For Claude Desktop or Cursor, add this server entry to the host's MCP configuration (Claude Desktop on Windows: %APPDATA%\Claude\claude_desktop_config.json; Cursor: .cursor/mcp.json). Replace the example path with the absolute path printed above; JSON paths need doubled backslashes:

   {
     "mcpServers": {
       "standardsforge": {
         "command": "powershell.exe",
         "args": ["-NoProfile", "-ExecutionPolicy", "Bypass", "-File", "C:\\absolute\\path\\to\\standardsforge-ready-0.1.0a6\\standardsforge-mcp.ps1"]
       }
     }
   }
   

   For Claude Code, register the same local launcher:

   claude mcp add standardsforge -- powershell.exe -NoProfile -ExecutionPolicy Bypass -File (Resolve-Path .\standardsforge-mcp.ps1).Path
   claude mcp get standardsforge
   

   Restart or reconnect the host if needed so it starts the MCP server. The host should show the seven StandardsForge read tools, including list_documents, search, and get_clause.

4. Ask your model: “Use StandardsForge to list the installed MIL-STD-810 editions, find the low-pressure section, then retrieve the exact source-linked evidence. Include the page, package identity, and any coverage or review limits.”

The MCP server reads the installed local corpus. Search finds candidates; exact retrieval supplies the evidence. The model does not choose applicability, project baselines, or compliance.

Linux and macOS

The prepared core and corpus work offline on 64-bit Linux and Intel or Apple silicon macOS with CPython 3.11 or newer and SQLite FTS5. From the extracted release, run sh ./setup.sh. Connecting an MCP model host then requires a separate install of standardsforge[mcp]==0.1.0a6 from PyPI into an environment outside the extracted folder. That code install uses the network; queries still use the local prepared corpus. Follow the copy-paste host setup.

Use it without a model

From the extracted release, a CLI search is:

python .\run.py search "environmental testing" --principal local-user --query-mode natural_language --limit 5

On Linux or macOS, use sh ./standardsforge.sh in place of python .\run.py. The prepared-library guide covers installation checks and the query guide covers inventory, exact edition and package pins, and source retrieval.

The downloadable v0.1.0a6 archive is a frozen release. Its page-text packs support source-linked physical-page retrieval; its MIL-STD-810H outline-v3 has 8,319 automated, unreviewed records. It does not provide document-wide reviewed obligation classifications or a project-approved baseline. The release also includes 18 reviewed 1661 transcriptions and 41 reviewed semantic records, including five separate 4.2.4 directives; these remain bounded agent-reviewed evidence. See the validation record for the release boundary.

Install the code CLI only

python -m pip install "standardsforge==0.1.0a6"

The PyPI wheel contains code. Use the prepared archive above for the already compiled library.

What is included

The prepared snapshot contains:

• 438 compressed MIL-STD page-text packs compiled from 912 verified source PDFs;
• 35,218 source-linked page records across 35,235 physical pages;
• an automated, explicitly unreviewed MIL-STD-810H derived outline;
• the dependency-free StandardsForge core wheel, portable offline core setup and root-anchored CLI launchers, a Windows x64 CPython 3.12 hash-inventoried offline MCP wheelhouse and launcher, exact local policies, inventory, and provenance;
• one-command local indexing for offline queries.

The acquisition snapshot completed September 21, 2026 against the official DLA ASSIST dataset marked updated September 18, 2026. It includes the selected current publicly exposed components at that cutoff. It does not include historical editions, restricted bytes, other DLA document classes, or document-wide reviewed semantic interpretation.

Complete prepared library snapshot

The table below is the entire 438-pack prepared MIL-STD library snapshot as of September 21, 2026 (9/21/2026). The acquisition completed on September 21, 2026 against the official DLA ASSIST dataset marked updated September 18, 2026. Each row is a fixed snapshot of the listed current-edition composition at that cutoff; it is not a claim that DLA has not changed the record since then or that the standard applies to a particular product.

Of these packs, 413 contain the complete selected current public composition. The other 25 contain every publicly exposed current component but are explicitly partial because 26 current components are restricted and are not included. An additional 26 restricted-only active records have no readable pack and therefore are not part of this prepared library. Titles and document dates below come from the recorded DLA manifest; “public” describes the acquisition boundary, not blanket republication rights. Readable labels expand DLA suffixes such as (2) and NOT 3 to Change 2 and Notice 3 while preserving the exact DLA identifier beside them.

What the engine preserves

Evidence packets retain exact edition and package identity, source citations, any available governing context, derivation and review status, authorization scope, coverage, and known evidence limits. Missing or unclassified context remains explicit rather than being inferred.

StandardsForge supplies evidence. It does not decide applicability, approve requirements or test plans, select a project baseline, or certify compliance. Those decisions remain with the responsible engineering and program authorities.

Documentation

The source repository is for development and maintainer workflows. End users should start with the prepared release above.

Contributing and security

Read CONTRIBUTING.md before changing code, contracts, documentation, or release artifacts. Contributions must use synthetic or demonstrably redistributable fixtures and preserve exact evidence, authorization, uncertainty, and review boundaries.

Report suspected vulnerabilities through the private process in SECURITY.md, not through a public issue.

License

StandardsForge code is licensed under Apache 2.0. Standards content has separate permissions; the code license does not grant rights to third-party documents.