Is Agent360 Browser MCP safe to use?

Agent360 Browser MCP has an HVTrust score of 61.9/100 (Grade C), ranked #577 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Agent360 Browser MCP?

Agent360 Browser MCP scores 61.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 46 GitHub stars and is categorized under MCP Servers.

Agent360 Browser MCP

Agent360dk/browser-mcp

The browser tool that can stop and ask you. A 2FA code, a CAPTCHA, a choice only you can make: it asks on your screen, then carries on in the tab you were already signed into. 40 tools, any MCP client, MIT.

MCP Servers JavaScript Listed MIT

Is Agent360 Browser MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.3 / 10

Provenance None

Signed commits 3%

Last push yesterday

Compare Agent360 Browser MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Agent360 Browser MCP scores 61.9/100 (Grade C), ranked #577 of 1325 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 4.3/10; 3% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Agent360 Browser MCP compares in MCP Servers

#325 Apollo MCP Server 61.9 ±0
#326 Porkbun DNS 🐷 61.9 ±0
#327 Agent360 Browser MCP 61.9 this agent
#328 Bagel 61.8 −0.1
#329 Studio MCP 61.8 −0.1

Bars show each HVTrust score; the tick marks Agent360 Browser MCP’s 61.9.

Where the 61.9 comes from

HVTrust dimensions vs the MCP Servers average

61.9 / 100 · 100.0% confidence

Agent360 Browser MCP MCP Servers average (775 agents)

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

5.5 / 25

4.8 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

7.8 above avg 12.1

AdoptionLog-scaled stars · package downloads

8.5 / 20

1.3 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.3/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.

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

65.5

Activity sub-score · out of 100

#327

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-09-25

yesterday

Commits (4 wk)

333

Downloads (7d)

2,194

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #574

Analysis

Activity Inputs

65.5 / 100

StarsRepository reach

10.0 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

5.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.3 / 10

OpenSSF Scorecard · scanned Sep 22, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about Agent360 Browser MCP

Agent360 Browser MCP 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 Agent360 Browser MCP publish package provenance?

No published build provenance is currently detected for Agent360 Browser 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 Agent360 Browser MCP have an OpenSSF Scorecard?

Agent360 Browser MCP has an OpenSSF Scorecard score of 4.3/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 Agent360 Browser MCP actively maintained?

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

What license does Agent360 Browser MCP use?

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

Are Agent360 Browser MCP's commits signed?

3% of the last 100 commits to Agent360 Browser 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

Agent360 Browser MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Google Gemini

Credential signal: API keys or service config markers documented.

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 Agent360 Browser 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

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-19

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-08-12

Provider Removed

Runtime surface shrank — no longer detected: Anthropic

Maintain Agent360 Browser MCP?

For maintainers

HVTrust scores Agent360 Browser 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

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

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 205 spots (#779 → #574)

2026-09-23

HVTrust Changed

HVTrust up 32.6pts (29.3 → 61.9)

2026-09-22

Newly Listed

First tracked at rank #779

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank rose 66 spots (#629 → #563)

2026-09-19

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-19

Rank Moved

Rank rose 29 spots (#658 → #629)

2026-09-11

Rank Moved

Rank dropped 13 spots (#639 → #652)

2026-09-08

Rank Moved

Rank rose 11 spots (#641 → #630)

2026-09-06

Rank Moved

Rank dropped 14 spots (#618 → #632)

2026-09-05

Rank Moved

Rank dropped 74 spots (#544 → #618)

2026-09-04

Rank Moved

Rank dropped 26 spots (#518 → #544)

2026-09-03

Rank Moved

Rank dropped 24 spots (#494 → #518)

2026-09-02

Rank Moved

Rank dropped 18 spots (#476 → #494)

2026-08-31

Rank Moved

Rank dropped 26 spots (#445 → #471)

2026-08-30

Rank Moved

Rank rose 14 spots (#459 → #445)

2026-08-29

Rank Moved

Rank dropped 18 spots (#441 → #459)

2026-08-28

Rank Moved

Rank dropped 11 spots (#430 → #441)

2026-08-27

Rank Moved

Rank rose 35 spots (#465 → #430)

2026-08-27

Activity Score Changed

Activity score up 7pts (53 → 60)

2026-08-26

Scorecard Added

OSSF Scorecard: 2.9/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 254 spots (#719 → #465)

2026-08-26

HVTrust Changed

HVTrust up 20.3pts (34.8 → 55.1)

2026-08-23

Rank Moved

Rank dropped 13 spots (#702 → #715)

2026-08-17

Rank Moved

Rank rose 17 spots (#711 → #694)

2026-08-16

Rank Moved

Rank dropped 16 spots (#695 → #711)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-08-12

Provider Removed

Runtime surface shrank — no longer detected: Anthropic

2026-08-12

Rank Moved

Rank rose 15 spots (#703 → #688)

2026-08-10

Rank Moved

Rank dropped 36 spots (#666 → #702)

2026-08-08

Newly Listed

First tracked at rank #661

GitHub → npm: @agent360/browser-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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