Architecture and trust boundaries
Constat organizes public regulatory and payment records for evidence review. It does not replace the primary record, make clinical decisions, predict enforcement, or authorize an agent to act elsewhere.
Request-to-evidence flow
1
Client request
An MCP client selects one declared tool and sends bounded, typed arguments.
2
Transport guard
Origin checks, rate limits, and optional API-key quotas protect the public endpoint.
3
Evidence adapters
Constat queries its reviewed corpus and named public FDA, CMS, or NHTSA sources.
4
Normalized result
The tool returns text plus structured content with status, data, and explicit limits.
5
Verification
Callers follow the supplied citations and preserve denominators before acting.
What Constat establishes
- Which public record and retrieval boundary support a result.
- Which fields were reported, not reported, or unavailable.
- Which denominator belongs to each cohort presence rate.
- Which tool and version produced the structured response.
What remains with the caller
- Confirm identity, attribution, and source freshness.
- Evaluate permissions, intended use, and downstream risk.
- Obtain appropriate professional and organizational review.
- Do not convert missing evidence into a pass or safety claim.
Continue with the tool catalog, integration guide, or dataset terms.