Developers and Agents
Childcare API and MCP for licensing, inspections, trust, and source-linked facility records.
CribScore is the installable layer for teams that need childcare licensing and inspection data without scraping fifty state portals. Use npm, OpenAPI, remote MCP, and query-mapped docs to integrate one canonical surface instead of rebuilding provenance and parser logic state by state.
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
Childcare API for Developers
Use the CribScore childcare API for facility search, facility detail, trust metrics, prices, and decision workflows.
API
Childcare Licensing API
Read childcare licensing status, source-linked provider records, trust tiering, and state-by-state coverage from CribScore.
API
Daycare Inspection API
Use CribScore for daycare inspection history, violation context, score history, evidence, and predictive risk signals.
MCP
Remote MCP for Childcare Agents
Connect the hosted CribScore MCP endpoint to agent clients with one remote streamable HTTP config.
MCP
Local MCP Install with npm
Install the CribScore MCP package from npm and run it locally with `npx` or as a pinned dependency.
API
OpenAPI Reference for CribScore
Use the CribScore OpenAPI document for typed SDK generation, request inspection, API collections, and contract verification.
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.