# MCP Server for OSCAL (pypi · mcp-server-for-oscal)

AI agent tools for Open Security Controls Assessment Language (OSCAL)

- Trust score: 94/100 (high trust)
- Change this week: +19
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `mcp-server-for-oscal`: 94/100 (this document), [markdown](https://verifymcp.io/servers/dfkunstler-mcp-server-for-oscal/mcp-server-for-oscal.md), [page](https://verifymcp.io/servers/dfkunstler-mcp-server-for-oscal/mcp-server-for-oscal)

## Channel facts

- Registry: `pypi`
- Package: `mcp-server-for-oscal`
- Version: `0.7.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 53 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to dfkunstler/mcp-server-for-oscal).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 94/100
  - Stability check failed: the tool surface changed between 0.5.2 and 0.7.1: 0 tool removals, 5 breaking changes, 6 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (9% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 46 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 47 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add dfkunstler-mcp-server-for-oscal -- uvx mcp-server-for-oscal
```

### Cursor

```json
{
  "mcpServers": {
    "dfkunstler-mcp-server-for-oscal": {
      "command": "uvx",
      "args": [
        "mcp-server-for-oscal"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dfkunstler-mcp-server-for-oscal": {
      "command": "uvx",
      "args": [
        "mcp-server-for-oscal"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dfkunstler-mcp-server-for-oscal -- uvx mcp-server-for-oscal
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dfkunstler-mcp-server-for-oscal": {
      "type": "local",
      "command": [
        "uvx",
        "mcp-server-for-oscal"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dfkunstler-mcp-server-for-oscal --command uvx --arg mcp-server-for-oscal
```

### Hermes

```yaml
mcp_servers:
  dfkunstler-mcp-server-for-oscal:
    command: "uvx"
    args: ["mcp-server-for-oscal"]
```

### Netclaw

```json
{
  "McpServers": {
    "dfkunstler-mcp-server-for-oscal": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-server-for-oscal"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dfkunstler-mcp-server-for-oscal -t stdio -c uvx -a mcp-server-for-oscal
```

### Other

```json
{
  "mcpServers": {
    "dfkunstler-mcp-server-for-oscal": {
      "command": "uvx",
      "args": [
        "mcp-server-for-oscal"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 94, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 79, +3)

- [security improvement] CVE-2026-59951 no longer affects this package
- [security improvement] CVE-2026-116685 no longer affects this package
- [security improvement] CVE-2026-116684 no longer affects this package
- [security improvement] CVE-2026-116686 no longer affects this package
- [security improvement] Known CVEs: fail → pass

### 2026-10-30 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 94.

### 2026-10-29 (score 75, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-28 (score 90, 0)

- [security regression] CVE-2026-116685 affects this package: high
- [security regression] CVE-2026-116684 affects this package: high
- [security regression] CVE-2026-116686 affects this package: high

### 2026-10-27 (score 90, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-26 (score 74, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.7.0 → 0.7.1

### 2026-10-25 (score 89, +16)

- [security improvement] Malware scan: unverified → pass

## MCP tools (46)

### `list_oscal_models` (~61 tokens)

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.

### `get_oscal_schema` (~106 tokens)

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.

Input parameters:

- `model_name` (string, required): 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.

Output parameters:

- `result` (string)

### `get_allowed_values` (~208 tokens)

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`.

Input parameters:

- `limit` (integer): Maximum items per page, 1-100. A page may hold fewer to fit the response budget.
- `model` (string, required): OSCAL model name from list_oscal_models, e.g. "catalog".
- `offset` (integer): Zero-based index of the first item.
- `target` (string, required): 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.

### `get_constraints` (~245 tokens)

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.

Input parameters:

- `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, required): OSCAL model name from list_oscal_models, e.g. "catalog".
- `offset` (integer): Zero-based index of the first item.
- `target` (string, required): 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.

### `find_references_to` (~226 tokens)

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.

Input parameters:

- `assembly` (string, required): 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.

### `get_definition` (~200 tokens)

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`.

Input parameters:

- `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, required): 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.

### `get_metaschema_source` (~166 tokens)

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.

Input parameters:

- `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.

### `list_oscal_resources` (~77 tokens)

List OSCAL community resources (tools, content, articles, talks) from the awesome-oscal
list, each with `category` and markdown `text`. Results are paged.

Input parameters:

- `limit` (integer): Maximum items per page, 1-100.
- `offset` (integer): Zero-based index of the first item.

### `query_component_definition` (~253 tokens)

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.

Input parameters:

- `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.

### `list_component_definitions` (~76 tokens)

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.

Input parameters:

- `limit` (integer): Maximum items per page, 1-100.
- `offset` (integer): Zero-based index of the first item.

### `list_components` (~71 tokens)

List loaded Components with UUID, title, and parent Component Definition. Use when
picking a `query_value` for query_component_definition. Results are paged.

Input parameters:

- `limit` (integer): Maximum items per page, 1-100.
- `offset` (integer): Zero-based index of the first item.

### `list_capabilities` (~78 tokens)

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.

Input parameters:

- `limit` (integer): Maximum items per page, 1-100.
- `offset` (integer): Zero-based index of the first item.

### `get_capability` (~55 tokens)

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.

Input parameters:

- `uuid` (string, required): UUID of the Capability, from list_capabilities.

Output parameters:

- `result`

### `validate_oscal_content` (~103 tokens)

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.

Input parameters:

- `content` (string, required): 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.

### `validate_oscal_file` (~127 tokens)

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.

Input parameters:

- `file_uri` (string, required): 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.

### `query_catalog` (~119 tokens)

Return loaded OSCAL Catalogs with metadata and `childTypeCounts`. For controls and groups,
use list_catalog_controls or list_catalog_groups, then get_child_element.

Input parameters:

- `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.

### `list_catalogs` (~74 tokens)

List loaded OSCAL Catalogs with UUID, title, child count, and size. Use when picking a
\`query_value` for query_catalog. Results are paged.

Input parameters:

- `limit` (integer): Maximum items per page, 1-100.
- `offset` (integer): Zero-based index of the first item.

### `query_ssp` (~126 tokens)

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.

Input parameters:

- `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.

### `list_ssps` (~77 tokens)

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.

Input parameters:

- `limit` (integer): Maximum items per page, 1-100.
- `offset` (integer): Zero-based index of the first item.

### `query_profile` (~119 tokens)

Return loaded OSCAL Profiles with metadata and `childTypeCounts`. For child elements, use
list_profile_imports or list_profile_modify, then get_child_element.

Input parameters:

- `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.

### `list_profiles` (~72 tokens)

List loaded OSCAL Profiles with UUID, title, child count, and size. Use when picking a
\`query_value` for query_profile. Results are paged.

Input parameters:

- `limit` (integer): Maximum items per page, 1-100.
- `offset` (integer): Zero-based index of the first item.

### `query_assessment_plan` (~124 tokens)

Return loaded OSCAL Assessment Plans with `childTypeCounts`. For child elements, use list_assessment_plan_tasks or list_assessment_plan_activities, then
get_child_element.

Input parameters:

- `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.

### `list_assessment_plans` (~79 tokens)

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.

Input parameters:

- `limit` (integer): Maximum items per page, 1-100.
- `offset` (integer): Zero-based index of the first item.

### `query_assessment_results` (~124 tokens)

Return loaded OSCAL Assessment Results with `childTypeCounts`. For child elements, use list_assessment_results_results or list_assessment_results_findings, then
get_child_element.

Input parameters:

- `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.

### `list_assessment_results` (~78 tokens)

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.

Input parameters:

- `limit` (integer): Maximum items per page, 1-100.
- `offset` (integer): Zero-based index of the first item.

### `query_poam` (~122 tokens)

Return loaded OSCAL Plans of Action and Milestones with metadata and `childTypeCounts`.
For POA&M items, use list_poam_items, then get_child_element.

Input parameters:

- `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.

### `list_poams` (~78 tokens)

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.

Input parameters:

- `limit` (integer): Maximum items per page, 1-100.
- `offset` (integer): Zero-based index of the first item.

### `query_mapping_collection` (~118 tokens)

Return loaded OSCAL Mapping Collections with metadata and `childTypeCounts`. For
mappings, use list_mapping_collection_mappings, then get_child_element.

Input parameters:

- `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.

### `list_mapping_collections` (~77 tokens)

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.

Input parameters:

- `limit` (integer): Maximum items per page, 1-100.
- `offset` (integer): Zero-based index of the first item.

### `text_search_oscal` (~129 tokens)

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.

Input parameters:

- `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, required): Full-text search terms.

### `list_catalog_controls` (~104 tokens)

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.

Input parameters:

- `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.

### `list_catalog_groups` (~101 tokens)

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.

Input parameters:

- `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.

### `list_ssp_control_implementations` (~98 tokens)

List the control-implementation element of loaded OSCAL SSPs, one per SSP. Get
its OSCAL JSON with get_child_element. Results are paged.

Input parameters:

- `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.

### `list_ssp_system_components` (~99 tokens)

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.

Input parameters:

- `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.

### `list_profile_imports` (~100 tokens)

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.

Input parameters:

- `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.

### `list_profile_modify` (~94 tokens)

List the modify element (control tailoring) of loaded OSCAL Profiles, one per profile.
Get its OSCAL JSON with get_child_element. Results are paged.

Input parameters:

- `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.

### `list_assessment_plan_tasks` (~98 tokens)

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.

Input parameters:

- `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.

### `list_assessment_plan_activities` (~98 tokens)

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.

Input parameters:

- `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.

### `list_assessment_results_results` (~97 tokens)

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.

Input parameters:

- `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.

### `list_assessment_results_findings` (~98 tokens)

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.

Input parameters:

- `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.

### `list_poam_items` (~101 tokens)

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.

Input parameters:

- `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.

### `list_mapping_collection_mappings` (~97 tokens)

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.

Input parameters:

- `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.

### `get_child_element` (~104 tokens)

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.

Input parameters:

- `element_id` (string, required): 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.

Output parameters:

- `result`

### `query_oscal_documentation` (~124 tokens)

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.

Input parameters:

- `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, required): Question or search terms about OSCAL.

