Skip to content

Jobsite Safety Reference (free) MCP server

com.jobsitecerts/safety-referencejobsitecerts.comstreamable-httpv1.0.0Scanned

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

9 tools: 4 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 4 write, 5 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Jobsite Safety Reference (free) MCP server can do

The Jobsite Safety Reference (free) MCP server is published by jobsitecerts.com, a domain the MCP Registry verified. It has 9 tools. It can create or change data (4 tools: osha_recordability_check, training_required_for, verify_certificate and start_jobsite_workspace), but cannot delete data. 5 tools only read.

1 tool reads private data (lookup_jobsite_docs); 2 tools bring in text other people can write (search_regulatory_news and get_toolbox_talk).

The fixed checks matched 2 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 4Claude Code: ask
  • osha_recordability_checkRuns 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 r…1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "osha_recordability_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: OSHA recordability check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • start_jobsite_workspaceCreate 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 se…No findings

    Why it is in this group

    • The name "start_jobsite_workspace" says "start": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Start a sample Jobsite workspace
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • training_required_forWhat training Jobsite's requirements inventory assigns a construction trade in a US state, optionally for roles the worker also holds (supervisor, competent person, forklift operat…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Training a trade needs, from Jobsite's inventory
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • verify_certificateCheck a certificate, or a whole certificate wallet, that a worker shared from Jobsite as a link (https://jobsitecerts.com/w/…).1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...m/w/…). Returns the holder's name, each credential with its issuer, issue and expiry dates..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check a worker's shared certificate
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 5Show 5 read-only tools
  • get_toolbox_talkA 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…Reads text others writeNo findings

    Why it is in this group

    • The name "get_toolbox_talk" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "discussion": it reads comments, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a toolbox talk
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • lookup_jobsite_docsLook up how Jobsite (this product) works — features, UI navigation, terminology, account / billing, worker-side experience, what counts as a 'group' vs 'crew', etc.Reads private dataNo findings

    Why it is in this group

    • The name "lookup_jobsite_docs" says "lookup": a word for reading.

    What it can reach

    • private-dataThe name "lookup_jobsite_docs" says "lookup" and "doc": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search the Jobsite product guide
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_articlesSearch Jobsite's published marketing content — blog articles, head-to-head COMPETITOR COMPARISON pages (e.g.No findings

    Why it is in this group

    • The name "search_articles" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search Jobsite articles
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_law_corpusSearch 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, …No findings

    Why it is in this group

    • The name "search_law_corpus" says "search": a word for reading.
    Description, as the server wrote it
    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'.

    Annotations the server declares

    • title: Search the regulation corpus
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_regulatory_newsSearch recent regulatory / safety news from the Federal Register (filtered to OSHA) and the OSHA news RSS feed.Reads text others writeNo findings

    Why it is in this group

    • The name "search_regulatory_news" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "search" and "rss": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Search regulatory news
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:21 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://jobsitecerts.com/api/mcp/public: tools/list returned 9 tools to an anonymous client, including osha_recordability_check (write), training_required_for (write), verify_certificate (write), start_jobsite_workspace (write)

    What this check looks for

Posture changes

  1. Nov 8, 2026
    • Tools that change things, listed without credentials: 2 to 4
    • RFC 9728 protected resource metadata: https://jobsitecerts.com/.well-known/oauth-protected-resource to none
    • Authorization servers: https://jobsitecerts.com to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed

Findings

Matches of fixed checks, with the text they matched.

1 warn1 info
  • The server marks "osha_recordability_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...m/w/…). Returns the holder's name, each credential with its issuer, issue and expiry dates..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools3 added, 4 changed.+3 added~4 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 4; RFC 9728 protected resource metadata: https://jobsitecerts.com/.well-known/oauth-protected-resource -> none; Authorization servers: https://jobsitecerts.c…View diff
    • Tools that change things, listed without credentials: 2 to 4
    • RFC 9728 protected resource metadata: https://jobsitecerts.com/.well-known/oauth-protected-resource to none
    • Authorization servers: https://jobsitecerts.com to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__safety-reference__lookup_jobsite_docs",
      "mcp__safety-reference__search_articles",
      "mcp__safety-reference__search_law_corpus",
      "mcp__safety-reference__search_regulatory_news",
      "mcp__safety-reference__get_toolbox_talk"
    ],
    "ask": [
      "mcp__safety-reference__osha_recordability_check",
      "mcp__safety-reference__training_required_for",
      "mcp__safety-reference__verify_certificate",
      "mcp__safety-reference__start_jobsite_workspace"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as safety-reference. Review it before you use it.

Capability tags behind 3 rules
  • mcp__safety-reference__lookup_jobsite_docs private-data
  • mcp__safety-reference__search_regulatory_news untrusted-input
  • mcp__safety-reference__get_toolbox_talk untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.jobsitecerts/safety-reference/verify?hash=f5cd12eb34fc78c57fbd1ee5ae67be07fa84614db4c9e172391cdcf889c71057" | jq -e '.changed == false'

Pinned hash f5cd12eb34fc, from Nov 12, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.jobsitecerts/safety-reference/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.jobsitecerts/safety-reference
[![Anlyon Radar](https://radar.anlyon.com/badge/com.jobsitecerts/safety-reference.svg)](https://radar.anlyon.com/servers/com.jobsitecerts/safety-reference)

Source: MCP Registry. Synced Oct 31, 2026, 00:18 UTC.

Jobsite Safety Reference (free) MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 9 tools, 4 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Jobsite Safety Reference (free) MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Jobsite Safety Reference (free) MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Jobsite Safety Reference (free) MCP server have?

9 tools: 4 write, 5 read. osha_recordability_check, training_required_for, verify_certificate, start_jobsite_workspace, lookup_jobsite_docs, search_articles, search_law_corpus, search_regulatory_news and 1 more.

Does the Jobsite Safety Reference (free) MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Jobsite Safety Reference (free) MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Jobsite Safety Reference (free) MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.