chrome-devtools-mcp-adspower — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited chrome-devtools-mcp-adspower (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Connect Google's Chrome DevTools MCP to AdsPower antidetect browser profiles. This lets AI coding agents (Claude Code, Cursor, Codex CLI) control fingerprint-isolated browser sessions through natural language.
Claude Code → Chrome DevTools MCP → AdsPower Profile (unique fingerprint + proxy)
→ AdsPower Profile (unique fingerprint + proxy)
→ AdsPower Profile (unique fingerprint + proxy)AdsPower's Local API opens browser profiles and exposes a Chrome DevTools Protocol (CDP) endpoint for each one. Chrome DevTools MCP connects to that endpoint via --browserUrl.
npm install -g chrome-devtools-mcp@latest)requests installedimport requests
API_KEY = "your_api_key"
BASE_URL = "http://local.adspower.net:50325"
HEADERS = {"Authorization": f"Bearer {API_KEY}"}
PROFILE_ID = "your_profile_id"
# Open the browser profile
resp = requests.get(
f"{BASE_URL}/api/v1/browser/start?user_id={PROFILE_ID}",
headers=HEADERS,
timeout=30,
).json()
if resp["code"] == 0:
# This is the CDP WebSocket endpoint
ws_endpoint = resp["data"]["ws"]["puppeteer"]
debug_port = ws_endpoint.split(":")[2].split("/")[0]
print(f"CDP WebSocket: {ws_endpoint}")
print(f"Debug port: {debug_port}")
else:
print(f"Error: {resp['msg']}")The ws_endpoint looks like: ws://127.0.0.1:XXXXX/devtools/browser/GUID
Once the profile is open and you have the debug port, connect Chrome DevTools MCP:
# Connect to the AdsPower browser instance
npx chrome-devtools-mcp@latest --browserUrl=http://127.0.0.1:XXXXXReplace XXXXX with the actual port from Step 1.
Add to your MCP config (.claude/mcp.json or settings.json):
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest",
"--browserUrl=http://127.0.0.1:XXXXX"
]
}
}
}Once connected, you can tell your AI agent:
> Navigate to amazon.com and check if the account is still logged in
> Take a screenshot of the current page
> Check the network requests for any blocked or failed calls
> Run document.title in the browser console and tell me what page this is
> Inspect the fingerprint by visiting browserscan.netThe AI agent sees the browser through Chrome DevTools MCP, while AdsPower ensures the browser has a unique fingerprint and proxy.
To work across multiple AdsPower profiles sequentially:
import requests
import subprocess
import time
API_KEY = "your_api_key"
BASE_URL = "http://local.adspower.net:50325"
HEADERS = {"Authorization": f"Bearer {API_KEY}"}
def get_profiles(group_name):
resp = requests.get(
f"{BASE_URL}/api/v1/user/list",
headers=HEADERS,
params={"group_name": group_name, "page": 1, "page_size": 100},
).json()
return resp["data"]["list"]
def open_profile(profile_id):
resp = requests.get(
f"{BASE_URL}/api/v1/browser/start?user_id={profile_id}",
headers=HEADERS,
timeout=30,
).json()
if resp["code"] == 0:
ws = resp["data"]["ws"]["puppeteer"]
port = ws.split(":")[2].split("/")[0]
return port
return None
def close_profile(profile_id):
requests.get(
f"{BASE_URL}/api/v1/browser/stop?user_id={profile_id}",
headers=HEADERS,
)
# Process each profile
profiles = get_profiles("My Campaign")
for p in profiles:
port = open_profile(p["user_id"])
if port:
print(f"Profile {p['name']} ready on port {port}")
print(f"Connect MCP: npx chrome-devtools-mcp@latest --browserUrl=http://127.0.0.1:{port}")
# Your automation here...
input("Press Enter when done with this profile...")
close_profile(p["user_id"])
time.sleep(2)| Scenario | What happens |
|---|---|
| Multi-account health check | Open each profile → MCP checks login status, screenshots dashboard |
| Ad verification | Open profiles with different geo proxies → MCP inspects ad content per region |
| Fingerprint auditing | Open profiles → MCP navigates to BrowserScan → reads fingerprint results |
| Authenticated scraping | Open profile with saved cookies → MCP extracts data from logged-in pages |
| A/B test across identities | Open multiple profiles → MCP captures different UI versions |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.