updated 2026-11-10 04:07 UTC

MCP Baepsae

Repository

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 224d ago
Advisories None known
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.4/100 (Grade C), ranked #870 of 1374 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; no published advisory affects its latest release (mcp-baepsae); last pushed 2026-03-31. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Baepsae 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

Chain of custody

Scanners check what the code says. This traces who ships MCP Baepsae 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 Partly signed

    github.com/oozoofrog/mcp-baepsae, MIT, last pushed 2026-03-31. 37% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

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

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies4
    All 18 Scorecard checks
    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

  3. Published packages Linked and attested

    • npm mcp-baepsae Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: mcp-baepsae 6.3.0. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-29 OSSF Scorecard: 3.2/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 Baepsae’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 Baepsae compares in MCP Servers

  1. #480 PostgreSQL MCP Server 54.5 +0.1
  2. #481 MCP 1c Platform Tools 54.4 ±0
  3. #482 MCP Baepsae 54.4 this agent
  4. #483 Akshare One MCP 54.3 −0.1
  5. #484 Fanout MCP 54.3 −0.1

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

Where the 54.4 comes from

HVTrust dimensions vs the MCP Servers average

54.4 / 100 · 100.0% confidence

MCP Baepsae MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.3 / 25
2.5 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
11.2 / 17
1.1 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.2 below avg 12.2
AdoptionLog-scaled stars · package downloads
5.9 / 20
1.7 below avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-11-08
Rank Moved
Rank dropped 13 spots (#858 → #871)
2026-10-27
Rank Moved
Rank rose 26 spots (#885 → #859)
2026-10-18
Rank Moved
Rank dropped 15 spots (#866 → #881)
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 224 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
11.4
Activity sub-score · out of 100
#482
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-10 04:07 UTC · Repo last pushed 224 days ago — may be stale

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
26
Forks
3
Last Push
2026-03-31
224 days ago
Commits (4 wk)
0
Downloads (7d)
72
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▲2
was #872

Analysis

Activity Inputs

11.4 / 100
StarsRepository reach
8.6 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
2.8 / 20

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?
Stale. The repository has not been pushed to in 224 days. Consider whether the project is still being maintained.
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
Rank 21HVTrust 3Grade 2Scorecard 1Delisted 1Listed 1Provenance 1MCP 1
2026-11-08
Rank Moved
Rank dropped 13 spots (#858 → #871)
2026-10-27
Rank Moved
Rank rose 26 spots (#885 → #859)
2026-10-18
Rank Moved
Rank dropped 15 spots (#866 → #881)
2026-10-14
Rank Moved
Rank dropped 13 spots (#844 → #857)
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)
GitHub → npm: mcp-baepsae

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.4 Grade C
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.4 · Raw JSON