Developer · Remote MCP server
Chromedevtoolsmcp MCP
A paid remote MCP for AI agent browser DevTools MCP, built to return verdicts, receipts, usage logs,.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.clauxel.chromedevtoolsmcp/chromedevtoolsmcp-mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-05-25
- Updated
- 2026-05-25
- Publisher
- com.clauxel.chromedevtoolsmcp
- Namespace
- Namespace verified by the MCP Registry via the domain chromedevtoolsmcp.clauxel.com or a parent domain of it · how
- Listed under
- Browser automation MCP servers
- Repository
- github.com/clauxel/chrome-devtools-session-mcp-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://chromedevtoolsmcp.clauxel.com/mcp | Authorization |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- No - could not connect (DNS or connection failure)
- Handshake
- -
- Checked on
- 2026-10-05
How to connect Chromedevtoolsmcp MCP
Chromedevtoolsmcp MCP is a remote MCP server: there is nothing to install. Its endpoint is https://chromedevtoolsmcp.clauxel.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization. Clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| ChipzenAI poker arena for agents. Play rated poker on chipzen.ai against LLM bots and human-built bots. | Local · stdio |
| ChirpStackManage and live-debug LoRaWAN devices on a ChirpStack v4 network server over its gRPC API. | Local · stdio |
| ChromaDB Remote MCP ServerRemote ChromaDB vector database MCP server with streamable HTTP transport. | Remote & Local · HTTPLive check: ✗ no handshake |
| Chrome Debugger MCPChrome breakpoint debugging MCP server for inspecting runtime values and stepping through code. | Local · stdio |
| Chromium BridgeMCP bridge between Chromium browsers (Arc, Vivaldi, Brave) and Claude Code: browser automation. | Local · stdio |
| ChronTimestamped audit log for every AI conversation - stored locally in SQLite, owned by you. | Local · stdio |
| Chronicle MCPLocal MCP server to sync, clean, and index AI chat logs locally. Saves up to 40% context tokens. | Local · stdio |
| Ci SentinelMulti-CI security scanner with a live threat-intel feed of compromised CI components. | Remote · HTTPLive check: ✗ no handshake |