Is SAS MCP Server safe to use?

SAS MCP Server has an HVTrust score of 59.1/100 (Grade C), ranked #660 of 1343 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for SAS MCP Server?

SAS MCP Server scores 59.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 61 GitHub stars and is categorized under MCP Servers.

SAS MCP Server

Repository

Website

A self-hosted Model Context Protocol (MCP) server that connects to your SAS Viya environment and provides tools across the analytics lifecycle.

MCP Servers Python Listed Apache-2.0

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

OSSF Scorecard 5.1 / 10

Provenance None

Signed commits 94%

Last push 2d ago

Compare SAS MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: SAS MCP Server scores 59.1/100 (Grade C), ranked #660 of 1343 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.1/10; 94% of recent commits are signed; last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How SAS MCP Server 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.

Raise the OSSF Scorecard from 5.1 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Dependency-Update-Tool 0 +8.2 → 67.3 B · #238 of 778

Already done? Suggest a correction Add the trust badge

How SAS MCP Server compares in MCP Servers

Bars show each HVTrust score; the tick marks SAS MCP Server’s 59.1.

Where the 59.1 comes from

HVTrust dimensions vs the MCP Servers average

59.1 / 100 · 100.0% confidence

SAS MCP Server MCP Servers average (778 agents)

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

11.1 / 25

0.8 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.8 / 17

0.6 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

19.1 / 20

6.9 above avg 12.2

AdoptionLog-scaled stars · package downloads

4.3 / 20

3.0 below avg 7.3

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-30

Rank Moved

Rank dropped 34 spots (#627 → #661)

2026-09-24

Rank Moved

Rank rose 11 spots (#635 → #624)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

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

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

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

64.7

Activity sub-score · out of 100

#367

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-10-01

Activity & Reach

Stars

Forks

Last Push

2026-09-29

2 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #661

Analysis

Activity Inputs

64.7 / 100

StarsRepository reach

10.8 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

22.7 / 25

CommunityFork signal

6.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.1 / 10

OpenSSF Scorecard · scanned Sep 30, 2026

Signed Commits

94%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 6

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 1

SAST 0

Security-Policy 4

Signed-Releases -1

Token-Permissions 8

Vulnerabilities 0

Common questions about SAS MCP Server

SAS MCP Server 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 SAS MCP Server publish package provenance?

No published build provenance is currently detected for SAS MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does SAS MCP Server have an OpenSSF Scorecard?

SAS MCP Server has an OpenSSF Scorecard score of 5.1/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 SAS MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 2 day(s).

What license does SAS MCP Server use?

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

Are SAS MCP Server's commits signed?

94% of the last 100 commits to SAS MCP Server 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

SAS MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

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

N/A

No package source configured

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 SAS MCP Server'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

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain SAS MCP Server?

For maintainers

HVTrust scores SAS MCP Server 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-30

Rank Moved

Rank dropped 34 spots (#627 → #661)

2026-09-24

Rank Moved

Rank rose 11 spots (#635 → #624)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 203 spots (#432 → #635)

2026-09-23

HVTrust Changed

HVTrust up 14.8pts (45.0 → 59.8)

2026-09-22

Newly Listed

First tracked at rank #432

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-12

Rank Moved

Rank dropped 14 spots (#599 → #613)

2026-09-11

Rank Moved

Rank dropped 18 spots (#581 → #599)

2026-09-08

Rank Moved

Rank dropped 10 spots (#562 → #572)

2026-09-07

Rank Moved

Rank dropped 33 spots (#529 → #562)

2026-09-05

Rank Moved

Rank dropped 82 spots (#440 → #522)

2026-09-03

Rank Moved

Rank dropped 11 spots (#433 → #444)

2026-09-01

Scorecard Added

OSSF Scorecard: 5.5/10

2026-09-01

Grade Changed

Trust grade D → C

2026-09-01

Rank Moved

Rank rose 715 spots (#1139 → #424)

2026-09-01

HVTrust Changed

HVTrust up 35.1pts (24.5 → 59.6)

2026-08-31

Rank Moved

Rank dropped 21 spots (#1118 → #1139)

2026-08-30

Rank Moved

Rank dropped 49 spots (#1069 → #1118)

2026-08-29

Rank Moved

Rank dropped 47 spots (#1022 → #1069)

2026-08-28

Rank Moved

Rank dropped 34 spots (#988 → #1022)

2026-08-27

Rank Moved

Rank dropped 24 spots (#964 → #988)

2026-08-26

Rank Moved

Rank dropped 107 spots (#857 → #964)

2026-08-22

Rank Moved

Rank rose 10 spots (#859 → #849)

2026-08-17

Rank Moved

Rank rose 20 spots (#876 → #856)

2026-08-16

Newly Listed

First tracked at rank #876

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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