MCP Server for OSCAL
PYPI · MCP-SERVER-FOR-OSCAL
AI agent tools for Open Security Controls Assessment Language (OSCAL)
Available components
Last scanned (11 hours ago)
Scores higher than 97% of PyPI servers
Category Security
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 53 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to dfkunstler/mcp-server-for-oscal). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5582 tokens (~121/item across 46 items; 46 tools + 0 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 Management94
- Stability check failed: the tool surface changed between 0.5.2 and 0.7.1: 0 tool removals, 5 breaking changes, 6 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (9% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 46 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 47 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 +3
- CVE-2026-59951 no longer affects this package ▲ security
- CVE-2026-116685 no longer affects this package ▲ security
- CVE-2026-116684 no longer affects this package ▲ security
- CVE-2026-116686 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 94.
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 28 Oct 26 0
- CVE-2026-116685 affects this package: high ▼ security
- CVE-2026-116684 affects this package: high ▼ security
- CVE-2026-116686 affects this package: high ▼ security
- 27 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.7.0 → 0.7.1 functional
- 25 Oct 26 +16
- Malware scan: unverified → pass ▲ security
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 5 Nov 2026 · Analysed pypi/mcp-server-for-oscal@0.7.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | dfkunstler/mcp-server-for-oscal |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/dfkunstler/mcp-server-for-oscal/.github/workflows/release.yml@refs/tags/v0.7.1 |
| Rekor log index | 3499068261 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:d1a0389ae7bde983c5b47cafb9bc464c56ba2a4884b3373d4b9891437876b074 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 53 packages
| Packages resolved | 53 |
|---|---|
| No linked repository | 1 |
| 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 →
about ~34
Return server metadata: package version, keywords, bundled OSCAL version, and the number of documents loaded from OSCAL_DOCUMENTS_DIR.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_references_to ~226
Find the fields, flags, props, and links that OSCAL Metaschema `index-has-key` constraints require to reference an assembly by key (UUID or ID), with the matching `index`, source file and line for both, and `cross-document`. Use when you need what must point to a component, party, location, or resource, including prop and link references a search for UUID fields misses. Results are paged within a response budget.
| Name | Type | Req | Description |
|---|---|---|---|
| assembly | string | yes | Instance or definition name of the referenced assembly, matched exactly, e.g. "component", "party", "resource", or "system-component". |
| limit | integer | – | Maximum items per page, 1-100. A page may hold fewer to fit the response budget. |
| model | – | – | OSCAL model name from list_oscal_models, e.g. "system-security-plan", to keep only references declared in that model. Indexes always resolve across all models. Omit for all models. |
| offset | integer | – | Zero-based index of the first item. |
No output schema declared.
No examples provided.
get_allowed_values ~208
Return the values OSCAL Metaschema `allowed-values` constraints permit at a target, with `allow-other`, `namespace` and `conditions` for predicates, and source file and line. Use when the JSON schema does not list the values; use get_constraints for other constraint types. Results are paged within a response budget, and an empty page lists `suggested-targets`.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. A page may hold fewer to fit the response budget. |
| model | string | yes | OSCAL model name from list_oscal_models, e.g. "catalog". |
| offset | integer | – | Zero-based index of the first item. |
| target | string | yes | Target_Selector: a Metaschema definition name, optionally followed by "/" (child) or "//" (descendant) and instance names, e.g. "defined-component/prop/@name". No predicates, unions, or whitespace. |
No output schema declared.
No examples provided.
get_capability ~55
Get one Capability by UUID as OSCAL JSON, or null when no Capability has that UUID. Use when working with Component Definitions that contain capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | UUID of the Capability, from list_capabilities. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_child_element ~104
Get one child element by UUID or token ID, with its OSCAL JSON in `raw_json`. If the result is an `ambiguous_element_id` error, retry with parent_doc_uuid.
| Name | Type | Req | Description |
|---|---|---|---|
| element_id | string | yes | UUID or token ID (e.g. ac-1) of the child element. Token IDs are unique only within one document. |
| parent_doc_uuid | – | – | UUID of one parent document to scope results to. Omit for all documents. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_constraints ~245
List the OSCAL Metaschema constraints at a target (`allowed-values`, `matches`, `index`, `index-has-key`, `is-unique`, `has-cardinality`, `expect`) with type-specific details and source file and line; a bare definition name returns every constraint declared on it and its local definitions. Use when you need rules the JSON schema does not express; use get_allowed_values for the values themselves. Results are paged within a response budget.
| Name | Type | Req | Description |
|---|---|---|---|
| constraint_types | – | – | Constraint types to keep. Omit or pass an empty list for all types. |
| limit | integer | – | Maximum items per page, 1-100. A page may hold fewer to fit the response budget. |
| model | string | yes | OSCAL model name from list_oscal_models, e.g. "catalog". |
| offset | integer | – | Zero-based index of the first item. |
| target | string | yes | Target_Selector: a Metaschema definition name, optionally followed by "/" (child) or "//" (descendant) and instance names, e.g. "defined-component/prop/@name". No predicates, unions, or whitespace. |
No output schema declared.
No examples provided.
get_definition ~200
Return every OSCAL Metaschema definition with a given name, with formal name, description, remarks, flags, model children, constraint summaries, and source file and line. Use when you need documentation or structure that the generated JSON and XML schemas shorten or drop. Results are paged within a response budget, and long remarks are marked `truncated`.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | – | – | Definition kind to keep. Omit for all kinds. |
| limit | integer | – | Maximum items per page, 1-100. A page may hold fewer to fit the response budget. |
| model | – | – | OSCAL model name from list_oscal_models, e.g. "catalog". Omit for all models. |
| name | string | yes | Metaschema definition name, 1-200 characters, matched exactly (case-sensitive), e.g. "defined-component" or "uuid". |
| offset | integer | – | Zero-based index of the first item. |
No output schema declared.
No examples provided.
get_metaschema_source ~166
Read a line range of a bundled OSCAL Metaschema source file verbatim, or list the files with line counts when `file` is omitted. Use when checking a `source-file` and `line` from get_definition, get_allowed_values, get_constraints, or find_references_to. A response may hold fewer lines to fit the response budget; continue from `end-line` + 1 while `has-more` is true.
| Name | Type | Req | Description |
|---|---|---|---|
| file | – | – | Bundle-relative path exactly as listed, e.g. "oscal_component_metaschema.xml". Omit to list the files. |
| line_count | integer | – | Maximum lines to return, 1-500. |
| start_line | integer | – | 1-based first line to return. |
No output schema declared.
No examples provided.
get_oscal_documentation ~123
Read an OSCAL documentation page by `docId` as a verbatim line range. Use when a query_oscal_documentation snippet is not enough. A response may hold fewer lines to fit the response budget; continue from `end-line` + 1 while `has-more` is true.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_id | string | yes | docId from a query_oscal_documentation result. |
| line_count | integer | – | Maximum lines to return, 1-500. |
| start_line | integer | – | 1-based first line to return. |
No output schema declared.
No examples provided.
get_oscal_schema ~106
Return the JSON schema or XML Schema (XSD) of one OSCAL model as text. Use when you need the structure of an OSCAL model: its properties, types, and required fields.
| Name | Type | Req | Description |
|---|---|---|---|
| model_name | string | yes | OSCAL model name from list_oscal_models, or "complete" for all models (very large). |
| schema_type | string | – | "json" returns the JSON schema as JSON text; "xsd" returns the XML Schema. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_assessment_plan_activities ~98
List activities in loaded OSCAL Assessment Plans with UUID, title, and parent document. Get an activity's OSCAL JSON with get_child_element. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| parent_doc_uuid | – | – | UUID of one parent document to scope results to. Omit for all documents. |
No output schema declared.
No examples provided.
list_assessment_plan_tasks ~98
List tasks in loaded OSCAL Assessment Plans with UUID, title, and parent document. Get a task's OSCAL JSON with get_child_element. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| parent_doc_uuid | – | – | UUID of one parent document to scope results to. Omit for all documents. |
No output schema declared.
No examples provided.
list_assessment_plans ~79
List loaded OSCAL Assessment Plans with UUID, title, child count, and size. Use when picking a `query_value` for query_assessment_plan. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
No output schema declared.
No examples provided.
list_assessment_results ~78
List loaded OSCAL Assessment Results with UUID, title, child count, and size. Use when picking a `query_value` for query_assessment_results. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
No output schema declared.
No examples provided.
list_assessment_results_findings ~98
List findings in loaded OSCAL Assessment Results with UUID, title, and parent document. Get a finding's OSCAL JSON with get_child_element. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| parent_doc_uuid | – | – | UUID of one parent document to scope results to. Omit for all documents. |
No output schema declared.
No examples provided.
list_assessment_results_results ~97
List results in loaded OSCAL Assessment Results with UUID, title, and parent document. Get a result's OSCAL JSON with get_child_element. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| parent_doc_uuid | – | – | UUID of one parent document to scope results to. Omit for all documents. |
No output schema declared.
No examples provided.
list_capabilities ~78
List loaded Capabilities with UUID, name, and parent Component Definition. Use when working with Component Definitions that contain capabilities; the list is empty when none do. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
No output schema declared.
No examples provided.
list_catalog_controls ~104
List controls in loaded OSCAL Catalogs with token ID (e.g. ac-1), title, and parent document. Get a control's OSCAL JSON with get_child_element. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| parent_doc_uuid | – | – | UUID of one parent document to scope results to. Omit for all documents. |
No output schema declared.
No examples provided.
list_catalog_groups ~101
List control groups (families) in loaded OSCAL Catalogs with token ID, title, and parent document. Get a group's OSCAL JSON with get_child_element. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| parent_doc_uuid | – | – | UUID of one parent document to scope results to. Omit for all documents. |
No output schema declared.
No examples provided.
list_catalogs ~74
List loaded OSCAL Catalogs with UUID, title, child count, and size. Use when picking a `query_value` for query_catalog. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
No output schema declared.
No examples provided.
list_component_definitions ~76
List loaded Component Definitions with UUID, title, component count, and size. Use when picking a `component_definition_filter` for query_component_definition. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
No output schema declared.
No examples provided.
list_components ~71
List loaded Components with UUID, title, and parent Component Definition. Use when picking a `query_value` for query_component_definition. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
No output schema declared.
No examples provided.
list_mapping_collection_mappings ~97
List mappings in loaded OSCAL Mapping Collections with UUID, title, and parent document. Get a mapping's OSCAL JSON with get_child_element. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| parent_doc_uuid | – | – | UUID of one parent document to scope results to. Omit for all documents. |
No output schema declared.
No examples provided.
list_mapping_collections ~77
List loaded OSCAL Mapping Collections with UUID, title, child count, and size. Use when picking a `query_value` for query_mapping_collection. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
No output schema declared.
No examples provided.
list_oscal_models ~61
List the OSCAL model names, each with description, layer, formal and short names, and release status. Use when you need a valid `model_name` for get_oscal_schema or a `model` for the Metaschema tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_oscal_resources ~77
List OSCAL community resources (tools, content, articles, talks) from the awesome-oscal list, each with `category` and markdown `text`. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
No output schema declared.
No examples provided.
list_poam_items ~101
List POA&M items in loaded OSCAL POA&Ms with ID, title, and parent document. Get an item's OSCAL JSON with get_child_element. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| parent_doc_uuid | – | – | UUID of one parent document to scope results to. Omit for all documents. |
No output schema declared.
No examples provided.
list_poams ~78
List loaded OSCAL Plans of Action and Milestones with UUID, title, child count, and size. Use when picking a `query_value` for query_poam. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
No output schema declared.
No examples provided.
list_profile_imports ~100
List imports in loaded OSCAL Profiles, with positional IDs (import-0, import-1). Get an import's OSCAL JSON with get_child_element. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| parent_doc_uuid | – | – | UUID of one parent document to scope results to. Omit for all documents. |
No output schema declared.
No examples provided.
list_profile_modify ~94
List the modify element (control tailoring) of loaded OSCAL Profiles, one per profile. Get its OSCAL JSON with get_child_element. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| parent_doc_uuid | – | – | UUID of one parent document to scope results to. Omit for all documents. |
No output schema declared.
No examples provided.
list_profiles ~72
List loaded OSCAL Profiles with UUID, title, child count, and size. Use when picking a `query_value` for query_profile. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
No output schema declared.
No examples provided.
list_ssp_control_implementations ~98
List the control-implementation element of loaded OSCAL SSPs, one per SSP. Get its OSCAL JSON with get_child_element. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| parent_doc_uuid | – | – | UUID of one parent document to scope results to. Omit for all documents. |
No output schema declared.
No examples provided.
list_ssp_system_components ~99
List system components in loaded OSCAL SSPs with UUID, title, and parent document. Get a component's OSCAL JSON with get_child_element. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| parent_doc_uuid | – | – | UUID of one parent document to scope results to. Omit for all documents. |
No output schema declared.
No examples provided.
list_ssps ~77
List loaded OSCAL System Security Plans with UUID, title, child count, and size. Use when picking a `query_value` for query_ssp. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
No output schema declared.
No examples provided.
query_assessment_plan ~124
Return loaded OSCAL Assessment Plans with `childTypeCounts`. For child elements, use list_assessment_plan_tasks or list_assessment_plan_activities, then get_child_element.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| query_type | string | – | "all" (paged), "by_uuid", or "by_title" (exact, then full-text). |
| query_value | – | – | UUID or title to match. Required for by_uuid and by_title. |
No output schema declared.
No examples provided.
query_assessment_results ~124
Return loaded OSCAL Assessment Results with `childTypeCounts`. For child elements, use list_assessment_results_results or list_assessment_results_findings, then get_child_element.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| query_type | string | – | "all" (paged), "by_uuid", or "by_title" (exact, then full-text). |
| query_value | – | – | UUID or title to match. Required for by_uuid and by_title. |
No output schema declared.
No examples provided.
query_catalog ~119
Return loaded OSCAL Catalogs with metadata and `childTypeCounts`. For controls and groups, use list_catalog_controls or list_catalog_groups, then get_child_element.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| query_type | string | – | "all" (paged), "by_uuid", or "by_title" (exact, then full-text). |
| query_value | – | – | UUID or title to match. Required for by_uuid and by_title. |
No output schema declared.
No examples provided.
query_component_definition ~253
Return OSCAL Components from loaded Component Definitions as OSCAL JSON, or one Capability when a by_uuid or by_title query matches a Capability. Use when you need component details: call it directly with by_title or by_type when you know the name or type, else find UUIDs and titles first with list_components; use list_capabilities or get_capability only for Component Definitions that contain capabilities. Results are paged.
| Name | Type | Req | Description |
|---|---|---|---|
| component_definition_filter | – | – | UUID or exact title (case-insensitive) of one Component Definition to search. Omit to search all. |
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| query_type | string | – | "all" (paged, large without a filter), "by_uuid", "by_title" (title, then property value), or "by_type" (Component type). by_uuid and by_title return a matching Capability first. |
| query_value | – | – | UUID, title, or Component type to match. Required unless query_type is "all". |
| return_format | string | – | Response format. Only "raw" (OSCAL JSON) is supported. |
Structured output declared, but exposes no named fields.
No examples provided.
query_mapping_collection ~118
Return loaded OSCAL Mapping Collections with metadata and `childTypeCounts`. For mappings, use list_mapping_collection_mappings, then get_child_element.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| query_type | string | – | "all" (paged), "by_uuid", or "by_title" (exact, then full-text). |
| query_value | – | – | UUID or title to match. Required for by_uuid and by_title. |
No output schema declared.
No examples provided.
query_oscal_documentation ~124
Search OSCAL documentation (Knowledge Base if configured, plus local docs) and return paged passages. Use when a schema lacks the answer; for a model property try get_oscal_schema. Pass a hit's `docId` to get_oscal_documentation for the full page.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. A page may hold fewer to fit the response budget. |
| offset | integer | – | Zero-based index of the first item. |
| query | string | yes | Question or search terms about OSCAL. |
No output schema declared.
No examples provided.
query_poam ~122
Return loaded OSCAL Plans of Action and Milestones with metadata and `childTypeCounts`. For POA&M items, use list_poam_items, then get_child_element.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| query_type | string | – | "all" (paged), "by_uuid", or "by_title" (exact, then full-text). |
| query_value | – | – | UUID or title to match. Required for by_uuid and by_title. |
No output schema declared.
No examples provided.
query_profile ~119
Return loaded OSCAL Profiles with metadata and `childTypeCounts`. For child elements, use list_profile_imports or list_profile_modify, then get_child_element.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| query_type | string | – | "all" (paged), "by_uuid", or "by_title" (exact, then full-text). |
| query_value | – | – | UUID or title to match. Required for by_uuid and by_title. |
No output schema declared.
No examples provided.
query_ssp ~126
Return loaded OSCAL SSPs with metadata and `childTypeCounts`. For child elements, use list_ssp_control_implementations or list_ssp_system_components, then get_child_element.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. |
| offset | integer | – | Zero-based index of the first item. |
| query_type | string | – | "all" (paged), "by_uuid", or "by_title" (exact, then full-text). |
| query_value | – | – | UUID or title to match. Required for by_uuid and by_title. |
No output schema declared.
No examples provided.
text_search_oscal ~129
Search loaded OSCAL documents and child elements, including control prose, ranked by relevance. Pass a child hit's entity ID and `parentDocumentUuid` to get_child_element.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items per page, 1-100. A page may hold fewer to fit the response budget. |
| offset | integer | – | Zero-based index of the first item. |
| oscal_model_type | – | – | OSCAL model name from list_oscal_models, e.g. "catalog". Omit for all models. |
| query_text | string | yes | Full-text search terms. |
No output schema declared.
No examples provided.
validate_oscal_content ~103
Validate OSCAL JSON text and return per-level results for JSON syntax, JSON Schema, the OSCAL model, and oscal-cli (skipped when not installed). Later levels are skipped when the JSON does not parse.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | OSCAL JSON document as a string. |
| model_type | – | – | OSCAL model name from list_oscal_models, e.g. "catalog". Omit to detect it from the document's root key. |
No output schema declared.
No examples provided.
validate_oscal_file ~127
Validate an OSCAL JSON file and return per-level results for JSON syntax, JSON Schema, the OSCAL model, and oscal-cli (skipped when not installed). Use when the document is in a file; for JSON text use validate_oscal_content.
| Name | Type | Req | Description |
|---|---|---|---|
| file_uri | string | yes | Path or URI of an OSCAL JSON file. Remote URIs are rejected unless the server operator enables remote URIs. |
| model_type | – | – | OSCAL model name from list_oscal_models, e.g. "catalog". Omit to detect it from the document's root key. |
No output schema declared.
No examples provided.
How do I install the MCP Server for OSCAL server?
MCP Server for OSCAL runs locally as a PyPI package, launched with uvx mcp-server-for-oscal. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-server-for-oscal
claude mcp add dfkunstler-mcp-server-for-oscal -- uvx mcp-server-for-oscal
What is the MCP Server for OSCAL server?
MCP Server for OSCAL is listed in the public MCP registry as io.github.dfkunstler/mcp-server-for-oscal. AI agent tools for Open Security Controls Assessment Language (OSCAL). This page covers its PyPI package (mcp-server-for-oscal).
Is the MCP Server for OSCAL server safe to use?
MCP Server for OSCAL scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 MCP Server for OSCAL server expose?
MCP Server for OSCAL exposes 46 tools: list_oscal_models, get_oscal_schema, get_allowed_values, get_constraints, find_references_to, and 41 more. Their descriptions and schemas cost roughly 5,138 tokens of context every time the server is loaded.
Is the MCP Server for OSCAL server still maintained?
MCP Server for OSCAL is still listed as active in the MCP registry. We last reached this channel on 5 November 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 MCP Server for OSCAL server under?
MCP Server for OSCAL 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.
What did VerifyMCP test on the MCP Server for OSCAL server?
VerifyMCP ran 16 checks on MCP Server for OSCAL, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.