Fire extinguisher inspection, maintenance and hydrostatic test intervals by agent type

NFPA 10 sets four separate service obligations for a portable fire extinguisher (monthly visual inspection, annual maintenance, periodic internal examination, and hydrostatic pressure testing) and the interval for two of those four depends on which agent and shell the extinguisher is, in a way that is scattered across several sections and a table rather than stated as one list. A record here is one obligation for one extinguisher type/shell combination, with the interval and the NFPA 10 section it comes from. Answers 'how often does a CO2 extinguisher need hydrostatic testing', 'does a stainless steel dry chemical extinguisher get the same 12-year hydro interval as a standard one', 'how often does a wet chemical K-class extinguisher need internal examination', and 'my dry chemical extinguisher is nonrechargeable, when does it get replaced instead of retested'. The exceptions are where a facility manager gets this wrong: stainless steel dry chemical shells get the 5-year interval that pressurized-water and CO2 units get, not the 12-year interval every other dry chemical extinguisher gets, and nonrechargeable stored-pressure extinguishers skip hydrostatic testing entirely in favor of a hard 12-year removal-from-service date. Two authorities are carried side by side, because a US workplace is answerable to both and they are not word-for-word identical: NFPA 10, as restated for regulated facilities by the Minnesota Department of Health, and OSHA's own general-industry standard at 29 CFR 1910.157, whose Table L-1 sets hydrostatic intervals directly in regulation and names types the NFPA summary does not (foam, AFFF, Halon 1211 and 1301, dry powder, wetting agent). Where the two overlap they agree, and each row says which rulebook it answers to.

The data

Where this came from

Every record above links the page it was taken from and quotes the sentence that states it. These are the 2 sources this dataset was assembled from.

• health.state.mn.ushttps://www.health.state.mn.us/facilities/regulation/engineering/docs/lscfireext.pdf
• ecfr.govhttps://www.ecfr.gov/current/title-29/subtitle-B/chapter-XVII/part-1910/subpart-L/section-1910.157

Machine-readable

• data.jsonThe whole dataset — every record with its source URL and source quote.
• Open Knowledge Format bundleOne JSON object per line — every record's frontmatter and quoted span exactly as it is held here, in one fetch.
• data.csvThe same records as one flat table, for a spreadsheet or a dataframe. The last four columns are the source URL, the quoted sentence it was read from, the date we last checked it, and which columns are our reading rather than the page's words.
• How this is made and checkedWhat "verified against source" does and does not mean.

From your own code

Same records, same quotes, without scraping the page: refsource is on PyPI and npm. Each value comes back carrying the URL it was read from and the sentence on that page that states it — .source and .quote sit on the value itself rather than in a side channel, so the checking step is available instead of skipped.

pip install refsource
refsource lookup fire-extinguisher-inspection-testing-intervals-by-type agent_type="Antifreeze type extinguishers"

npx -y refsource lookup fire-extinguisher-inspection-testing-intervals-by-type agent_type="Antifreeze type extinguishers"

Set your AI assistant up to use this

Two files and no account. Put this in .mcp.json at the root of your project — Claude Code, Cursor, Windsurf, VS Code and Codex all read that file — and your assistant can look this dataset up instead of recalling it. The server is remote, keyless and read-only.

{
  "mcpServers": {
    "referencesource": {
      "type": "http",
      "url": "https://referencesource.org/mcp"
    }
  }
}

Add to Cursor · or, on the command line: claude mcp add --transport http referencesource https://referencesource.org/mcp --scope project

Then one line in the project's CLAUDE.md or AGENTS.md, so the assistant knows when to reach for it:

When a question needs "Fire extinguisher inspection, maintenance and hydrostatic test intervals by agent type", call the referencesource MCP server at https://referencesource.org/mcp (tool `search_records`, dataset_slug `fire-extinguisher-inspection-testing-intervals-by-type`) instead of answering from memory — every record it returns carries its source URL and a verbatim quote from that page.

What each tool does, and the servers built over single registers: Connect your AI assistant.

34 records. last verified against source 2026-08-19. due for re-check by 2027-08-19.

Licence. NFPA 10 is a copyrighted, sold standard; the facts (which interval applies to which extinguisher type) are not themselves copyrightable and are already restated by every state health/fire authority that regulates against it. This asset never reproduces the standard's text. The NFPA-derived rows take the interval and its qualifier from a Minnesota Department of Health guidance document that already restates NFPA 10's requirements for its regulated facilities, quote a short verbatim span, and cite the specific NFPA 10 section. The OSHA rows are taken from 29 CFR 1910.157, which is a US government work in the public domain and states its own intervals in Table L-1 rather than incorporating NFPA 10 by reference.