Is Mobile MCP safe to use?

Mobile MCP has an HVTrust score of 92.9/100 (Grade A), ranked #5 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Mobile MCP?

Mobile MCP scores 92.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 7.2k GitHub stars and is categorized under MCP Servers.

Mobile MCP

mobile-next/mobile-mcp

Model Context Protocol Server for Mobile Automation and Scraping (iOS, Android, Emulators, Simulators and Real Devices)

MCP Servers TypeScript Listed Apache-2.0

Is Mobile MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.6 / 10

Provenance Attested

Signed commits 100%

Last push 3d ago

Compare Mobile MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Mobile MCP scores 92.9/100 (Grade A), ranked #5 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 7.6/10; 100% of recent commits are signed; last pushed 2026-09-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How Mobile MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Mobile MCP’s 92.9.

Where the 92.9 comes from

HVTrust dimensions vs the MCP Servers average

92.9 / 100 · 100.0% confidence

Mobile MCP MCP Servers average (775 agents)

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

22.0 / 25

11.7 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

15.0 / 17

2.8 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

19.2 / 20

7.1 above avg 12.1

AdoptionLog-scaled stars · package downloads

15.6 / 20

8.4 above avg 7.2

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

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 → A

Maintainer Checklist

Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.

Compare with Codebase Memory MCP Get email alerts for Mobile MCP View MCP Servers Report missing data

84.0

Activity sub-score · out of 100

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 A 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

7.2k

Forks

635

Last Push

2026-09-23

3 days ago

Commits (4 wk)

Downloads (7d)

52,891

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #4

Analysis

Activity Inputs

84.0 / 100

StarsRepository reach

23.2 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

23.2 / 25

CommunityFork signal

13.0 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

7.6 / 10

OpenSSF Scorecard · scanned Sep 9, 2026 (refresh pending)

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 4

SAST 10

Security-Policy 10

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 10

Common questions about Mobile MCP

Public supply-chain signals for Mobile MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Mobile MCP carries less obvious unverified-evidence risk than projects with thin signals.

Does Mobile MCP publish package provenance?

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

Does Mobile MCP have an OpenSSF Scorecard?

Mobile MCP has an OpenSSF Scorecard score of 7.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 Mobile MCP actively maintained?

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

What license does Mobile MCP use?

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

Are Mobile MCP's commits signed?

100% of the last 100 commits to Mobile 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.

Compare Mobile MCP head-to-head

Mobile MCP vs Codebase Memory MCP → Mobile MCP vs Playwright MCP → Mobile MCP vs LinkedIn MCP Server →

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

Mobile 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 Mobile 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

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Mobile MCP?

For maintainers

HVTrust scores Mobile 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.

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 → A

2026-09-23

Rank Moved

Rank rose 552 spots (#556 → #4)

2026-09-23

HVTrust Changed

HVTrust up 56.4pts (36.5 → 92.9)

2026-09-22

Newly Listed

First tracked at rank #556

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-13

Grade Changed

Trust grade C → A

2026-09-13

Rank Moved

Rank rose 557 spots (#560 → #3)

2026-09-13

HVTrust Changed

HVTrust up 30.9pts (61.5 → 92.4)

2026-09-11

Rank Moved

Rank dropped 12 spots (#555 → #567)

2026-09-08

Rank Moved

Rank rose 14 spots (#576 → #562)

2026-09-07

Rank Moved

Rank dropped 38 spots (#538 → #576)

2026-09-06

Rank Moved

Rank dropped 10 spots (#528 → #538)

2026-09-05

Rank Moved

Rank dropped 69 spots (#459 → #528)

2026-09-03

Scorecard Added

OSSF Scorecard: 7.6/10

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 284 spots (#735 → #451)

2026-09-03

HVTrust Changed

HVTrust up 10.9pts (49.1 → 60.0)

2026-09-02

Rank Moved

Rank dropped 37 spots (#698 → #735)

2026-09-01

Rank Moved

Rank dropped 27 spots (#671 → #698)

2026-08-31

Rank Moved

Rank dropped 37 spots (#634 → #671)

2026-08-30

Rank Moved

Rank dropped 10 spots (#624 → #634)

2026-08-29

Rank Moved

Rank dropped 39 spots (#585 → #624)

2026-08-28

Rank Moved

Rank dropped 19 spots (#566 → #585)

2026-08-27

Rank Moved

Rank dropped 15 spots (#551 → #566)

2026-08-26

Rank Moved

Rank dropped 71 spots (#480 → #551)

2026-08-24

Rank Moved

Rank dropped 15 spots (#464 → #479)

2026-08-22

Rank Moved

Rank rose 14 spots (#480 → #466)

2026-08-19

Rank Moved

Rank dropped 12 spots (#467 → #479)

2026-08-17

Rank Moved

Rank rose 13 spots (#489 → #476)

2026-08-16

Rank Moved

Rank dropped 10 spots (#479 → #489)

2026-08-13

Rank Moved

Rank dropped 15 spots (#462 → #477)

2026-08-12

Rank Moved

Rank rose 15 spots (#477 → #462)

2026-08-10

Rank Moved

Rank dropped 23 spots (#450 → #473)

2026-08-08

Newly Listed

First tracked at rank #445

GitHub → npm: @mobilenext/mobile-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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