Mobai MCP

MCP Servers TypeScript Listed Apache-2.0

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

OSSF Scorecard 2.0 / 10
Provenance None
Signed commits 0%
Last push 5d ago
Advisories None known
Compare Mobai MCP
Suggest a correction

In detail: Mobai MCP scores 50.8/100 (Grade C), ranked #986 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.0/10; recent commits are unsigned; no published advisory affects its latest release (mobai-mcp); last pushed 2026-10-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How Mobai MCP 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.

Chain of custody

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

    github.com/MobAI-App/mobai-mcp, Apache-2.0, last pushed 2026-10-13. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Weak

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

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 4
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 0
  3. Published packages Linked, not attested

    • npm mobai-mcp Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: mobai-mcp 2.9.0. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

  • 2026-08-27 OSSF Scorecard: 2.1/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 Mobai MCP’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.

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 Mobai MCP compares in MCP Servers

  1. #555 Mac Control MCP 50.8 ±0
  2. #556 Google Surf MCP 50.8 ±0
  3. #557 Mobai MCP 50.8 this agent
  4. #558 MCP NixOS 50.7 −0.1
  5. #559 Serpapi MCP 50.5 −0.3

Bars show each HVTrust score; the tick marks Mobai MCP’s 50.8.

Where the 50.8 comes from

HVTrust dimensions vs the MCP Servers average

50.8 / 100 · 100.0% confidence

Mobai MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.5 / 25
8.1 below avg 10.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.8 below avg 13.6
Transparency50% declared license · 50% OSSF Scorecard
10.2 / 17
2.1 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
12.6 / 20
in line with avg 12.2
AdoptionLog-scaled stars · package downloads
8.7 / 20
1.3 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-14
Rank Moved
Rank rose 36 spots (#999 → #963)
2026-10-14
Activity Score Changed
Activity score up 5pts (46 → 52)
2026-10-11
Rank Moved
Rank dropped 12 spots (#977 → #989)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.0/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.
50.9
Activity sub-score · out of 100
#557

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-10-18 00:07 UTC · Repo last pushed 5 days ago

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
252
Forks
20
Last Push
2026-10-13
5 days ago
Commits (4 wk)
2?
Downloads (7d)
151
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼2
was #984

Analysis

Activity Inputs

50.9 / 100
StarsRepository reach
14.4 / 30
FreshnessLast push recency
24.3 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
6.1 / 20

Common questions about Mobai MCP

Public trust evidence for Mobai MCP 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 Mobai MCP publish package provenance?
No published build provenance is currently detected for Mobai MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Mobai MCP have an OpenSSF Scorecard?
Mobai MCP has an OpenSSF Scorecard score of 2.0/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 Mobai MCP actively maintained?
Actively maintained. The repository was pushed to within the last 5 day(s).
What license does Mobai MCP use?
Mobai MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Mobai MCP's commits signed?
0% of the last 100 commits to Mobai MCP 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
Mobai MCP 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 Mobai MCP'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 Mobai MCP?

For maintainers

HVTrust scores Mobai MCP 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.

Reputation Timeline

Signal history
Rank 30HVTrust 3Listed 2Score 2Grade 2Scorecard 1Delisted 1MCP 1
2026-10-14
Rank Moved
Rank rose 36 spots (#999 → #963)
2026-10-14
Activity Score Changed
Activity score up 5pts (46 → 52)
2026-10-11
Rank Moved
Rank dropped 12 spots (#977 → #989)
2026-10-10
Rank Moved
Rank dropped 11 spots (#966 → #977)
2026-10-09
Rank Moved
Rank dropped 17 spots (#949 → #966)
2026-10-05
Rank Moved
Rank dropped 46 spots (#896 → #942)
2026-09-30
Rank Moved
Rank dropped 18 spots (#862 → #880)
2026-09-28
Rank Moved
Rank rose 24 spots (#880 → #856)
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 rose 168 spots (#1054 → #886)
2026-09-23
HVTrust Changed
HVTrust up 28.2pts (23.5 → 51.7)
2026-09-22
Newly Listed
First tracked at rank #1054
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank rose 30 spots (#880 → #850)
2026-09-13
Rank Moved
Rank rose 29 spots (#896 → #867)
2026-09-12
Rank Moved
Rank dropped 12 spots (#884 → #896)
2026-09-11
Rank Moved
Rank dropped 10 spots (#874 → #884)
2026-09-09
Rank Moved
Rank dropped 26 spots (#850 → #876)
2026-09-07
Grade Changed
Trust grade D → C
2026-09-07
Rank Moved
Rank rose 371 spots (#1214 → #843)
2026-09-07
HVTrust Changed
HVTrust up 17.4pts (34.1 → 51.5)
2026-09-06
Rank Moved
Rank dropped 14 spots (#1200 → #1214)
2026-09-05
Rank Moved
Rank dropped 35 spots (#1165 → #1200)
2026-09-04
Rank Moved
Rank rose 13 spots (#1178 → #1165)
2026-09-04
Activity Score Changed
Activity score up 8pts (41 → 49)
2026-09-03
Rank Moved
Rank dropped 42 spots (#1136 → #1178)
2026-09-02
Rank Moved
Rank dropped 46 spots (#1090 → #1136)
2026-09-01
Rank Moved
Rank dropped 40 spots (#1050 → #1090)
2026-08-31
Rank Moved
Rank dropped 33 spots (#1017 → #1050)
2026-08-30
Rank Moved
Rank dropped 56 spots (#961 → #1017)
2026-08-29
Rank Moved
Rank dropped 49 spots (#912 → #961)
2026-08-28
Rank Moved
Rank dropped 34 spots (#878 → #912)
2026-08-27
Scorecard Added
OSSF Scorecard: 2.1/10
2026-08-27
Rank Moved
Rank rose 243 spots (#1121 → #878)
2026-08-27
HVTrust Changed
HVTrust up 12.5pts (20.4 → 32.9)
2026-08-26
Rank Moved
Rank dropped 62 spots (#1059 → #1121)
2026-08-24
Rank Moved
Rank dropped 13 spots (#1045 → #1058)
2026-08-16
Rank Moved
Rank dropped 35 spots (#1022 → #1057)
2026-08-12
Rank Moved
Rank rose 16 spots (#1029 → #1013)
2026-08-10
Rank Moved
Rank dropped 58 spots (#960 → #1018)
2026-08-08
Newly Listed
First tracked at rank #954

Embed Badge Badge guide for maintainers →

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