Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/triuzzi/brave-devtools-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/triuzzi/brave-devtools-mcp/brave-mcp)<a href="https://agentmods.dev/mcp/triuzzi/brave-devtools-mcp/brave-mcp"><img src="https://agentmods.dev/badge/mcp/triuzzi/brave-devtools-mcp/brave-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
brave-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- figma-console-mcp — 86% identical, 7 lines differ
What it actually says
{
"brave-mcp": {
"command": "npx",
"args": [
"-y",
"brave-mcp"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 10 lines scan A e4fe4a7f8dea
brave-mcp is an MCP server published in the GitHub repository triuzzi/brave-devtools-mcp (28 stars, last pushed 7d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
chrome-devtools-mcp
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
public-browser
Public Browser MCP Server - Chrome browser automation via CDP. Runs locally from the public-browser npm package.
chrome-bridge-mcp
MCP server with 63 tools for browser automation via Chrome extension. Works on ChromeOS/Crostini. Runs locally from the chrome-bridge-mcp npm package.
chrome-local-mcp
A local Chrome browser automation MCP server powered by Puppeteer for Claude Code. Runs locally from the chrome-local-mcp npm package.
chrome-console-log-mcp-server
MCP server for capturing Chrome console logs via CDP. Runs locally from the @onlyhumn/chrome-console-log-mcp-server npm package.
chrome-remote-debugging-mcp
MCP server for controlling Chrome over the DevTools Protocol (CDP). Runs locally from the chrome-remote-debugging-mcp Python package.