Developers and Agents
Childcare API and MCP for licensing, inspections, trust, and source-linked facility records.
One canonical surface instead of fifty state portals. Read the guides, try the API, install the MCP.
Remote MCP
Connect agents to the hosted MCP endpoint when you want a zero-infra evaluation path.
Open remote MCP guideOpenAPI
Generate clients, collections, and typed integrations from the canonical API contract.
Open OpenAPI guideProof surfaces
Use `/states`, `/trust`, and facility pages as the citation corpus behind the install story.
Open trust consoleQuery-mapped guides
Pages built for the terms developers actually search.
API
API Reference
The complete REST reference for CribScore: facility search, facility detail, trust, decision memo, webhooks, and evidence — typed, source-linked, and OpenAPI-backed.
API
Facilities API
Search, detail, compare, risk forecast, and evidence endpoints for licensed childcare facilities — source-linked, trust-tagged, and ready for underwriting + agent workflows.
API
Facilities API
Search, detail, compare, risk forecast, and evidence endpoints for licensed childcare facilities — source-linked, trust-tagged, and ready for underwriting + agent workflows.
MCP
Remote MCP (hosted)
Connect your agent client to the hosted CribScore MCP endpoint with one streamable-HTTP config. Zero install, scales with you, bearer-auth.
MCP
Local MCP (npm)
Install the CribScore MCP package from npm and run it locally over stdio. Use this when you want version pinning, offline operation, or local API testing.
API
API Reference
The complete REST reference for CribScore: facility search, facility detail, trust, decision memo, webhooks, and evidence — typed, source-linked, and OpenAPI-backed.
What you can build on top of CribScore
Agent workflows
Search providers, compare facilities, read trust tiers, and cite evidence without brittle browser-driving.
Internal product infrastructure
Use one canonical API for trust-aware recommendations, monitoring, underwriting review, and provider operations.
Answer-engine citations
Point retrieval and answer layers at the docs, state, trust, and facility proof surfaces instead of raw portal HTML.
Proof before claims
The install story only works if the public proof surfaces stay honest. State pages, trust pages, facility detail, and monthly reports are the public record behind the package and docs.
Distribution bundle
npm
Published package for local MCP installation.
Registry metadata
Checked-in MCP Registry metadata for registry and host verification.
OpenAPI
Typed API contract for generated clients and API tooling.
Postman source
Repo-backed collection source for workspace publishing.
Reports and changelog
Recurring proof content tied to distribution and surface changes.