"A tool for managing and working with file systems" matching MCP servers:

Enables AI agents to call tools through a security gateway that intercepts requests, enforces deterministic policy and risk checks, blocks or escalates high-risk actions for human approval, and keeps tool credentials and audit logs protected.

MCP server enabling Claude Code to capture screenshots of Windows applications through WSL2, allowing AI to diagnose UI errors and verify layouts.

Implements a secure MCP server with API Key and JWT authentication, providing tools like echo, login, secure_action, and admin_action. Includes MCP Inspector integration for testing and debugging.

Enables AI assistants to list directories, read, write, and search files within a locked root directory, using resolve-then-validate path checks, size caps, and binary detection to prevent sandbox escapes.

Local, read-only MCP server that provides verified access to bounded.tools' signed static API, including the Web-Build Conformance report and SPDX SBOM, with byte-for-byte verification against a Sigstore-signed manifest.

Enables centralized proxy and orchestration of MCP servers, providing unified tool discovery, authentication, and secure request routing. It adds a human-in-the-loop approval gate for high-risk actions and audit logging.

A secure tool-execution plane for agentic AI that enforces JWT authentication, rate limiting, prompt-injection inspection, and audit logging, while ingesting downstream OpenAPI endpoints as MCP tools.

Protects AI agents from bad tool outputs, schema mismatches, and tool poisoning by validating, sanitizing, and scoring reliability of tool responses.

Enables AI agents to request an independent second opinion from a different frontier model, with PII scrubbing before transit, live web search grounding, caching, and multi-provider failover.

A wrapper for mcp-remote that provides secure authentication for protected MCP servers using Adobe IMS or Okta OAuth flows. It features automated token management, validation, and background refreshing for seamless access to remote resources.

Enables AI agents to discover and execute tools via a secure MCP server with JWT authentication, RBAC, rate limiting, and audit logging.

Governed MCP server for bank-grade agent tool access with RBAC, PII redaction, rate limiting, and audit logging.

Provides a human-in-the-loop security layer for AI agents by intercepting file operations, explaining them with a local LLM, and enforcing a deterministic policy that requires user approval for risky actions.

Enables AI agents to safely read, write, and search files within a whitelisted sandbox directory, rejecting any attempts to escape the sandbox.

This MCP server provides secure access to databases for AI agents, enforcing authentication, authorization, human approval, logging, and notifications to prevent dangerous actions.

Enables agents to securely stage, validate, and submit binary data for on-premises storage, then list, inspect, process via registered server-side processors, and token-guarded delete those assets using opaque identifiers. Upload bytes travel over a separate data plane rather than through MCP JSON, with staging, validation, and prepare/apply/verify flows enforced throughout.

Enables AI agents to inspect any public domain’s web technology stack, email deliverability and DNS health (MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, BIMI), and HTTPS security posture with typed JSON scores and remediation-ready findings, plus history, bulk checks, monitoring alerts, and reverse technology lookups.

Enables AI agents to read connected bank accounts, transactions, and balances through the Lunch Flow Personal API using a personal API key.

A stateless remote MCP server that lets AI agents anonymously submit encrypted reports of alignment and safety failures to leaks.md (what others did) and confession.md (what the agent itself did), returning a receipt without accounts or keys. It exposes public tools such as submit_leak and submit_confession over Streamable HTTP.

Enables agents to check third-party tool licenses, validate vendor policies, and issue license receipts before using external tools.

Enables declaring a catalog of tools for LLMs, filtering them by role, validating arguments, guarding sensitive calls with server-side confirmations, and recording an audit log.

An enterprise MCP server scaffold that provides secure, governed access to internal tools through RBAC, audit logging, rate limiting, and prompt-injection boundaries, with a FastAPI control plane and OpenTelemetry observability.

Enables verification of deployment-scoped model-visible DSH tool surface conformance by checking recorded tool identities and schemas against approved locks, reporting only drift categories and hashes.

MCP server that detects and guards against tool poisoning and prompt injection attacks in tool descriptions and schemas. It provides risk scoring, pattern detection, safe rewriting, and audit reports with zero external API cost.

Enables agents to search across the pooled tools of many connected MCP servers and invoke them through a single endpoint, returning only the handful of tools relevant to each request. Filters by the caller's permissions before ranking, so agents never see or plan around tools their user is not allowed to use.

Enables MCP clients to fetch the signed-in Microsoft Entra user's profile from Microsoft Graph via the GET /me endpoint using the provided bearer token.

Enables AI agents to securely discover, invoke, and manage tools through a hardened MCP endpoint with protections like injection detection, circuit breakers, retry backoff, response caching, context-window limiting, and state snapshots.

Enables wrapping any Model Context Protocol server command so every tools/call is evaluated against compiled typed policy rails, with redaction, approval, throttling, denial, and a tamper-evident evidence trail.

Enables MCP tool handlers to be declared with a decorator, collected into a registry from a config map, and served over a bearer-token-authenticated Streamable HTTP ASGI app. Tools can also be invoked in-process without running any HTTP server.

Enables MCP clients to manage files in an isolated workspace and perform lightweight Git operations through a protected Streamable HTTP endpoint, including listing, reading, writing, searching, replacing, and deleting files plus checking status and diffs.