pulsemcp verified Safe content atomic mcp-remote

Chrome Browser Automation

This MCP server provides AI assistants with comprehensive browser automation and semantic search capabilities through Chrome extension integration, built by hangye using TypeScript with a monorepo architecture spanning native messaging, WebAssembly optimization, and Vue.js interfaces. The implementation offers advanced browser tools including intelligent element clicking, form filling, screenshot capture, keyboard simulation, and navigation utilities, combined with a vector search engine featuring AI-powered content indexing, semantic similarity matching using transformer models with ONNX runtime, and multi-language text processing capabilities. Built with Chrome Native Messaging for cross-platform communication, SIMD-accelerated WebAssembly for performance optimization, and comprehensive model caching with conditional initialization, it serves developers building AI-driven web automation workflows, teams requiring semantic search across browser content, and applications needing programmatic web interaction with intelligent element detection and content analysis capabilities.

Cognium trust score

86%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: browser-automation
Source: PulseMCP
Repository: github.com/hangwin/mcp-chrome
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve Chrome Browser Automation from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"