Voyager Browser MCP server
Voyager's web-page sense: safe read-only observation of one live URL (structure, security, a11y).
0 stars60 downloads/wk
Reviews
Write oneNobody has reviewed Voyager Browser yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Voyager Browser tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
observe_pageRead-only observation of ONE live web page: title/structure, forms (with insecure/cross-origin/sensitive flags), links (external + unsafe target=_blank), script origins, security posture (HTTPS/HSTS/CSP/mixed-content/cookies incl. SameSite/CSRF + CORS wildcard & the dangerous reflected-origin+credentials combo) and accessibility signals (lang, img alt coverage, heading order) → findings with DESCR
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
- Code scan25 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 67 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
How Voyager Browser compares
Against every graded Scraping and browsing MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 65% of 866 Scraping and browsing servers
- Tools
- 1
- the typical Scraping and browsing server has 6
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 60
- more than 42% of 309 Scraping and browsing servers with a package
What its tools let an agent do: 1 read
Install Voyager Browser in Claude Code, Cursor or VS Code
Runs npx -y @dir-ai/voyager-browser on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add voyager-browser -- npx -y @dir-ai/voyager-browser
What the publisher says
From the Voyager Browser repository's README, as published. We do not edit it. Read it on GitHub
@dir-ai/voyager-browser
Voyager's web-page sense. A safe, read-only observation of one live URL: its structure, forms, links, script origins, security posture (HTTPS / HSTS / CSP / mixed-content / cookies) and accessibility signals (lang, image alt coverage, heading order) — each with a described, never applied fix.
It parses static HTML — no JavaScript execution, no headless browser — so it's honest about what it can and cannot see (it will not render a client-side SPA's runtime state). Every piece of page text is returned framed as untrusted. It is SSRF-gated: it refuses non-http(s) URLs and anything resolving to private, loopback, or cloud-metadata addresses.
One sense in the Voyager family. Read-only, like all the
senses — it never submits a form, clicks, or mutates anything.
Install
npm i -g @dir-ai/voyager-browserUse
voyager-browser observe https://example.com
voyager-browser observe https://example.com --jsonhttps://example.com/
https://example.com — 200; 3 finding(s), worst: medium. 0 form(s), 1 link(s).
title: Example Domain
security: https · a11y lang:yes alt:n/a
med HTTPS without HSTS
↳ add Strict-Transport-Security: max-age=63072000; includeSubDomains
med no Content-Security-Policy
↳ add a Content-Security-Policy to constrain scripts/resources
low no X-Content-Type-Options: nosniff
↳ add X-Content-Type-Options: nosniffAs an MCP server
One tool, observe_page.
{ "command": "voyager-browser", "args": ["mcp"] }As a library
import { observe } from '@dir-ai/voyager-browser'
const brief = await observe('https://example.com')
console.log(brief.summary)
console.log(brief.security) // { https, hsts, csp, mixedContent, thirdPartyScripts, … }
console.log(brief.forms) // insecure / cross-origin / sensitive flags
console.log(brief.findings) // severity + described fixWhat it looks for
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Voyager Browser: common questions
- Is Voyager Browser MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the Voyager Browser safety report
- How do I install Voyager Browser?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Voyager Browser need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Voyager Browser maintained?
- The last commit was 107 days ago (2026-07-20). The latest release is v0.7.0.
- What can I use instead of Voyager Browser?
- Servers from other publishers that do the same job: AIHawk MCP server, One Search MCP server and Browser MCP server.
- How does Voyager Browser compare with other Scraping and browsing MCP servers?
- safety score 85/100 (higher than 65% of 866 Scraping and browsing servers); tools 1 (the typical Scraping and browsing server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Voyager Browser
Same job from other publishers: the closest match first, then the best rated.
- AIHawkAI browser agent: browses, clicks, types, and reads real web pages from plain-English instructions.not reviewedWidely usedA
- One SearchWeb search, URL discovery, scraping & extraction with agent-browser and search providersnot reviewedGrowingB
- BrowserMCP server for loading authenticated web pages using Chrome DevTools Protocolnot reviewedGrowingA
unbrowser by UnchainedChrome-free MCP web access for agents with low-token page maps and browser escalation hints.not reviewedGrowingB- SeleniumBase MCPStealthy browser automation, testing, and web-scraping via CDP Mode.not reviewedWidely usedA
