Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Unbrowse

NPM · UNBROWSE · 2 COMPONENTS

Websites as APIs: read pages, run site tasks via learned APIs, cloud browser with saved logins.

0 this week 54 Trust /100

Last scanned (13 hours ago)

Scores higher than 27% of npm servers

Category Browser Automation

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to unbrowse-ai/unbrowse). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright), so the captured schema is incomplete.Unverified
Stability & Change Management0
  • Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 4 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (10)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • MCP protocol

Checks we could not complete (4)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright), so the captured schema is incomplete.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 9 Nov 26 +5
    • Source repository: unverified → pass ▲ security
  • 8 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 21 Oct 26 0
    • Security disclosure: unverified → pass ▲ functional
  • 20 Oct 26 0
    • Security disclosure: pass → unverified ▼ functional
  • 16 Oct 26 0
    • Package version: 12.3.1 → 12.5.0 functional
  • 14 Oct 26 0
    • Tool safety: Tool safety not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright). security
    • Stability: Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all. security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright). functional
    • Schema quality: Schema quality not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright), so the captured schema is incomplete. functional
  • 12 Oct 26 0
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Package version: 12.1.1 → 12.3.1 functional
  • 28 Sept 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/unbrowse@12.5.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo unbrowse-ai/unbrowse
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/unbrowse-ai/unbrowse/.github/workflows/release.yml@refs/tags/v12.5.0
Rekor log index 3272684410
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:04899541b382085cf43b0725feebb981a38fd2eee3b1c95687a24d25de9063e0218bb3d84dac219e6f7fc7cd71be3dde525464888e6176c1e907e24b5

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

The sandbox run completed and this package exposed no tools.

Install

How do I install the Unbrowse MCP server?

Unbrowse runs locally as an npm package, launched with npx -y unbrowse mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · unbrowse

# add to Claude Code
claude mcp add unbrowse-ai-unbrowse -- npx -y unbrowse mcp
Common questions

What is the Unbrowse MCP server?

Unbrowse is an MCP server listed in the public MCP registry as io.github.unbrowse-ai/unbrowse. Websites as APIs: read pages, run site tasks via learned APIs, cloud browser with saved logins. This page covers its npm package (unbrowse).

Is the Unbrowse MCP server safe to use?

Unbrowse scores 54 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Unbrowse MCP server expose?

Unbrowse exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.

Is the Unbrowse MCP server still maintained?

Unbrowse is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Unbrowse MCP server under?

Unbrowse declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Unbrowse MCP server?

VerifyMCP ran 10 checks on Unbrowse, covering Malware scan, Known CVEs, Install scripts, Dependency health and 6 more. 4 items could not be completed, a gap on our side rather than a finding about Unbrowse: Schema quality, Stability, Tool coverage and Tool safety. 4 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.