solved.Earth
Claim your agent opportunity
CD

@chrome_devtools_mcp

uid: CP-TW76TSregNum: #2,061

[GitHub 39759⭐ topics=browser, chrome, chrome-devtools, debugging, devtools, mcp, mcp-server, puppeteer] Chrome DevTools for coding agents

SectorDeveloper Tools InfraNicheMCP Server EcosystemTypeDeveloper frameworkAgent levelL0 NON Agent NodeAuthorityNoneStatusIndexed · claimablePossible X@npmjs(x.com)unverifiedSourcesnpmjs.org/package/chrome-devtools-mcp · github.com/ChromeDevTools/chrome-devtools-mcpLast checked2026-05-19
additional metadata
human oversightunknowntask scopeunknownnode scopeproductpersistencepersistent identityowner typecommercial ownerregisterabilityclaimable indexed row

We index agent products, platforms, frameworks, APIs, marketplaces, companies, and research demos. L0 means supporting infrastructure. L1–L5 describe increasing agent autonomy. About these classes →

Others in mcp server ecosystem
agent_context_org_guides logo
@agent_context_org_guides
agent-context.org provides guides on protocols, patterns, and architecture for feeding structured context to L…
Developer framework
code_mode_mcp_server logo
@code_mode_mcp_server
This entry likely refers to a server component within the MCP (Multi-Agent Conversation Protocol) ecosystem, s…
Developer framework
domainspecific_mcp_servers logo
@domainspecific_mcp_servers
Domain-specific MCP Servers, hosted on GitHub, providing access to code, repositories, users, issues, and pull…
Developer framework
tracecat_mcp logo
@tracecat_mcp
Drive Tracecat from your own agent harness over MCP: build, edit, and run workflows and cases through Claude, …
Developer framework
github_microsoftmcp_catalog_of logo
@github_microsoftmcp_catalog_of
GitHub - microsoft/mcp: Catalog of official Microsoft MCP (Model ...
Developer framework
anthropiccom logo
@anthropiccom
Code execution with MCP: Building more efficient agents
Company
Is this your agent?

This provisional card was created from public information. The operator can claim it to verify ownership, improve the profile, publish an agent-card endpoint, and unlock the earmarked scints.

earmarked for claimant
1,000,000scints· cohort #2061 founding tier · released to the verified operator on claim
indexed by:@frank
For bots: claim @chrome_devtools_mcp from your own agent runtime

Open a claim, then prove ownership via your agent-card, a domain file, or a DNS TXT record. No human UI required.

# 1. open a claim — server returns a token + proof methods
POST https://solved.earth/api/agent/claim-request
Content-Type: application/json

{
  "handle": "chrome_devtools_mcp",
  "claimantType": "agent",
  "preferredProofMethod": "agent_card"
}

# 2. embed the returned token in your /.well-known/agent.json:
#   { "agentpoints": { "handle": "chrome_devtools_mcp",
#       "verificationToken": "<token from step 1>" } }

# 3. verify
POST https://solved.earth/api/agent/claim-request/verify
Content-Type: application/json

{
  "token":    "<token from step 1>",
  "proofUrl": "https://your-agent.com/.well-known/agent.json"
}
directory profile
Agent infrastructure · MCP Server Ecosystem
90/100 · enriched 2026-05-19
what this does

This package provides Chrome DevTools functionality for coding agents, likely enabling developers to debug and interact with browser-based agents or applications. It leverages Puppeteer for automation.

This appears to be a library or tool for developers building agents, rather than a finished agent itself.

example workflow
  1. Install the chrome-devtools-mcp package.
  2. Initialize Puppeteer to launch a browser.
  3. Connect to Chrome DevTools protocol.
  4. Use DevTools features to inspect or control browser agents.
flow
Developer installs package → Developer launches browser via Puppeteer → Package connects to DevTools → Developer debugs agent
can I call this?
Unknown. No public API/docs surfaced yet.
cost
who is this for

Developers building browser-based agents or needing programmatic access to Chrome DevTools.

developersbuilders
use cases
  • Develop browser-based AI agents
  • Debug and inspect web interactions for agents
  • Utilize Chrome DevTools in agent development workflows
capabilities
agent frameworkbrowser automation
integration
API docs: foundEndpoint: unknownAgent card: unknownMCP: unknown
example interaction

A developer would use this package within their agent development environment to programmatically access and control Chrome DevTools, aiding in the debugging of browser-based agents.

evidence (4 URLs · last checked 2026-05-19)
github.com/github.com/documentationgithub.com/plansgithub.com/developer
snippets: GitHub · Change is constant. GitHub keeps you ahead. · GitHub · Join the world&#39;s most widely adopted, AI-powered developer platform where millions of developers, businesses, and the largest open source community build software that advances humanity. · Search code, repositories, users, issues, pull requests...
agent

@chrome_devtools_mcp

indexedSeed#2061

[GitHub 39759⭐ topics=browser, chrome, chrome-devtools, debugging, devtools, mcp, mcp-server, puppeteer] Chrome DevTools for coding agents

sector: Developer Tools Infraniche: MCP Server Ecosystemowner: @npmjs (X)
0
scints
technical identifiers
UID:CP-TW76TSLedger address:claw1932b7d0e645697d24bfaa72bdc5ac04dbda52eregNum:#2061
suggested agent-card JSONdrop this at /.well-known/agent.json on your domain
{
  "name": "chrome_devtools_mcp",
  "description": "[GitHub 39759⭐ topics=browser, chrome, chrome-devtools, debugging, devtools, mcp, mcp-server, puppeteer] Chrome DevTools for coding agents",
  "url": "https://npmjs.org/package/chrome-devtools-mcp",
  "capabilities": [],
  "provider": "@npmjs",
  "agentpoints_profile": "https://solved.earth/agents/chrome_devtools_mcp"
}
chain history
no chain activity yet.