Reported issues for MCP Server for OSCAL

Pod holds 19 of 37 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to MCP Server for OSCAL.

Most discussed

Add post-copy hash verification to OscalStore DB seeding

The OscalStore verifies the bundled DB's integrity before copying it to a new path, but does not verify the copy after writing. A corrupted copy (e.g., from disk errors or partial writes) would result in a silently broken server. This adds SHA-256 post-copy verification to both seeding paths (_resolve_persistent and _copy_bundled_to_temp), and removes the brittle test_new_path_with_bundled_db_seeds test that hardcodes a document count (232) which breaks when bundled DB content changes.

Read the thread · 2026-04-08 · closed · outside contributor · 0 comments

Add OAuth 2.1 authentication for streamable-http transport

Summary

The MCP server currently has no authentication or authorization when using streamable-http transport. The README explicitly warns against using it for this reason. The MCP Python SDK (v1.23+) now includes built-in OAuth 2.1 Resource Server support following the MCP authorization specification and RFC 9728 (Protected Resource Metadata). We should leverage this t

Read the thread · 2026-03-02 · open · outside contributor · 0 comments

AgentCore runtime support

Add support for AgentCore runtime deployment in AWS. Intent here is just to update MCP server implementation to satisfy AgentCore Runtime requirements. AgentCore configuration and deployment automation are out of scope for now.

Read the thread · 2026-02-20 · closed · outside contributor · 0 comments

Disable dependabot major-version updates

Major version update decisions should never be required for security purposes.

Read the thread · 2026-02-17 · closed · outside contributor · 0 comments

Include OSCAL Capabilities in query_component_definition results

Component Definition includes a Capability type, which aggregates Components

Read the thread · 2026-02-17 · closed · outside contributor · 0 comments

JSON schema validation

As a document reviewer, I need to be sure that any OSCAL document generated by the MCP server is well-formed JSON, so that I can catch and fix any LLM/Agent errors as early as possible.

Read the thread · 2026-01-21 · closed · outside contributor · 1 comment

Automatically create a PR for updates to awesome-oscal content

Tool list_oscal_resources depends on content from awesome-oscal project. We maintain a copy of that file in our source tree and, currently, must manually run a script to update it. Proposal: Setup GitHub notifications for updates to awesome-oscal project's README. When a new commit is pushed, exec `hatch run upd

Read the thread · 2025-12-19 · closed · outside contributor · 1 comment

new tool: validate_oscal_content

As an AI-agent user, I need to be sure that OSCAL content generated or modified by the LLM is both well-formed and valid according to the NIST definitions.

As an AI-agent user, I want the relevant validators to be determined automatically from my input and run in the appropriate order to ensure accurate results, so that I don't have to understand the dependencies or nuances of the tools.

Implement JSON schema validation; integrat

Read the thread · 2025-12-13 · closed · outside contributor · 4 comments

Most recent

test: Enable parallel test execution with pytest-xdist

Five tests in tests/tools/test_query_component_definition.py fail under pytest-xdist parallel execution because they depend on shared mutable module-level singletons (_store and _oscal_store). This prevents enabling parallel = true in [tool.hatch.envs.hatch-test].

Fix:

Add an autouse reset_store fixture that saves, clears, and restores singleton state around each test
Fix 5 tests that rely on implicit store population
Enable parallel = true in pyproject.toml
Add a

Read the thread · 2026-04-08 · closed · outside contributor · 0 comments

OSCAL content index

Develop scalable alternative to current in-memory ComponentDefinitionStore with support for all OSCAL models.

Read the thread · 2026-03-27 · closed · outside contributor · 0 comments

feat: Add agent session state, conversation management, and CLI wiring

Wire Strands SDK session management (FileSessionManager, S3SessionManager), conversation management (SlidingWindowConversationManager, SummarizingConversationManager, NullConversationManager), and agent state into the OSCAL agent factory and CLI. All changes are isolated to config.py, oscal_agent.py, and their test files. The MCP server (main.py) is unaffected. No new dependencies required.

Key changes:

Add session/conversation config env vars to Config
Extend `create_osca

Read the thread · 2026-03-24 · closed · outside contributor · 0 comments

feat: Refactor OSCAL Strands agent for production readiness

Summary

The oscal_agent.py module contains a prototype Strands agent that is not currently wired into the application. This issue refactors it into a production-ready agent with a standalone entry point.

User Stories

Centralized tool registry — As a developer, I want a single source of truth for which tools are available, so that adding a new tool doesn't require updating both main.py and oscal_agent.py separately.
Stateless agent module — As a developer, I want the

Read the thread · 2026-03-21 · closed · outside contributor · 0 comments

Publish to official MCP server registry

https://modelcontextprotocol.io/registry/quickstart

Read the thread · 2026-03-20 · closed · outside contributor · 0 comments

query_component_definitions tools overrun the context window

When many CDefs are loaded, certain queries from the agent return enough data to overrun the context window for most LLMs.

Add pagination to at least list* tools in query_component_definitions module.

Read the thread · 2026-03-20 · closed · outside contributor · 0 comments

trestle 4.0.1

Upgrade to trestle 4.0.1

Read the thread · 2026-03-20 · closed · outside contributor · 0 comments

feat(Skill): Create OSCAL Agent Skills package

Package existing resources as expected by Agent Skills standard to maximize compatibility. We already provide a Kiro Power, but that only works for Kiro users.

Read the thread · 2026-03-09 · open · outside contributor · 0 comments

OSCAL v1.2.1

Integrate OSCAL v1.2.1 patch release

Read the thread · 2026-03-06 · closed · outside contributor · 0 comments

Add smoke tests using standalone agent

Existing unit tests are great indicators of whether the server/tool code functions as expected. But they don't tell us whether interactions with the LLM produce expected results.

Read the thread · 2026-02-12 · open · outside contributor · 0 comments

Support multiple versions of OSCAL

Customer feedback received via email Thursday, February 5, 2026 at 04:40:

One additional thought on the auto-updating schema version: while this makes a lot of sense from a learning and onboarding perspective, I wonder whether a more “production-ready” version of the agent would need to handle older schemas as well. In real environments, teams may not always be ready to move to a new schema version immediately, particularly if files are being populated programmatically. Unless, of course, sche

Read the thread · 2026-02-11 · open · outside contributor · 0 comments

The remaining reports are on the project's issue tracker.