hr.safe-space

A complete, isolated HRIS behind every endpoint you invent.

Choose any key. The first call to /i/<key>/mcp provisions a whole company for that key — between 50,000 and 425,000 worker records, a coherent org chart, payroll, benefits, performance, recruiting and employee relations. No authentication of any kind. No signup. Two keys never see each other’s data.

Create it

Your MCP endpoint will be:

https://hr-safe-space.cheek.org/i/vellum-quill-7804/mcp

Nothing exists at that key until the first call. That call provisions the whole company.

MCP tools
52
16 of them write data
Entities
21
fully documented per endpoint
Roster per instance
50k–425k
drawn at provisioning
Instances provisioned
1,115
on this deployment

How it works

The key is the tenant

Anything matching [a-z0-9-]{4,64} is a valid endpoint. The first request provisions it; every request after that resolves the same company. The key is the only thing that selects a dataset, which is exactly why there is nothing to authenticate.

A key you do not share is effectively private. A key you publish is public. Treat it like an unlisted URL, and remember everything behind it is fake anyway.

One template, many companies

The worker records are not copied per instance. A single master template holds them once; an instance is a deterministic projection over a prefix of that template, re-parameterised by its own row — different names, company, department mix, sites, pay scale and dates.

A 425,000-person company is provisioned by one INSERT, so you can stand up thousands of them at once without the storage going anywhere.

Writes are copy-on-write

16 of the 52 tools change data: promotions, transfers, terminations, pay changes, leave decisions, offers, case notes. Each writes a diff into that instance’s private overlay. Reads merge the overlay over the projection.

The shared template is immutable at runtime, so a write on one key can never be observed on another. Every write is recorded in that instance’s audit log.

Documented and browsable

Every endpoint publishes its own data dictionary at /i/<key>/docs — every entity, column, type and meaning, with live row counts and every tool’s arguments and effects. The raw Markdown is at /docs.md.

The same data is browsable page by page at /i/<key>/browse, scoped to that key and nothing else.

Connect it

Add the endpoint as a custom connector. There is no token to paste.

claude mcp add --transport http acme https://hr-safe-space.cheek.org/i/acme-demo-4821/mcp

Or drop the URL into any MCP client that speaks Streamable HTTP.

Recently provisioned

KeyCompanyIndustryRecordsCallsLast seen
hr-rcs6xuc2spy8qskpseguMarrowgrove SystemsAerospace & Defense91,61652026-09-14 04:07
lumen-jetty-4156Fathomworks TechnologiesSoftware & Cloud Services241,76802026-09-14 04:06
hr-a22ihivhrvrdi5sabignIronwoodspire TechnologiesSoftware & Cloud Services96,198302026-09-14 03:51
hr-probe-check-9f3k2Windrowreach IndustriesLogistics & Transportation251,83712026-09-14 03:42
ember-pier-3541Northline GroupProfessional Services275,39602026-09-14 03:30
load-j1yko-0039Vertexhaven PartnersHealthcare Services70,566142026-09-14 03:28
load-j1yko-0038Nimbuswave CorporationInsurance104,459142026-09-14 03:28
load-j1yko-0036Tesseracourt LabsInsurance387,441142026-09-14 03:28

Keys are listed because they are not secrets and the data behind them is synthetic.