Jobsite Safety Reference (free)
REMOTE · JOBSITECERTS.COM
Free, no-login construction safety tools: OSHA rule text, toolbox talks, 1904 recordability.
Available components
Last scanned (20 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +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.
- 19 Nov 26 +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.
- 17 Nov 26 +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.
- 15 Nov 26 +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.
- 13 Nov 26 +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.
- 10 Nov 26 +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.
- 8 Nov 26 +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.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://jobsitecerts.com/api/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jobsitecerts.com | CN=YR2,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | RSA 2048 | SHA256-RSA | 6ba3cd0470d45b22477580f5f06924edacc |
| SANs: jobsitecerts.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jobsitecerts.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| jobsitecerts.com. | No DS | 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 | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://challenges.cloudflare.com https://api.mapbox.com https://va.vercel-scripts.com https://www.youtube.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' https://api.mapbox.com; font-src 'self' data:; img-src 'self' data: blob: https:; media-src 'self' data: blob: https://*.supabase.co; worker-src 'self' blob:; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://challenges.cloudflare.com https://api.mapbox.com https://events.mapbox.com https://api.openai.com https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com; frame-src 'self' https://challenges.cloudflare.com https://www.youtube.com https://www.youtube-nocookie.com; frame-ancestors 'self'; base-uri 'self'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), microphone=(self), geolocation=(self), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jobsitecerts.com/api/mcp/public | Verified | 200 | |
| http (plaintext) | http://jobsitecerts.com/api/mcp/public | HTTPS enforced | 308 | https://jobsitecerts.com/api/mcp/public |
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_toolbox_talk Get a toolbox talk ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
No output schema declared.
No examples provided.
lookup_jobsite_docs Search the Jobsite product guide ~203
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max sections to return. Defaults to 4, cap 8. |
| query | string | yes | Natural-language query, e.g. 'how do I add a worker', 'difference between groups and crews', 'where do I see expiring certs'. |
No output schema declared.
No examples provided.
osha_recordability_check OSHA recordability check ~340
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
search_articles Search Jobsite articles ~222
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max articles to return. Defaults to 4, cap 6. |
| query | string | yes | Natural-language query, e.g. 'how is Jobsite better than Procore', 'Jobsite vs SiteDocs', 'confined space article'. |
No output schema declared.
No examples provided.
search_law_corpus Search the regulation corpus ~327
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Plain-words regulatory question or a citation number — 'fall protection trigger height', '1926.501', 'silica exposure control plan'. |
No output schema declared.
No examples provided.
search_regulatory_news Search regulatory news ~197
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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return per source. Defaults to 6, cap 12. |
| query | string | yes | Natural-language search terms. Best with topical keywords plus standard numbers when known. |
No output schema declared.
No examples provided.
start_jobsite_workspace Start a sample Jobsite workspace ~240
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
training_required_for Training a trade needs, from Jobsite's inventory ~309
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
verify_certificate Check a worker's shared certificate ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| link | string | yes | The share link the worker gave you, or the 43-character code at its end. |
No output schema declared.
No examples provided.
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.
remote · jobsitecerts.com
claude mcp add --transport http com-jobsitecerts-safety-reference 'https://jobsitecerts.com/api/mcp/public'
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.