# Jobsite Safety Reference (free) (remote · jobsitecerts.com)

Free, no-login construction safety tools: OSHA rule text, toolbox talks, 1904 recordability.

- Trust score: 84/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `jobsitecerts.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/com-jobsitecerts-safety-reference/api-mcp-public.md), [page](https://verifymcp.io/servers/com-jobsitecerts-safety-reference/api-mcp-public)

## Channel facts

- Endpoint: `https://jobsitecerts.com/api/mcp/public`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2697 tokens (~299/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Jobsite Safety Reference (free) MCP server?

Jobsite Safety Reference (free) is a hosted endpoint at https://jobsitecerts.com/api/mcp/public, 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.

### Claude

```bash
claude mcp add --transport http com-jobsitecerts-safety-reference 'https://jobsitecerts.com/api/mcp/public'
```

### Cursor

```json
{
  "mcpServers": {
    "com-jobsitecerts-safety-reference": {
      "url": "https://jobsitecerts.com/api/mcp/public"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-jobsitecerts-safety-reference": {
      "type": "http",
      "url": "https://jobsitecerts.com/api/mcp/public"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-jobsitecerts-safety-reference]
url = "https://jobsitecerts.com/api/mcp/public"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-jobsitecerts-safety-reference": {
      "type": "remote",
      "url": "https://jobsitecerts.com/api/mcp/public",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-jobsitecerts-safety-reference --url 'https://jobsitecerts.com/api/mcp/public' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-jobsitecerts-safety-reference:
    url: "https://jobsitecerts.com/api/mcp/public"
```

### Netclaw

```json
{
  "McpServers": {
    "com-jobsitecerts-safety-reference": {
      "Transport": "http",
      "Url": "https://jobsitecerts.com/api/mcp/public"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-jobsitecerts-safety-reference -t streamable-http -u 'https://jobsitecerts.com/api/mcp/public'
```

### Other

