Pretorin Compliance
PYPI · PRETORIN · SCANNED SEP 22
Access Pretorin controls, evidence, narratives, and local Plan-backed Campaigns from AI tools.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 6 of 71 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 39124 tokens (~133/item across 293 items; 270 tools + 23 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_evidence" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 272 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Pretorin Compliance MCP server?
Pretorin Compliance runs locally as a PyPI package, launched with uvx pretorin. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · pretorin
claude mcp add pretorin-ai-pretorin -- uvx pretorin
{
"mcpServers": {
"pretorin-ai-pretorin": {
"command": "uvx",
"args": [
"pretorin"
]
}
}
} {
"servers": {
"pretorin-ai-pretorin": {
"command": "uvx",
"args": [
"pretorin"
]
}
}
} codex mcp add pretorin-ai-pretorin -- uvx pretorin
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pretorin-ai-pretorin": {
"type": "local",
"command": [
"uvx",
"pretorin"
],
"enabled": true
}
}
} openclaw mcp add pretorin-ai-pretorin --command uvx --arg pretorin
mcp_servers:
pretorin-ai-pretorin:
command: "uvx"
args: ["pretorin"] {
"McpServers": {
"pretorin-ai-pretorin": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"pretorin"
]
}
}
} assistant mcp add pretorin-ai-pretorin -t stdio -c uvx -a pretorin
{
"mcpServers": {
"pretorin-ai-pretorin": {
"command": "uvx",
"args": [
"pretorin"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.29.17 → 0.29.18 functional
- 21 Sept 26 +15
- Stability: 0.90 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.29.14 → 0.29.17 functional
- Package version: 0.29.14 → 0.29.16 functional
- Package version: 0.29.14 → 0.29.15 functional
- 20 Sept 26 0
- Package version: 0.29.13 → 0.29.14 functional
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −2
- Stability: fail → 0.83 functional
- Package version: 0.29.10 → 0.29.13 functional
- Package version: 0.29.10 → 0.29.12 functional
- Package version: 0.29.10 → 0.29.11 functional
- 17 Sept 26 0
- Package version: 0.29.9 → 0.29.10 functional
- 16 Sept 26 +1
- Package version: 0.29.8 → 0.29.9 functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 86 to 89.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Analysed pypi/pretorin@0.29.18
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 71 packages
| Packages resolved | 71 |
|---|---|
| Stale | 4 |
| No linked repository | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_risk ~42
Get a single risk with eager-loaded artifact_links.
| Name | Type | Req | Description |
|---|---|---|---|
| risk_id | string | yes | Risk ID |
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
get_risk_assessment_report ~79
Read metadata for the current Risk Assessment Report (RAR) in the active system/framework scope. This is proof-only: it never creates or regenerates a report, and returns not found when no current RAR exists.
| Name | Type | Req | Description |
|---|---|---|---|
| framework_id | string | yes | Active framework ID |
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
get_risk_posture ~50
Read the system's aggregate risk-assessment posture: inherent and residual distributions, weighted residual score, overdue reviews, and top risks.
| Name | Type | Req | Description |
|---|---|---|---|
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
get_scope ~67
Get system scope/policy information including excluded controls and Q&A
| Name | Type | Req | Description |
|---|---|---|---|
| framework_id | string | yes | The framework ID (e.g., nist-800-53-r5, fedramp-moderate, soc2) |
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
get_scope_question_detail ~79
Use this BEFORE answering a specific scope question. Returns guidance, tips, example responses, and the current answer for ONE question. Pull only when ready to answer.
| Name | Type | Req | Description |
|---|---|---|---|
| framework_id | string | yes | Framework ID |
| question_id | string | yes | Question ID from the pending list |
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
get_scope_review_results ~88
Poll for scope generation or review results. Returns structured findings with severity, affected question IDs, and recommended fixes. Status will be 'queued', 'running', 'succeeded', or 'failed'. Poll every 2 seconds until done.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Job ID from trigger_scope_generation or trigger_scope_review |
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
get_source_manifest ~102
Get the resolved source manifest for a system and evaluate it against currently detected sources. Shows which external sources (git, cloud, HRIS, etc.) are required, recommended, or optional, and whether each is currently satisfied. If no local manifest is configured, falls through to the platform's in-scope recommended source kinds.
| Name | Type | Req | Description |
|---|---|---|---|
| framework_id | string | – | Framework ID (defaults to active context). |
| system_id | string | – | The system ID or name |
No output schema declared.
No examples provided.
get_stale_edges ~41
List controls with stale inheritance — the source narrative changed but the inherited control hasn't been updated.
| Name | Type | Req | Description |
|---|---|---|---|
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
get_stig ~39
Get single STIG benchmark detail by ID including title, version, and release info.
| Name | Type | Req | Description |
|---|---|---|---|
| stig_id | string | yes | The STIG benchmark ID |
No output schema declared.
No examples provided.
get_stig_applicability ~39
Get which STIGs apply to a system based on its profile.
| Name | Type | Req | Description |
|---|---|---|---|
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
get_stig_rule ~56
Get full detail for a single STIG rule including CCIs, check text, and fix text.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | The STIG rule ID |
| stig_id | string | yes | The STIG benchmark ID |
No output schema declared.
No examples provided.
get_system ~35
Get detailed information about a specific system including frameworks and security impact level
| Name | Type | Req | Description |
|---|---|---|---|
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
get_system_issues ~182
List issues across a whole system/framework rather than one control. Use this to find remediation work without walking every control. Each row carries control_implementation_id and issue_id for the treatment tools, plus lifecycle_status, gate_status, and is_blocking.
| Name | Type | Req | Description |
|---|---|---|---|
| control_id | string | – | Optional: The control ID. Use canonical IDs from list_controls. NIST/FedRAMP IDs are zero-padded (e.g., ac-02). CMMC IDs use dotted notation (e.g., AC.L2-3.1.1). |
| framework_id | string | – | Optional: Framework ID; defaults to active scope |
| limit | integer | – | – |
| offset | integer | – | – |
| source | string | – | Optional source filter |
| status | string | – | – |
| system_id | string | – | Optional: The system ID or name |
No output schema declared.
No examples provided.
get_test_manifest ~166
Get a system's applicable STIG test manifest. Full mode preserves scanner-ready check/fix definitions; use stig_id + rule_id for one exact definition, or mode=summary with limit/offset for a bounded discovery page. Responses include explicit pagination and truncation metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rules per page; defaults to 25 in summary mode and 1 for an exact rule |
| mode | string | – | Full scanner definition or compact rule metadata |
| offset | integer | – | Zero-based rule offset across the filtered manifest |
| rule_id | string | – | Optional exact DISA rule ID (or internal rule UUID) |
| stig_id | string | – | Optional STIG benchmark ID to scope the manifest |
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
get_vendor ~26
Get detailed information about a specific vendor.
| Name | Type | Req | Description |
|---|---|---|---|
| vendor_id | string | yes | Vendor ID |
No output schema declared.
No examples provided.
get_vendor_assessment ~43
Get a vendor assessment with its frozen template snapshot and captured answers.
| Name | Type | Req | Description |
|---|---|---|---|
| assessment_id | string | yes | Assessment ID |
| vendor_id | string | yes | Vendor ID |
No output schema declared.
No examples provided.
get_vendor_assessment_template ~34
Get a vendor assessment template with its sections and question specs.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | Assessment template ID |
No output schema declared.
No examples provided.
get_vendor_dashboard ~179
Get the organization-wide third-party-risk (TPRM) reporting dashboard: posture counts, by_tier / by_provider_type breakdowns, the 5x5 residual likelihood x impact heatmap (each cell carries a vendor count), and bounded document/contract expiry lists. horizon_days (1-365, default 90) sets the look-ahead window. Organization-wide: requires an org-scoped token with the vendor.pii or admin scope — system-scoped tokens are rejected. Note: per-cell heatmap vendor rosters are omitted here to stay within the response-size budget (heatmap_vendors_omitted is set to true); call list_vendors with a risk_tier filter to enumerate vendors in a tier.
| Name | Type | Req | Description |
|---|---|---|---|
| horizon_days | integer | – | Look-ahead window in days for the expiring-soon KPIs and lists. |
No output schema declared.
No examples provided.
get_vendor_history ~35
Get audit and evidence history for a vendor.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| vendor_id | string | yes | Vendor ID |
No output schema declared.
No examples provided.
get_workflow ~158
Return one workflow's manifest, markdown instructions, and referenced tool schemas. Use mode=compact to preserve the complete playbook and validation contracts without schema annotations, section=<heading id> for one complete bounded section, or include_tool_schemas=false for a minimal {id, body} response when the harness already registered the tools.
| Name | Type | Req | Description |
|---|---|---|---|
| include_tool_schemas | boolean | – | Bundle referenced tool definitions; false returns only workflow id and Markdown guidance for harnesses that already registered the tools |
| mode | string | – | Full annotated schemas or compact validation-equivalent schemas |
| section | string | – | Optional Markdown heading title/id from response_metadata.available_sections; returns that complete section including nested headings |
| workflow_id | string | yes | Workflow id to fetch |
No output schema declared.
No examples provided.
get_workflow_state ~113
Use this FIRST when starting a compliance workflow. Returns the lifecycle state for a system+framework: which stage needs work (scope, policies, controls, evidence), what the next action is, and progress counts. `stages.controls.controls_with_unmet_baseline_expectations` counts in-scope controls with an unmet baseline-tier evidence expectation. Lightweight — no content, just status.
| Name | Type | Req | Description |
|---|---|---|---|
| framework_id | string | yes | Framework ID for this workflow context |
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
import_stig_checklist ~196
Import a .ckl/.cklb file into a checklist's per-rule reviews (review axis). Full-fidelity complement to submit_test_results: ingests asset metadata + the four DISA statuses + finding details/comments + severity override, reconciled against the benchmark. Returns match/import counters + reconciles flag + capped rule-id buckets (the full per-rule outcomes are omitted for size; use the CLI for full detail). A non-reconciling import (rules dropped) returns an error result — never treat it as complete. Writes are refused outside the active context system.
| Name | Type | Req | Description |
|---|---|---|---|
| checklist_id | string | yes | Target checklist ID (must already exist) |
| file_path | string | yes | Local path to the .ckl (XML) or .cklb (JSON) file |
| format | string | – | File format, or 'auto' to detect |
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
import_stig_checklist_xccdf ~149
Import an XCCDF scan document (SCAP/OpenSCAP results) into the system test axis. Separate from import_stig_checklist (the .ckl/.cklb review axis). The test axis is system-scoped, so the response reports how many checklists on the system the scan affects. Use this to push a scanner recipe's XCCDF results so they derive DISA statuses across all checklists bound to the same benchmark.
| Name | Type | Req | Description |
|---|---|---|---|
| checklist_id | string | yes | A checklist ID on the target system |
| file_path | string | yes | Local path to the XCCDF results document |
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
import_vendor_assessment_template ~93
Import a SIG-Lite or CAIQ-Lite xlsx workbook as a vendor assessment template. By default dry_run is true and returns a preview; set dry_run false plus acknowledge_license_rights true to persist.
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledge_license_rights | boolean | – | – |
| dry_run | boolean | – | – |
| file_path | string | yes | Local xlsx workbook path |
| source_format | string | yes | – |
No output schema declared.
No examples provided.
infer_stigs ~35
AI-infer applicable STIGs from a system's profile.
| Name | Type | Req | Description |
|---|---|---|---|
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
inspect_campaign_evidence ~53
Read only the exact evidence artifact frozen into this evidence-ID review child. Control evidence-set children use assignment-scoped search_evidence instead.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | – |
| step_index | integer | yes | – |
No output schema declared.
No examples provided.
inspect_campaign_issue ~54
Read only the exact canonical Issue frozen into this issue-triage child. The server derives Issue and control-implementation identity from the trusted assignment.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | – |
| step_index | integer | yes | – |
No output schema declared.
No examples provided.
inspect_campaign_resource_receipts ~59
Inspect the bounded content-free typed-write receipt ledger and matching child-Plan artifacts for this assigned Campaign item. Use before retrying an intended write after an uncertain response.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | – |
| tool | string | – | – |
No output schema declared.
No examples provided.
launch_vendor_assessment ~44
Launch a vendor assessment from a template, freezing the template snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | Assessment template ID |
| vendor_id | string | yes | Vendor ID |
No output schema declared.
No examples provided.
link_evidence ~389
Link an existing evidence item to a control within exactly one active system/framework scope. Bind it to exactly one declared evidence expectation so the control's coverage map marks that expectation covered, or explicitly record why the artifact is intentionally unbound. Narrative citations ground claims but never satisfy expectation coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_unverified_sources | boolean | – | Allow writes when source attestation shows a mismatch. Defaults to false. |
| control_id | string | yes | The control ID. Use canonical IDs from list_controls. NIST/FedRAMP IDs are zero-padded (e.g., ac-02). CMMC IDs use dotted notation (e.g., AC.L2-3.1.1). |
| evidence_id | string | yes | The evidence item ID |
| expectation_item | string | – | Optional: Raw expectation text from the control context. The platform hashes it to the stable expectation key; use this or expectation_key. |
| expectation_key | string | – | Preferred: stable expectation key from get_control_context.expectation_coverage. Use this or expectation_item to bind the evidence to one declared expectation. |
| framework_id | string | – | Optional: Framework context for the link; defaults to active scope |
| plan_id | string | – | Optional: ID of the agent-authored plan this write is part of. When supplied, the platform write is tagged with the plan and the plan's local produced_artifacts[] audit chain gets an entry. |
| step_index | integer | – | Optional: zero-based index of the plan step that triggered this write. Only meaningful when plan_id is also supplied. |
| system_id | string | – | Optional: The system ID or name |
| unbound_reason | string | – | Use only when this artifact genuinely supports no declared expectation. The platform preserves the control link, clears its current expectation binding, and records the reason in the audit chain. Mut… |
No output schema declared.
No examples provided.
link_evidence_to_cci_implementation ~219
Link an existing evidence item to a per-system CCI implementation row. Use this when you already have the CCI implementation UUID (e.g., from get_cci_implementation or get_cci_status). This governed stig_scan write must match the active MCP system/framework context; agents cannot override that boundary.
| Name | Type | Req | Description |
|---|---|---|---|
| cci_implementation_id | string | yes | The per-system CCI implementation row UUID |
| evidence_id | string | yes | The evidence item ID |
| framework_id | string | – | Optional framework ID; defaults to and must match the active scope |
| plan_id | string | – | Optional: ID of the agent-authored plan this write is part of. When supplied, the platform write is tagged with the plan and the plan's local produced_artifacts[] audit chain gets an entry. |
| step_index | integer | – | Optional: zero-based index of the plan step that triggered this write. Only meaningful when plan_id is also supplied. |
| system_id | string | – | Optional: The system ID or name |
No output schema declared.
No examples provided.
link_evidence_to_objective_implementation ~239
Link an existing evidence item to a per-system assessment objective implementation row (CMMC / NIST 800-171A). Use this when you have the objective implementation UUID (e.g. from list_objectives or get_objective_implementation). The platform also mirrors the evidence into the parent control's library. This governed write must match the active MCP system/framework context; agents cannot override that boundary.
| Name | Type | Req | Description |
|---|---|---|---|
| assessment_objective_implementation_id | string | yes | The per-system assessment objective implementation row UUID |
| evidence_id | string | yes | The evidence item ID |
| framework_id | string | – | Optional framework ID; defaults to and must match the active scope |
| plan_id | string | – | Optional: ID of the agent-authored plan this write is part of. When supplied, the platform write is tagged with the plan and the plan's local produced_artifacts[] audit chain gets an entry. |
| step_index | integer | – | Optional: zero-based index of the plan step that triggered this write. Only meaningful when plan_id is also supplied. |
| system_id | string | – | Optional: The system ID or name |
No output schema declared.
No examples provided.
link_evidence_to_stig_rule_workflow ~226
Link an existing evidence item to a STIG rule workflow. Lazy-creates the workflow row if none exists yet for (system, stig_rule). Use this to attach remediation proof, mitigating-control documentation, or waiver-justification artifacts to a failing rule. This governed stig_scan write must match the active MCP system/framework context; agents cannot override that boundary.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_id | string | yes | The evidence item ID |
| framework_id | string | – | Optional framework ID; defaults to and must match the active scope |
| plan_id | string | – | Optional: ID of the agent-authored plan this write is part of. When supplied, the platform write is tagged with the plan and the plan's local produced_artifacts[] audit chain gets an entry. |
| step_index | integer | – | Optional: zero-based index of the plan step that triggered this write. Only meaningful when plan_id is also supplied. |
| stig_rule_id | string | yes | The STIG catalog rule UUID |
| system_id | string | – | Optional: The system ID or name |
No output schema declared.
No examples provided.
link_evidence_to_vendor ~60
Link existing evidence to a vendor. Set vendor_id to null to unlink.
| Name | Type | Req | Description |
|---|---|---|---|
| attestation_type | string | – | – |
| evidence_id | string | yes | Evidence item ID |
| vendor_id | string | – | Vendor ID (null to unlink) |
No output schema declared.
No examples provided.
link_risk_artifact ~195
Attach an artifact (control, evidence, finding, monitoring_event, or vendor) to a risk. Pass exactly one of control_id / evidence_id / finding_id / monitoring_event_id / vendor_id. Pass framework_id when linking a control.
| Name | Type | Req | Description |
|---|---|---|---|
| control_id | string | – | Optional: The control ID. Use canonical IDs from list_controls. NIST/FedRAMP IDs are zero-padded (e.g., ac-02). CMMC IDs use dotted notation (e.g., AC.L2-3.1.1). |
| evidence_id | string | – | – |
| finding_id | string | – | – |
| framework_id | string | – | Required when linking a control. |
| link_type | string | yes | – |
| monitoring_event_id | string | – | – |
| risk_id | string | yes | Risk ID |
| system_id | string | yes | The system ID or name |
| vendor_id | string | – | – |
No output schema declared.
No examples provided.
link_spec_snapshot ~259
Link an uploaded evidence item as the current snapshot for a system_spec kind, so it surfaces on the scope page. Use AFTER upload_evidence returns an evidence id. `kind` is one of the snapshot kinds (boundary_diagram, network_dfd, ppsm, interconnection) — call list_artifact_requirements for the authoritative set for this system. The asset inventory is NOT a snapshot kind; attest it with attest_spec_inventory instead. Requires an active workflow (call start_task first).
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_id | string | yes | ID of the uploaded evidence item to link as this kind's snapshot. |
| kind | string | yes | Snapshot kind to link the evidence to. One of boundary_diagram, network_dfd, ppsm, interconnection (per list_artifact_requirements). |
| plan_id | string | – | Optional: ID of the agent-authored plan this write is part of. When supplied, the platform write is tagged with the plan and the plan's local produced_artifacts[] audit chain gets an entry. |
| step_index | integer | – | Optional: zero-based index of the plan step that triggered this write. Only meaningful when plan_id is also supplied. |
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
list_artifact_requirements ~66
List the 5 auditor-required system_spec artifact kinds for a system (asset inventory + 4 snapshot kinds). Returns each kind's effective_required, optional/toggled-off state, attestation timestamp, and rationale.
| Name | Type | Req | Description |
|---|---|---|---|
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
list_assessments ~76
List formal assessments for one system, including status and immutable snapshot lifecycle fields used by the Auditor Portal.
| Name | Type | Req | Description |
|---|---|---|---|
| assessment_type | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| statuses | array | – | Repeatable status filters. |
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
list_campaigns ~86
List bounded local Plan-backed Campaign summaries for one trusted project root, ordered by immutable (created_at, Campaign Plan ID) and keyset-paginated. This local observation tool remains available during platform authentication or consent outages.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| project_dir | string | – | Optional trusted project directory; defaults to the MCP startup project. |
No output schema declared.
No examples provided.
list_ccis ~80
List CCI items with optional filters by NIST control ID or status.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results to return |
| nist_control_id | string | – | Filter by NIST control ID (e.g., AC-2) |
| offset | integer | – | Offset for pagination |
| status | string | – | Filter by CCI status |
No output schema declared.
No examples provided.
list_control_families ~55
List all control families for a specific framework with AI context (domain summary, risk context, implementation priority)
| Name | Type | Req | Description |
|---|---|---|---|
| framework_id | string | yes | The framework ID (e.g., nist-800-53-r5) |
No output schema declared.
No examples provided.
list_controls ~58
List controls for a framework, optionally filtered by control family
| Name | Type | Req | Description |
|---|---|---|---|
| family_id | string | – | Optional: Filter by control family ID |
| framework_id | string | yes | The framework ID (e.g., nist-800-53-r5) |
No output schema declared.
No examples provided.
list_frameworks ~37
List all available compliance frameworks (NIST 800-53, FedRAMP, SOC 2, ISO 27001, etc.)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_objectives ~255
List per-system assessment objective implementation rows (CMMC / NIST 800-171A). Filter by framework_id + control_id for one control's objectives, or by status. Each row carries effective status, status_source, narrative, evidence_ids, and has_status_conflict. control_id is normalized server-side (CMMC/800-171 IDs keep their native shape). Objectives are the assessable leaf a C3PAO adjudicates.
| Name | Type | Req | Description |
|---|---|---|---|
| control_id | string | – | Optional: The control ID. Use canonical IDs from list_controls. NIST/FedRAMP IDs are zero-padded (e.g., ac-02). CMMC IDs use dotted notation (e.g., AC.L2-3.1.1). |
| framework_id | string | – | Filter to one framework, e.g. 'cmmc_level_2' or 'nist-800-171' |
| limit | integer | – | Max results to return |
| offset | integer | – | Offset for pagination |
| only_conflicts | boolean | – | Only rows where human_status disagrees with scan_status |
| status | string | – | Filter by effective objective status |
| system_id | string | – | Optional: The system ID or name |
No output schema declared.
No examples provided.
list_org_policies ~18
List organization policies available for questionnaire work
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_oscal_artifacts ~147
List validated OSCAL export artifacts (SSP/SAR/SAP/POA&M/component-definition) for a system. Server-filtered to succeeded generation AND valid validation.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_type | string | – | Optional: filter by type (ssp, sap, sar, poam, component_definition, bundle) |
| assessment_id | string | – | Optional: filter by assessment ID |
| framework_id | string | – | Optional: filter by framework ID |
| limit | integer | – | Optional: page size (1-100, default 50) |
| offset | integer | – | Optional: pagination offset (default 0) |
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
list_recent_plans ~195
List recent plans (newest first), with optional filtering by state, workflow, and scope. Returns compact summaries — call get_plan for the full record once a plan is selected. Use this at session start to find an existing plan to resume instead of creating a duplicate.
| Name | Type | Req | Description |
|---|---|---|---|
| control_id | string | – | Optional: The control ID. Use canonical IDs from list_controls. NIST/FedRAMP IDs are zero-padded (e.g., ac-02). CMMC IDs use dotted notation (e.g., AC.L2-3.1.1). |
| framework_id | string | – | Framework id filter (e.g. fedramp-moderate). |
| limit | integer | – | Maximum number of plans to return. |
| state | string | – | Restrict results to plans in this state. |
| system_id | string | – | Optional: The system ID or name |
| workflow_id | string | – | – |
No output schema declared.
No examples provided.
list_recipes ~232
List loaded recipes with their summary metadata (id, name, tier, description, use_when, produces). Filter by tier, produces, and connected system sources. Use this to discover which recipes are available, then call get_recipe(id) to read the full body.
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | Return only the scope's active recipe set (the curated subset). Fails closed: an unprovisioned scope or unreadable artifact returns an empty list (use get_active_recipes to provision), and a missing… |
| include_deprecated | boolean | – | Include deprecated compatibility recipes. They are hidden from normal discovery and provisioning recommendations. Defaults to false. |
| include_unavailable | boolean | – | When system_id is supplied, include recipes whose required sources are missing. Defaults to false. |
| produces | string | – | Filter by what the recipe produces |
| system_id | string | – | Optional: The system ID or name |
| tier | string | – | Filter to one tier |
No output schema declared.
No examples provided.
list_risk_attestations ~47
List signed risk-attestation envelopes newest first for audit verification.
| Name | Type | Req | Description |
|---|---|---|---|
| risk_id | string | yes | Risk ID |
| system_id | string | yes | The system ID or name |
No output schema declared.
No examples provided.
list_risk_library ~35
List org-level risk library templates available to the org. Optional category filter.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter |
No output schema declared.
No examples provided.
What is the Pretorin Compliance MCP server?
Pretorin Compliance is an MCP server listed in the public MCP registry as io.github.pretorin-ai/pretorin. Access Pretorin controls, evidence, narratives, and local Plan-backed Campaigns from AI tools. This page covers its PyPI package (pretorin).
Is the Pretorin Compliance MCP server safe to use?
Pretorin Compliance scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Pretorin Compliance MCP server expose?
Pretorin Compliance exposes 270 tools: list_frameworks, get_framework, list_control_families, list_controls, get_control, and 265 more. Their descriptions and schemas cost roughly 37,576 tokens of context every time the server is loaded.
Is the Pretorin Compliance MCP server still maintained?
Pretorin Compliance is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Pretorin Compliance MCP server under?
Pretorin Compliance declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.