### `get_oscal_documentation` (~123 tokens)

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.

Input parameters:

- `doc_id` (string, required): 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.

### `about` (~34 tokens)

Return server metadata: package version, keywords, bundled OSCAL version, and the number of documents loaded from OSCAL_DOCUMENTS_DIR.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/dfkunstler-mcp-server-for-oscal/mcp-server-for-oscal#diagnostics

## Score history

- 2026-11-05: 94
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 90
- 2026-10-27: 90
- 2026-10-26: 74
- 2026-10-25: 89
- 2026-10-24: 73
- 2026-10-23: 70
- 2026-10-22: 69
- 2026-10-21: 84
- 2026-10-20: 83
- 2026-10-19: 83
- 2026-10-18: 82
- 2026-10-17: 67
- 2026-10-16: 82
- 2026-10-15: 69
- 2026-10-14: 83
- 2026-10-13: 34
- 2026-10-12: 38
- 2026-10-04: 64
- 2026-10-03: 63
- 2026-10-02: 63
- 2026-10-01: 62
- 2026-09-30: 62

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/mcp-server-for-oscal/
- Socket report: https://socket.dev/pypi/package/mcp-server-for-oscal
- Repository: https://github.com/dfkunstler/mcp-server-for-oscal
- Changelog RSS feed: https://verifymcp.io/servers/dfkunstler-mcp-server-for-oscal/mcp-server-for-oscal.xml
- Changelog JSON feed: https://verifymcp.io/servers/dfkunstler-mcp-server-for-oscal/mcp-server-for-oscal/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dfkunstler-mcp-server-for-oscal/mcp-server-for-oscal.json
- HTML version of this page: https://verifymcp.io/servers/dfkunstler-mcp-server-for-oscal/mcp-server-for-oscal