```json
{
  "mcpServers": {
    "com-jobsitecerts-safety-reference": {
      "type": "http",
      "url": "https://jobsitecerts.com/api/mcp/public"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-06 (score 77, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (9)

### `lookup_jobsite_docs` (~203 tokens)

Search the Jobsite product guide

Look up how Jobsite (this product) works — features, UI navigation, terminology, account / billing, worker-side experience, what counts as a 'group' vs 'crew', etc. Use this for any 'how do I…' / 'where do I find…' / 'what does X mean in Jobsite' question. Returns matching sections from the curated product guide. NOT for OSHA / regulatory questions (use search_law_corpus) and NOT for a company's own records (its workers, certificates, jobs). If a returned section is flagged todo:true, the topic is in scope but not yet documented — say so rather than inventing an answer.

Input parameters:

- `limit` (number): Max sections to return. Defaults to 4, cap 8.
- `query` (string, required): Natural-language query, e.g. 'how do I add a worker', 'difference between groups and crews', 'where do I see expiring certs'.

### `search_articles` (~222 tokens)

Search Jobsite articles

Search Jobsite's published marketing content — blog articles, head-to-head COMPETITOR COMPARISON pages (e.g. 'Jobsite vs Procore', 'Jobsite vs SiteDocs', 'Jobsite vs SafetyCulture'), and pillar guides. Use this whenever the user asks how Jobsite compares to a competitor ('how are you better than Procore', 'Jobsite vs SafetyCulture', 'why pick you over X'), or asks for a published article on a construction-safety topic. Returns matching articles with a relevant excerpt and a link to the full page. This is DISTINCT from lookup_jobsite_docs (product how-to) and search_law_corpus (OSHA regulatory text). If nothing matches, say you don't have an article on it rather than inventing a comparison.

Input parameters:

- `limit` (number): Max articles to return. Defaults to 4, cap 6.
- `query` (string, required): Natural-language query, e.g. 'how is Jobsite better than Procore', 'Jobsite vs SiteDocs', 'confined space article'.

### `search_law_corpus` (~327 tokens)

Search the regulation corpus

Search the VERBATIM authority corpus behind Jobsite's training: 29 CFR regulation text (per-section, with citations), the CA/WA/OR state rules for heat illness and wildfire smoke, plus OSHA interpretations and NIOSH/CDC/EPA technical guidance the training cites. Use this when the user asks what an authority ACTUALLY SAYS — exact rule language, a specific citation ('what does 1926.501 require'), trigger heights, employer duties — and quote the returned text with its citation heading and jurisdiction. EVERY match carries an `authority` field: T1 is binding law, T2 is an agency interpretation and T3 is technical guidance. READ IT BEFORE YOU CHARACTERISE THE MATCH — quote a T2/T3 match as what that agency recommends or says, NEVER as what a regulation requires, and never call it a rule. It returns the source text itself, not a paraphrase of it — prefer it whenever the user wants what the rule says. The corpus spans the topics Jobsite trains on plus the authorities they cite, NOT all of 29 CFR: an empty result means 'not in the corpus', never 'no such rule exists'.

Input parameters:

- `jurisdiction` (string): Optional filter. Omit to search all jurisdictions (federal is most of the corpus).
- `limit` (number): Max sections to return. Defaults to 4, cap 8.
- `query` (string, required): Plain-words regulatory question or a citation number — 'fall protection trigger height', '1926.501', 'silica exposure control plan'.

### `search_regulatory_news` (~197 tokens)

Search regulatory news

Search recent regulatory / safety news from the Federal Register (filtered to OSHA) and the OSHA news RSS feed. Use for questions about recent rule changes, enforcement memos, or news that might affect a training course's content (e.g. 'any silica updates this year', 'recent fall protection rulemaking'). Returns titles, agencies, dates, URLs, and short summaries — pure pass-through, nothing is persisted. Prefer specific multi-word queries built around an OSHA topic or standard ('respirable silica §1926.1153', 'lockout tagout enforcement', 'fall protection 1926.501'). NOT for tenant-data questions; NOT for general OSHA reference (use search_law_corpus for established standards).

Input parameters:

- `limit` (number): Max results to return per source. Defaults to 6, cap 12.
- `query` (string, required): Natural-language search terms. Best with topical keywords plus standard numbers when known.

### `osha_recordability_check` (~340 tokens)

OSHA recordability check

Runs Jobsite's deterministic OSHA 29 CFR 1904 decision tree on the facts of an injury or illness: returns the proposed 300-log classification (or the questions still needed), the rationale with verbatim 1904 quotes, and any report-to-OSHA deadline (8 or 24 hours). Map the story to the answers; leave out anything not known — unknowns come back as questions, never guesses. Reads and writes no records.

Input parameters:

- `amputation_or_eye_loss` (boolean): Amputation (incl. a fingertip) or loss of an eye.
- `days_away` (boolean): ≥1 calendar day away after the day of injury (taken or recommended).
- `death` (boolean)
- `exception` (string): A 1904.5(b)(2) work-relatedness exception, or none.
- `inpatient_hospitalization` (boolean): Formal in-patient admission for care (not observation only).
- `loss_of_consciousness` (boolean)
- `new_case` (boolean): A new case, not a recurrence of one already recorded.
- `restricted_or_transferred` (boolean): Restricted work or job transfer beyond the day of injury.
- `significant_diagnosis` (boolean): Cancer, chronic irreversible disease, fractured/cracked bone or punctured eardrum, diagnosed by a clinician.
- `treatments` (array): Every care given ([] = none). First-aid items are the closed 1904.7(b)(5)(ii) list; anything else is medical treatment.
- `work_environment_event` (boolean): An event or exposure at work caused or contributed.

### `get_toolbox_talk` (~171 tokens)

Get a toolbox talk

A ready-to-deliver construction toolbox talk from Jobsite's library of nearly 300 talks, in English or Spanish: title, talking points, a discussion question, duration, and the OSHA standards it is built on. Find one by topic or hazard in plain words ("trenching", "heat", "ladder setup") or by standard number ("1926.501"), or fetch one by talk_number. Returns the best match plus up to five other matching titles.

Input parameters:

- `language` (string): en (default) or es (Spanish).
- `talk_number` (integer): Or one talk by its number (from other_matches).
- `topic` (string): The hazard, task or standard, e.g. "trench cave-ins", "silica", "1926.1053".

### `training_required_for` (~309 tokens)

Training a trade needs, from Jobsite's inventory

What training Jobsite's requirements inventory assigns a construction trade in a US state, optionally for roles the worker also holds (supervisor, competent person, forklift operator, scaffold erector and others). Every obligation comes from Jobsite's inventory, never from general knowledge, and carries its citation and the regulation text quoted verbatim: quote it as given. Each row's kind matters and must be kept: a mandate is an unconditional legal training duty; a condition applies only when the condition it names exists on the job; a policy is training Jobsite assigns without a legal mandate there, with its basis stated. A not-found answer means "not in Jobsite's requirements inventory", never "no training required". The inventory holds federal OSHA rows plus California, Washington, Oregon and Nevada rows. search_law_corpus returns the full text of any cited rule.

Input parameters:

- `limit` (integer): Max obligations to return (default 40, up to 80).
- `roles` (array): Roles or designations the worker also holds. A competent person is designated per topic, so pair it with topic to narrow.
- `state` (string, required): The US state the work is in: a two-letter code or name, e.g. "CA".
- `topic` (string): Narrow to one training topic.
- `trade` (string): The worker's trade in plain words, e.g. "roofer", "electrician", "sheet metal". An unknown trade returns the trades Jobsite knows.

### `verify_certificate` (~148 tokens)

Check a worker's shared certificate

Check a certificate, or a whole certificate wallet, that a worker shared from Jobsite as a link (https://jobsitecerts.com/w/…). Returns the holder's name, each credential with its issuer, issue and expiry dates, current status (current, expiring soon, expired or revoked), and its basis: earned in Jobsite training, an outside credential the employer recorded, or an employer record Jobsite has not verified. Only works with a link the worker made; it never looks a person up by name, and an expired or revoked link returns not found.

Input parameters:

- `link` (string, required): The share link the worker gave you, or the 43-character code at its end.

### `start_jobsite_workspace` (~240 tokens)

Start a sample Jobsite workspace

Create a new Jobsite workspace that holds only sample data (a sample crew, jobs and safety records; nothing real) for the person you are helping, so they can try Jobsite without setting anything up. Returns a one-time claim link to give them: opening it lets them create their login (or sign in) and own the workspace. The link expires in 7 days, and an unclaimed workspace is then deleted. Exploring the sample data is free; adding real workers needs a Jobsite plan. Takes no personal details. Limited to 3 workspaces a day per network address. Optional: company_name, focus (safety or home services) and the company's trade.

Input parameters:

- `company_name` (string): The company name for the workspace (default "Sample Company"). The person can change it later.
- `focus` (string): safety (default): the Safety Suite. home_services: the Home Services Suite (service calls, estimates).
- `trade` (string): The company's trade in a few words, e.g. "roofing" or "HVAC"; it sets the workspace's industry when it matches one Jobsite lists.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-jobsitecerts-safety-reference/api-mcp-public#diagnostics

## Score history

- 2026-11-21: 84
- 2026-11-20: 83
- 2026-11-19: 83
- 2026-11-18: 82
- 2026-11-17: 82
- 2026-11-16: 81
- 2026-11-15: 81
- 2026-11-14: 80
- 2026-11-13: 80
- 2026-11-12: 79
- 2026-11-11: 79
- 2026-11-10: 79
- 2026-11-09: 78
- 2026-11-08: 78
- 2026-11-07: 77
- 2026-11-06: 77
- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74

## Common questions

### What is the Jobsite Safety Reference (free) MCP server?

Jobsite Safety Reference (free) is an MCP server listed in the public MCP registry as com.jobsitecerts/safety-reference. Free, no-login construction safety tools: OSHA rule text, toolbox talks, 1904 recordability. This page covers its hosted endpoint (https://jobsitecerts.com/api/mcp/public).

### Is the Jobsite Safety Reference (free) MCP server safe to use?

Jobsite Safety Reference (free) scores 84 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 Jobsite Safety Reference (free) MCP server expose?

Jobsite Safety Reference (free) exposes 9 tools: lookup_jobsite_docs, search_articles, search_law_corpus, search_regulatory_news, osha_recordability_check, and 4 more. Their descriptions and schemas cost roughly 2,157 tokens of context every time the server is loaded.

### Does the Jobsite Safety Reference (free) MCP server require authentication?

No. We connected to Jobsite Safety Reference (free) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Jobsite Safety Reference (free) MCP server still maintained?

Jobsite Safety Reference (free) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Jobsite Safety Reference (free) MCP server?

VerifyMCP ran 13 checks on Jobsite Safety Reference (free), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://jobsitecerts.com/api/mcp/public
- Website: https://jobsitecerts.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-jobsitecerts-safety-reference/api-mcp-public.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-jobsitecerts-safety-reference/api-mcp-public/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-jobsitecerts-safety-reference/api-mcp-public.json
- HTML version of this page: https://verifymcp.io/servers/com-jobsitecerts-safety-reference/api-mcp-public
