updated 2026-10-16 20:06 UTC

Native DevTools

Repository

MCP server for computer use & browser automation - screenshot, OCR, click, type, find_text, Chrome/Electron CDP, template matching. macOS, Windows & Android. Works with Claude, Cursor, and any MCP client.

MCP Servers Rust Listed MIT

Is Native DevTools safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.2 / 10
Provenance Attested
Signed commits 100%
Last push 22d ago
Compare Native DevTools

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Native DevTools scores 74.6/100 (Grade B), ranked #262 of 1378 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 4.2/10; 100% of recent commits are signed; last pushed 2026-09-24. Every point is earned from checkable signals — never paid placement. How scoring works →

How Native DevTools 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 Native DevTools 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 Signed

    github.com/vectora-foundry/native-devtools-mcp, MIT, last pushed 2026-09-24. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

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

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 1

  3. Published packages Partly attested

    • npm native-devtools-mcp Source link points to this repo's current name Build provenance attested

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-30 OSSF Scorecard: 3.5/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 Native DevTools’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 Native DevTools compares in MCP Servers

  1. #148 MCP FreeScout 74.7 +0.1
  2. #149 MCP AutoMem 74.7 +0.1
  3. #150 Native DevTools 74.6 this agent
  4. #151 reMarkable MCP Server 74.4 −0.2
  5. #152 Zigbee2MQTT MCP 74.4 −0.2

Bars show each HVTrust score; the tick marks Native DevTools’s 74.6.

Where the 74.6 comes from

HVTrust dimensions vs the MCP Servers average

74.6 / 100 · 100.0% confidence

Native DevTools MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.8 / 25
7.3 above avg 10.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.5 above avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
12.1 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
17.1 / 20
4.8 above avg 12.3
AdoptionLog-scaled stars · package downloads
7.6 / 20
in line with avg 7.4

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-10-16
Rank Moved
Rank dropped 17 spots (#245 → #262)
2026-10-09
Rank Moved
Rank dropped 10 spots (#222 → #232)
2026-10-03
Grade Changed
Trust grade A → B
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.2/10. Tighten the weakest checks to improve public safety evidence.
Compare with another agent Get email alerts for Native DevTools View MCP Servers Report missing data
61.0
Activity sub-score · out of 100
#150
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 B 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-16 20:06 UTC · Repo last pushed 22 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
138
Forks
17
Last Push
2026-09-24
22 days ago
Commits (4 wk)
42
Downloads (7d)
74
npm
HN mentions (30d)
—
Open Issues
2
Rank Change
▼17
was #245

Analysis

Activity Inputs

61.0 / 100
StarsRepository reach
12.9 / 30
FreshnessLast push recency
21.9 / 25
ActivityRecent commits
20.4 / 25
CommunityFork signal
5.8 / 20

Common questions about Native DevTools

Native DevTools 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 Native DevTools publish package provenance?
Yes. Native DevTools's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Native DevTools have an OpenSSF Scorecard?
Native DevTools has an OpenSSF Scorecard score of 4.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 Native DevTools actively maintained?
Maintained. Last push was 22 days ago.
What license does Native DevTools use?
Native DevTools ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Native DevTools's commits signed?
100% of the last 100 commits to Native DevTools 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
medium confidence
Implemented
Native DevTools 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
low confidence
Unknown
Package source metadata is missing or inconclusive
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 Native DevTools'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-24
Activity Resumed
Activity resumed
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-08-29
Activity Went Stale
No commits for 90 days

Maintain Native DevTools?

For maintainers

HVTrust scores Native DevTools 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 24Grade 6HVTrust 5Listed 2Stale 1Scorecard 1Delisted 1Provenance 1MCP 1Score 1Fresh 1
2026-10-16
Rank Moved
Rank dropped 17 spots (#245 → #262)
2026-10-09
Rank Moved
Rank dropped 10 spots (#222 → #232)
2026-10-03
Grade Changed
Trust grade A → B
2026-10-03
Rank Moved
Rank dropped 59 spots (#153 → #212)
2026-10-03
HVTrust Changed
HVTrust down 4.1pts (80.0 → 75.9)
2026-09-27
Grade Changed
Trust grade B → A
2026-09-27
Rank Moved
Rank rose 36 spots (#175 → #139)
2026-09-24
Activity Resumed
Activity resumed
2026-09-24
Grade Changed
Trust grade C → B
2026-09-24
Rank Moved
Rank rose 336 spots (#513 → #177)
2026-09-24
HVTrust Changed
HVTrust up 14.0pts (63.8 → 77.8)
2026-09-24
Activity Score Changed
Activity score up 36pts (28 → 64)
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 702 spots (#1215 → #513)
2026-09-23
HVTrust Changed
HVTrust up 45.8pts (18.0 → 63.8)
2026-09-22
Newly Listed
First tracked at rank #1215
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank dropped 29 spots (#460 → #489)
2026-09-17
Grade Changed
Trust grade B → C
2026-09-11
Rank Moved
Rank dropped 10 spots (#443 → #453)
2026-09-10
Rank Moved
Rank dropped 17 spots (#426 → #443)
2026-09-07
Rank Moved
Rank dropped 38 spots (#375 → #413)
2026-09-06
Grade Changed
Trust grade D → B
2026-09-06
Rank Moved
Rank rose 623 spots (#998 → #375)
2026-09-06
HVTrust Changed
HVTrust up 22.0pts (44.0 → 66.0)
2026-09-05
Rank Moved
Rank dropped 49 spots (#949 → #998)
2026-09-04
Rank Moved
Rank dropped 30 spots (#919 → #949)
2026-09-03
Rank Moved
Rank dropped 46 spots (#873 → #919)
2026-09-02
Rank Moved
Rank dropped 49 spots (#824 → #873)
2026-09-01
Rank Moved
Rank dropped 30 spots (#794 → #824)
2026-08-31
Rank Moved
Rank dropped 34 spots (#760 → #794)
2026-08-30
Scorecard Added
OSSF Scorecard: 3.5/10
2026-08-30
Rank Moved
Rank rose 80 spots (#840 → #760)
2026-08-30
HVTrust Changed
HVTrust up 4.9pts (39.4 → 44.3)
2026-08-29
Activity Went Stale
No commits for 90 days
2026-08-29
Rank Moved
Rank dropped 45 spots (#795 → #840)
2026-08-28
Rank Moved
Rank dropped 23 spots (#772 → #795)
2026-08-27
Rank Moved
Rank dropped 24 spots (#748 → #772)
2026-08-26
Rank Moved
Rank dropped 102 spots (#646 → #748)
2026-08-16
Rank Moved
Rank dropped 10 spots (#626 → #636)
2026-08-10
Rank Moved
Rank dropped 21 spots (#598 → #619)
2026-08-08
Newly Listed
First tracked at rank #595
GitHub → npm: native-devtools-mcp

Embed Badge Badge guide for maintainers →

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