"How to View console.log Output in Chrome" matching MCP servers:

Provides a three-layer firewall for MCP servers that inspects tool outputs for malicious content, enforces egress destination policies, and gates consequential tool calls. It runs as both a proxy and an MCP server, enabling agents to scan content, check tool calls, and evaluate results before they reach the model.

MCP server for storing and managing QA workflows, encrypted credentials, and browser test run history. Enables agents to create targets, workflows, and retrieve decrypted credential bundles for test execution.

A Model Context Protocol (MCP) server for Chrome Enterprise Premium that exposes DLP rules, content detectors, connector policies, browser telemetry, and license management as MCP tools, enabling any MCP-compatible AI agent to inspect and configure a Chrome Enterprise environment.

MCP server that gives AI agents secure, consent-based access to a single browser tab, supporting read-only snapshots, element interaction with per-action approval, and frozen multi-step plans, all audited.

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

This MCP server enables interaction with Google's Verified Access API, allowing users to verify the security posture of Chrome OS and Chrome Browser devices through natural language commands.

An MCP server that sends plain-text Gmail messages only to a predefined allowlist, using generated recipient IDs instead of email addresses to enforce security.

Enables authorized web/API security analysis as a stateful, multi-stage workflow with persistent session state, human-controlled validation, candidate versus confirmed finding tracking, and stop conditions.

Blocks AI coding assistants from installing non-existent packages and accessing non-existent files.

Authentik MCP provides seamless integration with Authentik's API, supporting both full-featured and diagnostic modes. These enable secure, automated user, group, and system management through MCP-compatible tools.

Enables autonomous agents and MCP-compatible clients to enforce policy-approved actions using risk tiers, reversible checkpoints, and token approval bounds.

An MCP authorization server implementing OAuth2/OIDC flows, supporting dynamic client registration, PKCE, consent screens, and client ID metadata documents for MCP authorization.

MCP server for ai-scanner that enables AI agents to scan codebases for LLM usage, AI frameworks, and exposed secrets.

Enables AI agents to access only task-relevant data with secrets hidden and personal details pseudonymized, while enforcing destination policies to prevent data leakage even under prompt injection.

Enables AI assistants to view devices on a Portveil account and move, rotate, reconnect, or disconnect them across VPN locations, with verified successful moves.

Lets AI assistants work on sensitive files by reasoning over schemas and masked output while deterministic local code handles raw data, never exposing real values to the model.

Registers a set of inert, tempting decoy tools with any MCP-capable client so that any call from a hijacked or prompt-injected agent instantly raises an alert with full attack context and a per-call trace token. Also plants worthless canary tokens in honeypot files that trigger zero-false-positive leak alerts when they surface in agent output, files, or outbound requests.

Open behavioral litmus for MCP servers — grades A–F across tool-output injection, egress, sensitive-data, and adversarial-input, with reproducible, content-addressed evidence. Tools: run_litmus, verify_attestation.

Enables cloud-based MCP clients to delegate privacy-sensitive or large-output tasks to a local LLM, returning sanitized placeholders or digested summaries so private data never leaves the user's network.

Connects MISP to MCP clients, enabling threat indicator lookups and submissions in plain language.