Is MCP Server for OSCAL safe to use?

MCP Server for OSCAL has an HVTrust score of 62.3/100 (Grade C), ranked #558 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Server for OSCAL?

MCP Server for OSCAL scores 62.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 53 GitHub stars and is categorized under MCP Servers.

MCP Server for OSCAL

awslabs/mcp-server-for-oscal

OSCAL tools for AI agents

MCP Servers Python Needs review Apache-2.0

Is MCP Server for OSCAL safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.5 / 10

Provenance Attested

Signed commits 95%

Last push 95d ago

Compare MCP Server for OSCAL

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Server for OSCAL scores 62.3/100 (Grade C), ranked #558 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.5/10; 95% of recent commits are signed; last pushed 2026-06-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Server for OSCAL compares in MCP Servers

#312 Red Hat Lightspeed MCP 62.5 +0.2
#313 Arr MCP 62.4 +0.1
#314 MCP Server for OSCAL 62.3 this agent
#315 Unity MCP 62.3 ±0
#316 Power BI Modeling MCP Server 62.3 ±0

Bars show each HVTrust score; the tick marks MCP Server for OSCAL’s 62.3.

Where the 62.3 comes from

HVTrust dimensions vs the MCP Servers average

62.3 / 100 · 100.0% confidence

MCP Server for OSCAL MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

17.9 / 25

7.6 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.3 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

5.7 / 20

6.4 below avg 12.1

AdoptionLog-scaled stars · package downloads

6.4 / 20

0.8 below avg 7.2

Quick Trust Read

What Would Improve It

Improve maintenance to lift the weakest part of the trust profile.

Recent Changes

2026-09-26

Warning Issued

Warning: eligibility issues detected

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Amazon Bedrock

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.5/10. Tighten the weakest checks to improve public safety evidence.

Refresh maintenance signals The repo was last pushed 95 days ago. Fresh activity helps separate stable projects from stale ones.

Review Flags

[5.1] repository is archived

Compare with another agent Get email alerts for MCP Server for OSCAL View MCP Servers Report missing data

26.7

Activity sub-score · out of 100

#314

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-06-23

95 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #560

Analysis

Activity Inputs

26.7 / 100

StarsRepository reach

10.4 / 30

FreshnessLast push recency

11.8 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

4.4 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

4.5 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

95%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 9

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about MCP Server for OSCAL

MCP Server for OSCAL has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does MCP Server for OSCAL publish package provenance?

Yes. MCP Server for OSCAL's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does MCP Server for OSCAL have an OpenSSF Scorecard?

MCP Server for OSCAL has an OpenSSF Scorecard score of 4.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is MCP Server for OSCAL actively maintained?

Slowing down. Last push was 95 days ago — keep an eye on whether activity resumes.

What license does MCP Server for OSCAL use?

MCP Server for OSCAL ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Server for OSCAL's commits signed?

94% of the last 100 commits to MCP Server for OSCAL are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

MCP Server for OSCAL appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Amazon Bedrock

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to MCP Server for OSCAL's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Amazon Bedrock

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

Maintain MCP Server for OSCAL?

For maintainers

HVTrust scores MCP Server for OSCAL from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-26

Warning Issued

Warning: eligibility issues detected

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Amazon Bedrock

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 620 spots (#1172 → #552)

2026-09-23

HVTrust Changed

HVTrust up 42.2pts (20.2 → 62.4)

2026-09-22

Newly Listed

First tracked at rank #1172

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-08

Rank Moved

Rank dropped 12 spots (#490 → #502)

2026-09-07

Rank Moved

Rank dropped 31 spots (#459 → #490)

2026-09-06

Rank Moved

Rank dropped 11 spots (#448 → #459)

2026-09-05

Rank Moved

Rank dropped 65 spots (#383 → #448)

2026-09-04

Rank Moved

Rank dropped 11 spots (#372 → #383)

2026-09-03

Rank Moved

Rank dropped 20 spots (#352 → #372)

2026-09-02

Warning Issued

Warning: eligibility issues detected

2026-08-31

Rank Moved

Rank dropped 30 spots (#306 → #336)

2026-08-30

Rank Moved

Rank rose 10 spots (#316 → #306)

2026-08-29

Rank Moved

Rank dropped 19 spots (#297 → #316)

2026-08-27

Rank Moved

Rank dropped 11 spots (#277 → #288)

2026-08-26

Scorecard Added

OSSF Scorecard: 4.5/10

2026-08-26

Rank Moved

Rank rose 144 spots (#421 → #277)

2026-08-26

HVTrust Changed

HVTrust up 9.2pts (54.8 → 64.0)

2026-08-24

Rank Moved

Rank dropped 16 spots (#402 → #418)

2026-08-22

Rank Moved

Rank rose 15 spots (#415 → #400)

2026-08-19

Rank Moved

Rank dropped 12 spots (#399 → #411)

2026-08-17

Rank Moved

Rank rose 12 spots (#411 → #399)

2026-08-13

Rank Moved

Rank dropped 17 spots (#382 → #399)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-12

Rank Moved

Rank rose 18 spots (#400 → #382)

2026-08-10

Rank Moved

Rank dropped 20 spots (#378 → #398)

2026-08-08

Newly Listed

First tracked at rank #375

GitHub → PyPI: mcp-server-for-oscal

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-server-for-oscal.svg)](https://hvtracker.net/agents/mcp-server-for-oscal)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-server-for-oscal"><img src="https://hvtracker.net/badge/mcp-server-for-oscal.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON