MCP Resources
The MCP server exposes read-only resources across three URI schemes: analysis://, status://, and workflow://.
Available Resources
| Resource URI | Description |
|---|---|
analysis://schema | JSON schema for compliance artifacts |
analysis://guide/{framework_id} | Analysis guide for a specific framework |
analysis://control/{framework_id}/{control_id} | Analysis guidance for a specific control within one framework scope |
status://cli | Current CLI version, update availability, and upgrade guidance (command, approval/restart flags, and an explanatory note) |
workflow://recipe/{recipe_id} | Step-by-step workflow recipe for common compliance tasks |
Usage
Access these resources via ReadMcpResourceTool with server: "pretorin" in your MCP client.
Analysis Schema
analysis://schema
Returns the JSON schema for structured compliance artifacts. Use this when generating artifact JSON to ensure correct structure. See Artifact Schema for documentation.
Framework Analysis Guide
analysis://guide/{framework_id}
Available framework guides:
analysis://guide/fedramp-moderateanalysis://guide/nist-800-53-r5analysis://guide/nist-800-171-r3
Returns framework-specific analysis guidance including purpose, target audience, scope, and assessment methodology. Framework IDs match loosely, so a close variant of a listed ID resolves to the same guide; an unrelated ID raises an error.
Control Analysis Guidance
analysis://control/{framework_id}/{control_id}
Example: analysis://control/fedramp-moderate/ac-02
Returns control-specific analysis guidance including search patterns, evidence examples, and assessment criteria for one framework scope. Guidance is currently authored for five controls — ac-02, au-02, cm-02, ia-02, and sc-07 — listed once per framework guide above (15 resources). Control IDs are normalized, so ac-2 and AC-02 both resolve.
CLI Status
status://cli
Returns the current CLI version, latest available version, whether an update is available, passive notification status, and check state (verified/unverified), followed by the upgrade contract for this install: the upgrade command (or, where no self-update exists, an openable release URL), whether it requires human approval, whether a restart is required, and a note explaining what it changes.
Approval and restart are yes on every route where the command mutates the local install — Python package, Homebrew, and self-updating standalone binary alike. Hosts should surface the command to the operator rather than run it; an already-running MCP server keeps serving the previous version until it restarts. They are no only where no self-update path exists, because the value is then a download page and nothing changes until a person acts on it.
Workflow Recipes
workflow://recipe/{recipe_id}
Returns a step-by-step workflow recipe for common compliance tasks. Available recipes are listed dynamically via the MCP list_resources method; today that set is complete-one-policy, fix-control-family, and full-compliance-pass.
The former external Campaign recipes — workflow://recipe/external-campaign-controls
and workflow://recipe/external-campaign-questionnaires — are no longer
advertised by list_resources because they describe the deprecated
checkpoint/proposal/apply architecture. Those two URIs remain directly readable
only during the documented 0.29.x compatibility window, and their bodies open
with an explicit deprecation warning. New Campaign work starts
with CLI pretorin campaign start <type> or MCP check_campaign_runtime, then
preview_campaign only when ready, followed by explicit-digest
start_campaign, and re-enters through the same Campaign Plan
ID on either surface.
These are host-readable resources, distinct from the executable recipes behind list_recipes / start_recipe and the workflow bodies behind get_workflow.