Is MCP For Stata safe to use?

MCP For Stata has an HVTrust score of 55.5/100 (Grade C), ranked #837 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP For Stata?

MCP For Stata scores 55.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 276 GitHub stars and is categorized under MCP Servers.

MCP For Stata

Repository Website

Stata-MCP: A MCP server for integrating Stata into your agent loop with a safety-first design.

MCP Servers Python Listed AGPL-3.0

Is MCP For Stata safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.6 / 10

Provenance None

Signed commits 9%

Last push 4d ago

Compare MCP For Stata

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP For Stata scores 55.5/100 (Grade C), ranked #837 of 1374 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.6/10; 9% of recent commits are signed; last pushed 2026-11-06. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP For Stata 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.6 to 9.0lowest checks: Code-Review 0, Fuzzing 0, Pinned-Dependencies 0 +7.1 → 62.6 C · #342 of 778
Sign every commit9% signed today +4.6 → 60.1 C · #380 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

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

Source Partly signed

github.com/SepineTam/mcp-for-stata, AGPL-3.0, last pushed 2026-11-06. 9% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.6/10 (scanned Oct 30, 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 5

CII-Best-Practices 5

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 5

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10
Published packages None

No registry package. MCP For Stata is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

2026-08-26 OSSF Scorecard: 5.7/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues MCP For Stata’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 For Stata compares in MCP Servers

Bars show each HVTrust score; the tick marks MCP For Stata’s 55.5.

Where the 55.5 comes from

HVTrust dimensions vs the MCP Servers average

55.5 / 100 · 100.0% confidence

MCP For Stata MCP Servers average (778 agents)

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

7.4 / 25

3.4 below avg 10.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.9 below avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

1.0 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

16.4 / 20

4.2 above avg 12.2

AdoptionLog-scaled stars · package downloads

5.9 / 20

1.7 below avg 7.6

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-11-06

Rank Moved

Rank rose 85 spots (#911 → #826)

2026-11-06

Activity Score Changed

Activity score up 7pts (55 → 62)

2026-11-05

Rank Moved

Rank dropped 19 spots (#892 → #911)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.6/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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent View MCP Servers Report missing data

61.3

Activity sub-score · out of 100

#460

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-11-10

Activity & Reach

Stars

276

Forks

Last Push

2026-11-06

4 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #837

Analysis

Activity Inputs

61.3 / 100

StarsRepository reach

14.7 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

14.7 / 25

CommunityFork signal

7.3 / 20

Common questions about MCP For Stata

MCP For Stata 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 For Stata publish package provenance?

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

Does MCP For Stata have an OpenSSF Scorecard?

MCP For Stata has an OpenSSF Scorecard score of 5.6/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 For Stata actively maintained?

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

What license does MCP For Stata use?

MCP For Stata ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP For Stata's commits signed?

9% of the last 100 commits to MCP For Stata 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 For Stata appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

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

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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 MCP For Stata'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

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain MCP For Stata?

For maintainers

HVTrust scores MCP For Stata 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-11-06

Rank Moved

Rank rose 85 spots (#911 → #826)

2026-11-06

Activity Score Changed

Activity score up 7pts (55 → 62)

2026-11-05

Rank Moved

Rank dropped 19 spots (#892 → #911)

2026-10-31

Rank Moved

Rank dropped 15 spots (#866 → #881)

2026-10-26

Rank Moved

Rank dropped 23 spots (#832 → #855)

2026-10-23

Rank Moved

Rank dropped 17 spots (#810 → #827)

2026-10-22

Rank Moved

Rank rose 36 spots (#846 → #810)

2026-10-19

Rank Moved

Rank rose 23 spots (#867 → #844)

2026-10-18

Rank Moved

Rank dropped 40 spots (#827 → #867)

2026-10-15

Rank Moved

Rank rose 12 spots (#831 → #819)

2026-10-14

Rank Moved

Rank dropped 72 spots (#759 → #831)

2026-10-08

Rank Moved

Rank rose 41 spots (#786 → #745)

2026-10-04

Rank Moved

Rank dropped 11 spots (#768 → #779)

2026-10-02

Rank Moved

Rank dropped 22 spots (#752 → #774)

2026-09-30

Rank Moved

Rank dropped 11 spots (#733 → #744)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

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 283 spots (#398 → #681)

2026-09-23

HVTrust Changed

HVTrust up 10.9pts (47.1 → 58.0)

2026-09-22

Newly Listed

First tracked at rank #398

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-14

Rank Moved

Rank rose 21 spots (#689 → #668)

2026-09-09

Rank Moved

Rank dropped 11 spots (#651 → #662)

2026-09-07

Rank Moved

Rank dropped 48 spots (#595 → #643)

2026-09-05

Rank Moved

Rank dropped 73 spots (#522 → #595)

2026-09-04

Rank Moved

Rank dropped 21 spots (#501 → #522)

2026-09-03

Rank Moved

Rank dropped 50 spots (#451 → #501)

2026-09-01

Rank Moved

Rank dropped 12 spots (#431 → #443)

2026-08-30

Rank Moved

Rank rose 13 spots (#438 → #425)

2026-08-29

Rank Moved

Rank dropped 11 spots (#427 → #438)

2026-08-26

Scorecard Added

OSSF Scorecard: 5.7/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 478 spots (#893 → #415)

2026-08-26

HVTrust Changed

HVTrust up 34.1pts (23.6 → 57.7)

2026-08-23

Rank Moved

Rank rose 19 spots (#911 → #892)

2026-08-19

Rank Moved

Rank dropped 11 spots (#910 → #921)

2026-08-17

Rank Moved

Rank rose 10 spots (#919 → #909)

2026-08-16

Rank Moved

Rank dropped 37 spots (#882 → #919)

2026-08-15

Rank Moved

Rank dropped 16 spots (#866 → #882)

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-for-stata.svg)](https://hvtracker.net/agents/mcp-for-stata)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-for-stata"><img src="https://hvtracker.net/badge/mcp-for-stata.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

MCP For Stata

How MCP For Stata could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How MCP For Stata compares in MCP Servers

Where the 55.5 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about MCP For Stata

AI agent surface

Maintain MCP For Stata?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers