updated 2026-11-11 00:08 UTC

MCP Server for OSCAL

Repository by awslabs

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 141d ago
Advisories None known
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 59.7/100 (Grade C), ranked #711 of 1387 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; no published advisory affects its latest release (mcp-server-for-oscal); last pushed 2026-06-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Server for OSCAL could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge
Active listing, but review is needed
  • [5.1] repository is archived

Chain of custody

Scanners check what the code says. This traces who ships MCP Server for OSCAL and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/awslabs/mcp-server-for-oscal, Apache-2.0, last pushed 2026-06-23. 95% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.5/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    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

  3. Published packages Partly attested

  4. What you install today No known advisories

    Latest release checked: mcp-server-for-oscal 0.7.1. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-26 OSSF Scorecard: 4.5/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues MCP Server for OSCAL’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How MCP Server for OSCAL compares in MCP Servers

  1. #384 CN Scraper MCP 59.8 +0.1
  2. #385 Microsoft Learn MCP 59.7 ±0
  3. #386 MCP Server for OSCAL 59.7 this agent
  4. #387 MCP Sqlite Tools 59.4 −0.3
  5. #388 Teamwork MCP 59.3 −0.4

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

Where the 59.7 comes from

HVTrust dimensions vs the MCP Servers average

59.7 / 100 · 100.0% confidence

MCP Server for OSCAL MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.9 / 25
7.1 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.3 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
2.6 / 20
9.7 below avg 12.3
AdoptionLog-scaled stars · package downloads
6.9 / 20
0.7 below avg 7.6

Quick Trust Read

What Would Improve It
Improve maintenance to lift the weakest part of the trust profile.
Recent Changes
2026-11-11
Warning Issued
Warning: eligibility issues detected
2026-11-10
Warning Cleared
Warning cleared: eligibility issues resolved
2026-11-06
Rank Moved
Rank dropped 20 spots (#681 → #701)
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 141 days ago. Fresh activity helps separate stable projects from stale ones.
Review Flags
[5.1] repository is archived
Compare with another agent
View MCP Servers Report missing data
20.6
Activity sub-score · out of 100
#386
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-11-11 00:08 UTC · Repo last pushed 141 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
52
Forks
9
Last Push
2026-06-23
141 days ago
Commits (4 wk)
0
Downloads (7d)
126
pypi
HN mentions (30d)
—
Open Issues
9
Rank Change
▼1
was #710

Analysis

Activity Inputs

20.6 / 100
StarsRepository reach
10.3 / 30
FreshnessLast push recency
5.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.7 / 20

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 141 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
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

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
Rank 23Warning Issued 5Warning Cleared 3HVTrust 2Scorecard 1Delisted 1Listed 1Grade 1Provenance 1MCP 1Surface 1
2026-11-11
Warning Issued
Warning: eligibility issues detected
2026-11-10
Warning Cleared
Warning cleared: eligibility issues resolved
2026-11-06
Rank Moved
Rank dropped 20 spots (#681 → #701)
2026-10-24
Rank Moved
Rank rose 11 spots (#654 → #643)
2026-10-19
Rank Moved
Rank dropped 16 spots (#634 → #650)
2026-10-11
Rank Moved
Rank dropped 13 spots (#598 → #611)
2026-10-09
Rank Moved
Rank dropped 13 spots (#578 → #591)
2026-10-07
Rank Moved
Rank dropped 13 spots (#558 → #571)
2026-10-05
Warning Issued
Warning: eligibility issues detected
2026-10-03
Warning Cleared
Warning cleared: eligibility issues resolved
2026-10-01
Rank Moved
Rank rose 25 spots (#578 → #553)
2026-09-30
Warning Issued
Warning: eligibility issues detected
2026-09-29
Warning Cleared
Warning cleared: eligibility issues resolved
2026-09-28
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)
GitHub → PyPI: mcp-server-for-oscal

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 59.7 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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON