updated 2026-08-12 05:02 UTC

MCP Server for OSCAL

awslabs/mcp-server-for-oscal

OSCAL tools for AI agents

MCP Servers Python Grade C Listed Apache-2.0
55.8/100
Rank #399 of 1283
Compare MCP Server for OSCAL

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-06-23 · 50d ago
Recent change
Rank +1

Is MCP Server for OSCAL safe? MCP Server for OSCAL scores 55.8/100 (Grade C), ranked #399 of 1283 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; no OSSF Scorecard result yet; 95% of recent commits are signed; last pushed 2026-06-23. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#131 Xcode: MCP Bridge Wrapper for Cursor — 56.3 (C) → #132 GPU MCP Server — 56.0 (C) → #134 Screaming Frog SEO Spider MCP Server — 55.4 (C) → #135 Figma Ui MCP — 55.3 (C) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 20 spots (#378 → #398)
2026-08-08
Newly Listed
First tracked at rank #375
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Refresh maintenance signals The repo was last pushed 50 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for MCP Server for OSCAL View MCP Servers Report missing data
32.7
Activity sub-score · out of 100
#133
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 →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 50 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
51
Forks
7
Last Push
2026-06-23
50 days ago
Commits (4 wk)
0
Downloads (7d)
88
pypi
HN mentions (30d)
—
Open Issues
9
Rank Change
▲1
was #400

Analysis

HVTrust Dimensions vs MCP Servers

55.8 / 100 · 100.0% confidence

MCP Server for OSCAL MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.2 / 25
7.2 above avg 5.0
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.7 above avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
8.7 / 20
3.7 below avg 12.4
AdoptionLog-scaled stars · package downloads
6.7 / 20
0.9 above avg 5.8

Activity Inputs

32.7 / 100
StarsRepository reach
10.3 / 30
FreshnessLast push recency
18.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.2 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
—
Not available
Signed Commits
95%
of last 100 commits verified

Is MCP Server for OSCAL safe?

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?
No OpenSSF Scorecard data is currently published for MCP Server for OSCAL. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is MCP Server for OSCAL actively maintained?
Slowing down. Last push was 50 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.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Declared
Declared plugin/integration 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

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
Listed 1Rank 1
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
HVTrust 55.8 Grade C
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON