Chrome MCP Server (Security Hardened) (Pantheon-Security/chrome-mcp-secure) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. It declares 22 tools. No publisher has claimed this listing.

D
Caution
56/100

Chrome MCP Server (Security Hardened)

Enterprise-grade Chrome automation for AI agents with compliance-ready logging, post-quantum encryption, and SIEM integration.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Pantheon-Security

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 4 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 3 credentials: CHROME_MCP_AUTH_TOKEN, CHROME_MCP_ENCRYPTION_KEY, CHROME_MCP_USE_MACHINE_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies4 high1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.12.1GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.12.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.12.1GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highws@8.18.0GHSA-96hv-2xvq-fx4p

ws: Memory exhaustion DoS from tiny fragments and data chunks

ws: Uninitialized memory disclosure

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAUDIT_LOGGING
configAUDIT_LOG_DIR
configCEF_DEVICE_PRODUCT
configCEF_DEVICE_VENDOR
configCEF_DEVICE_VERSION
configCHROME_DISABLE_SECURITY
configCHROME_HOST
configCHROME_MCP_ALLOWED_DOMAINS
configCHROME_MCP_AUTH_ENABLED
configCHROME_MCP_AUTH_LOCKOUT_MS
configCHROME_MCP_AUTH_MAX_FAILED
🔐 secretCHROME_MCP_AUTH_TOKEN
configCHROME_MCP_AUTH_TOKEN_FILE
configCHROME_MCP_BLOCK_ENCODED_PAYLOADS
configCHROME_MCP_BLOCK_PROMPT_INJECTION
configCHROME_MCP_BLOCK_SUSPICIOUS_URLS
configCHROME_MCP_CERT_CACHE_TTL
configCHROME_MCP_CERT_PINNING
configCHROME_MCP_CERT_PINS
configCHROME_MCP_CERT_REPORT_ONLY
configCHROME_MCP_CONFIG_DIR~/.chrome-mcp
configCHROME_MCP_CREDENTIAL_TTL300000 # 5 minutes
configCHROME_MCP_ENCRYPTION_ENABLED
🔐 secretCHROME_MCP_ENCRYPTION_KEY$(openssl rand -base64 32)
configCHROME_MCP_ENCRYPTION_KEY_FILE
configCHROME_MCP_MAX_CREDENTIALS
configCHROME_MCP_PBKDF2_ITERATIONS
configCHROME_MCP_REDACTION_BLUR
configCHROME_MCP_REDACTION_COLOR
configCHROME_MCP_REDACTION_SELECTORS
configCHROME_MCP_REDACTION_TEXT
configCHROME_MCP_RESPONSE_VALIDATION
configCHROME_MCP_SCREENSHOT_REDACTION
configCHROME_MCP_SECRETS_BLOCK
configCHROME_MCP_SECRETS_IGNORE
configCHROME_MCP_SECRETS_MIN_SEVERITY
configCHROME_MCP_SECRETS_REDACT
configCHROME_MCP_SECRETS_SCANNING
configCHROME_MCP_SESSION_CHECK_INTERVAL
configCHROME_MCP_SESSION_INACTIVITY1800000 # 30 minutes
configCHROME_MCP_SESSION_MANAGEMENT
configCHROME_MCP_SESSION_MAX_LIFETIME28800000 # 8 hours
🔐 secretCHROME_MCP_USE_MACHINE_KEY
configCHROME_MCP_USE_POST_QUANTUM
configCHROME_MCP_WARN_SUSPICIOUS
configCHROME_PORT
configCOMPLIANCE_LOG_DIR./logs/compliance
configCOMPLIANCE_LOG_FORMATcef # cef, syslog, jsonl, json
configCOMPLIANCE_MIN_SEVERITY
configHEADLESS
configHOSTNAME
configLOG_LEVEL
configSYSLOG_HOSTsiem.company.com
configSYSLOG_PORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

22/22 tools missing one or more hints — health (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); navigate (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_tabs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +19 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

1 child_process call — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 4 high severity in production deps — @modelcontextprotocol/sdk@1.12.1 (high), @modelcontextprotocol/sdk@1.12.1 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Domain consistency

npm scope @pansec doesn't match GitHub owner pantheon-security

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/pantheon-security/chrome-mcp-secure?variant=verified)](https://m8ven.ai/mcp/pantheon-security/chrome-mcp-secure)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 43646d09a9b2d4794dede4d039b9163089cb6d10
code hash: 83c71892cf009bf4b4bc27ebb123bba90d503e6edfdb20784426806ba8b03499
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client