Is MCP Baepsae safe to use?

MCP Baepsae has an HVTrust score of 54.2/100 (Grade C), ranked #812 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 Baepsae?

MCP Baepsae scores 54.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 26 GitHub stars and is categorized under MCP Servers.

MCP Baepsae

oozoofrog/mcp-baepsae

MCP server with direct iOS simulator implementation

MCP Servers JavaScript Listed MIT

Is MCP Baepsae safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.2 / 10

Provenance Attested

Signed commits 37%

Last push 179d ago

Compare MCP Baepsae

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Baepsae scores 54.2/100 (Grade C), ranked #812 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 3.2/10; 37% of recent commits are signed; last pushed 2026-03-31. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Baepsae compares in MCP Servers

Bars show each HVTrust score; the tick marks MCP Baepsae’s 54.2.

Where the 54.2 comes from

HVTrust dimensions vs the MCP Servers average

54.2 / 100 · 100.0% confidence

MCP Baepsae MCP Servers average (775 agents)

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

13.3 / 25

3.0 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

11.2 / 17

1.0 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

0.1 / 20

12.0 below avg 12.1

AdoptionLog-scaled stars · package downloads

5.6 / 20

1.6 below avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

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

Maintainer Checklist

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

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

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

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

11.1

Activity sub-score · out of 100

#456

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-03-31

179 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #814

Analysis

Activity Inputs

11.1 / 100

StarsRepository reach

8.6 / 30

FreshnessLast push recency

0.1 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

2.2 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

3.2 / 10

OpenSSF Scorecard · scanned Sep 26, 2026

Signed Commits

37%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 9

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 4

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about MCP Baepsae

Public trust evidence for MCP Baepsae is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does MCP Baepsae publish package provenance?

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

Does MCP Baepsae have an OpenSSF Scorecard?

MCP Baepsae has an OpenSSF Scorecard score of 3.2/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 Baepsae actively maintained?

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

What license does MCP Baepsae use?

MCP Baepsae ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Baepsae's commits signed?

37% of the last 100 commits to MCP Baepsae 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 Baepsae 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

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

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 Baepsae'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

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain MCP Baepsae?

For maintainers

HVTrust scores MCP Baepsae 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-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 473 spots (#1277 → #804)

2026-09-23

HVTrust Changed

HVTrust up 40.3pts (14.1 → 54.4)

2026-09-22

Newly Listed

First tracked at rank #1277

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-10

Rank Moved

Rank dropped 26 spots (#745 → #771)

2026-09-09

Rank Moved

Rank dropped 15 spots (#730 → #745)

2026-09-07

Grade Changed

Trust grade D → C

2026-09-07

Rank Moved

Rank rose 433 spots (#1154 → #721)

2026-09-07

HVTrust Changed

HVTrust up 18.1pts (37.5 → 55.6)

2026-09-06

Rank Moved

Rank dropped 16 spots (#1138 → #1154)

2026-09-05

Rank Moved

Rank dropped 35 spots (#1103 → #1138)

2026-09-04

Rank Moved

Rank dropped 22 spots (#1081 → #1103)

2026-09-03

Rank Moved

Rank dropped 56 spots (#1025 → #1081)

2026-09-02

Rank Moved

Rank dropped 43 spots (#982 → #1025)

2026-09-01

Rank Moved

Rank dropped 43 spots (#939 → #982)

2026-08-31

Rank Moved

Rank dropped 34 spots (#905 → #939)

2026-08-30

Rank Moved

Rank dropped 41 spots (#864 → #905)

2026-08-29

Scorecard Added

OSSF Scorecard: 3.2/10

2026-08-29

Rank Moved

Rank rose 40 spots (#904 → #864)

2026-08-29

HVTrust Changed

HVTrust up 4.4pts (33.5 → 37.9)

2026-08-28

Rank Moved

Rank dropped 33 spots (#871 → #904)

2026-08-27

Rank Moved

Rank dropped 24 spots (#847 → #871)

2026-08-26

Rank Moved

Rank dropped 108 spots (#739 → #847)

2026-08-16

Rank Moved

Rank dropped 15 spots (#715 → #730)

2026-08-10

Rank Moved

Rank dropped 37 spots (#677 → #714)

2026-08-08

Newly Listed

First tracked at rank #676

GitHub → npm: mcp-baepsae

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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