Atlas / MCP servers / hanzili / Comet

CometCAUTION

mcp/hanzili/comet-1

MCP Server connecting to Perplexity Comet browser

Verdict
CAUTION
Grade
B
Trust score
89 /100
Exposed tools
6 4r · 2w · 0d
Transport
stdio
License
MIT
Stars
180
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

[](https://www.npmjs.com/package/comet-mcp)

Give Claude Code a browser that thinks.

An MCP server that connects Claude Code to Perplexity Comet - enabling agentic web browsing, deep research, and real-time task monitoring.

Why?

Existing web tools for Claude Code fall into two categories, both with limitations:

1. Search APIs (Tavily, Perplexity API, WebFetch)

Return static text. No interaction, no login, no dynamic content. Great for quick lookups, but can't navigate complex sites or fill forms.

2. Browser Automation (browser-use, Puppeteer MCP, Playwright MCP)

Can interact with pages, but use a one-agent-do-all approach: the same reasoning model that's writing your code is also deciding where to click, what to type, and how to navigate. This overwhelms the context window and fragments focus.

3. Comet MCP: Multi-Agent Delegation

Comet MCP takes a different approach. Instead of Claude controlling a browser directly, it delegates to Perplexity Comet - an AI purpose-built for web research and browsing.

  • Claude stays focused on your coding task
  • Comet handles the browsing: navigation, login walls, dynamic content, deep research
  • Result: Claude's coding intelligence + Perplexity's web intelligence, working together

Quick Start

1. Configure Claude Code

Add to ~/.claude.json or .mcp.json:

{
"mcpServers": {
"comet-bridge": {
"command": "npx",
"args": ["-y", "comet-mcp"]
}
}
}

2. Install Comet Browser

Download and install Perplexity Comet.

That's it! The MCP server automatically launches Comet with remote debugging when

Read from source at commit f88b87222ec2OBSERVED · 2026-10-06
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code
claude mcp add comet-mcp -- npx -y [email protected]
claude-desktop
{
  "mcpServers": {
    "comet-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ]
    }
  }
}
03

Exposed tools (6)

4 read · 2 write · 0 destructive.

ToolRiskDescription
comet_askwriteSend a prompt to Comet/Perplexity and wait for the complete response (blocking). Ideal for tasks requiring real browser interaction (login walls, dynamic content, filling forms) or deep research with agentic browsing.
comet_connectreadConnect to Comet browser (auto-starts if needed)
comet_modereadSwitch Perplexity search mode. Modes:
comet_pollreadCheck agent status and progress. Call repeatedly to monitor agentic tasks.
comet_screenshotreadCapture a screenshot of current page
comet_stopwriteStop the current agent task if it
04

Trust audit

CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeWARN
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
declared (9 observation(s))
Shell
declared (3 observation(s))
Dependencies
not all pinned
Secrets in source
none-found

Findings (7)

MEDIUMNetwork egress · net.raw_ip · CWE-200, CWE-319
src/cdp-client.ts:391
const response = await windowsFetch(`http://127.0.0.1:${port}/json/version`);
MEDIUMNetwork egress · net.raw_ip · CWE-200, CWE-319
src/cdp-client.ts:427
const response = await windowsFetch(`http://127.0.0.1:${port}/json/version`);
MEDIUMNetwork egress · net.raw_ip · CWE-200, CWE-319
src/cdp-client.ts:458
const response = await windowsFetch(`http://127.0.0.1:${port}/json/version`);
MEDIUMNetwork egress · net.raw_ip · CWE-200, CWE-319
src/cdp-client.ts:484
const response = await windowsFetch(`http://127.0.0.1:${port}/json/version`);
MEDIUMNetwork egress · net.raw_ip · CWE-200, CWE-319
src/cdp-client.ts:561
const response = await windowsFetch(`http://127.0.0.1:${this.state.port}/json/version`);
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
@modelcontextprotocol/sdk, chrome-remote-interface, @types/chrome-remote-interface, @types/node, typescript
Why it matters. 5 dependency range(s) float
Fix. pin exact versions or ship a lockfile
INFOInventory / provenance · inv.oversize · CWE-1104
demo.gif
demo.gif
Why it matters. 43072068 bytes not read

Gates applied: no_behavioural_pass.

Audited 2026-10-06 · audit v0.4.1 · source sha f88b87222ec2full audit observations/trust-audit/mcp-server/hanzili__comet-1.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-06f88b87222ec2CAUTIONB89first audit
06

Questions

What is the Comet MCP server?

MCP Server connecting to Perplexity Comet browser

What tools does Comet expose?

6 in total: 4 read-only, 2 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Comet safe to connect to an agent?

With care. The audit graded it B (89/100) and found 7 things worth knowing before you trust this server, listed below with the exact line each was found on.

What credentials does Comet need?

No credential environment variables were found in its source, so it appears to need none.

How does Comet run?

It speaks stdio, so it runs as a local process your client starts. It is published on npm as comet-mcp at 2.3.0.

How current is this page?

The grade is for one exact copy of the source (f88b87222ec2), read on 2026-10-06. The repository is watched and re-audited when it changes.

Advertisement