Magist

Run Magist’s deterministic compliance engine over a product description (features, target markets, audience age bands, optional business model) and return the regulations and Controls that may be triggered, a complexity tier with a numeric score, a blocker count, and a per-audience cohort breakdown. The call also creates or refreshes an idempotent public report URL for the receipt, retained for up to 90 days. Deterministic and reproducible: the same inputs always produce the same output, with no LLM in the path. Returns which obligations may apply for research purposes; it is not a determination that they do apply, and does not replace counsel. Consult a licensed attorney before relying on the result.

Given a regulation id, return the compliance Controls that may satisfy it, each with a priority signal (blocker / required / evaluate / best-practice) and a short summary of the work involved. Returns research information about typical control mappings, not a determination that a given product needs them. Consult counsel for scoping.

Search Magist’s open counsel directory for law firms by jurisdiction and practice area. Returns an editorial / firm-claimed directory to help a user identify licensed attorneys to consult. Inclusion is not endorsement; verify bar status and conflicts independently before engaging.

Given a Control id, list third-party vendors and in-house approaches that may implement it, with effort/cost signals and a source-disclosure (editorial research vs vendor submission). Magist does not accept payment from vendors and does not rank or endorse them. Returns a neutral catalog for research; evaluate fit independently.

Return recent regulatory enforcement actions from Magist’s catalog, optionally filtered by regulation id and a since-date. Each action includes the penalty, authority, a primary-source link, and (where authored) a practitionerAnalysis: a hedged, third-person editorial note on what the action illustrates, informational context that never addresses a specific product. penaltyAmount is null when no monetary amount is recorded (pending, confidential, annulled, or non-monetary outcomes; the amount string carries the honest description). Returns historical facts about what regulators have done: informational context, not a prediction about a specific product.

Return Magist’s closed catalogs of valid product feature ids and target market ids, each with a short human-readable label -- the exact identifiers compute_requirements accepts as "features" and "markets". Use this to validate ids before calling compute_requirements; ids outside these catalogs are rejected with an actionable error. Deterministic and reproducible; this is reference data, not itself a regulatory determination.

Look up one regulation by its Magist id and return structured research information: title, citation, jurisdiction, status, review dates, a plain-language summary, and the Controls that may satisfy it. Returns facts about what a regulation says, not a determination of how it applies to a specific product. Consult counsel for situation-specific questions.

Search Magist’s regulation corpus by keyword with optional filters (jurisdiction, domain, status, content-review status, coverage depth). Returns a paginated list of matching regulations with permanent citation URLs. Deterministic: the same query and filters return the same results every time. Returns research information for discovery, not a determination of which regulations apply to a specific product.

Verify a Magist grounding-proof token: the "groundingProof" field on a regulation or control record from the REST API (GET /api/v1/regulations/{id} or /api/v1/controls/{id}) when the server has signing enabled. MCP tool responses do not carry these tokens. Proves the citation was genuinely served by Magist's server for that exact atom at that exact corpus version; it does NOT verify legal correctness or that any obligation applies to a product. Returns valid:false with a reason when the token is missing, malformed, unsigned, or fails signature verification; this is expected when the record never carried a token (signing is an opt-in server setting).