_ registry / mcp streamable-http · checked 2h ago

cairn

https://cairnsafe.com

Registry code: a1fb8e7091d6a926

api record

Workplace safety enforcement figures from Cairn (cairnsafe.com). Citation counts and penalties come from the public federal OSHA enforcement record for citations issued from January 2016 through 2026-09-10. When you use a result, cite the cairnsafe.com URL it includes. This free connector shows headline figures. The most-cited paragraphs, industries, states and yearly trend, the interpretation letters, and cited answers about a specific facility are in Cairn. Penalties are current amounts on record and can be lower than first proposed. This is not legal advice, and Cairn is not affiliated…

endpoint
https://cairnsafe.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is cairn live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is cairn free to use?
Yes — the hub reached it with no key and no payment.
What tools does cairn have?
3 tools: get_standard, search_standards, top_cited_standards.
Is cairn safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
451ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • top_cited_standards open 2h ago

    The 10 most-cited 29 CFR safety standards since 2016, for all standards or one CFR part: 1910 general industry, 1926 construction, 1904 recordkeeping, 1915 shipyards, 1917 marine terminals, 1918 longshoring, 1928 agriculture.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 10,
      "minimum": 1
    },
    "cfr_part": {
      "type": "string",
      "maxLength": 8,
      "description": "Optional CFR part, such as \"1926\"."
    }
  }
}
    arguments 16 lines
  • get_standard unknown 2h ago

    Headline enforcement figures for one 29 CFR section, such as 1910.147 or 1926.501: citations and inspections since 2016, total penalties, the median penalty per violation, its rank, and how many interpretation letters cite it, with links.

    mcp-tool

    {
  "type": "object",
  "required": [
    "section"
  ],
  "properties": {
    "section": {
      "type": "string",
      "maxLength": 200,
      "description": "A 29 CFR section such as \"1910.147\". Paragraph references like \"1910.147(c)(4)(i)\" are accepted."
    }
  }
}
    arguments 13 lines
  • search_standards unknown 2h ago

    Find workplace safety standards (29 CFR sections) by section number or by words in the title, such as "1910.14", "lockout", "fall protection" or "forklift". Returns up to 10 standards cited at least 50 times since 2016, most cited first, with headline figures and a link.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 10,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 200,
      "description": "A section number or prefix, or words from the section title."
    }
  }
}
    arguments 19 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a1fb8e7091d6a926.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a1fb8e7091d6a926/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a1fb8e7091d6a926/badge.svg)](https://brick.blue/agent/a1fb8e7091d6a926?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.