"MCP Servers for Supabase" matching MCP servers:

MCP server that lets AI coding agents (Claude Code, Cursor, Cline) audit Supabase projects for security misconfigurations AND apply the fixes — without leaving the agent. Tools: audit_project, list_findings, preview_fix (BEGIN/ROLLBACK safety), apply_fix (with confirmation), apply_all_fixes (transactional bulk). Closes the audit-fix loop entirely in the agent — other Supabase scanners only report.

A basic skeleton for building MCP servers with Supabase-based authentication, RBAC, and audit logging. It provides tool and resource implementations for hub and contracts platforms, enabling secure, tenant-isolated operations.

Enables agents to discover, compare, and install other MCP servers using natural language tasks, backed by a searchable index of thousands of servers.

A neutral, public danger grade for MCP servers that AI agents rely on, providing A-F grades and transparency signals to vet servers before connecting.

Audits PostgreSQL/Supabase schemas for security issues like missing RLS, permissive policies, and sensitive data exposure during AI conversations.

Exposes the Maester security test framework for Microsoft 365/Entra/Defender as MCP tools, enabling AI agents to run tests, audit AI agents and MCP servers, and investigate security posture.

Provides AI assistants with specialized tools to interact with NIST's Open Security Controls Assessment Language (OSCAL) framework. It enables agents to retrieve schemas, explore models, and generate valid OSCAL documentation for security compliance automation.

Security gate that scans MCP servers and Claude Code Skills for vulnerabilities before execution.

Provides three AI security tools for Claude: scanning MCP servers for security risks, validating HDP delegation chains against IETF standards, and triaging security alerts with kill-chain analysis.

Permission tiers, approval gates, and audit logging for MCP servers.

Enables creation of secure-by-default MCP servers with 5-layer validation to protect against injection, path traversal, and other attack vectors.

A client-side MCP proxy that injects OAuth 2.0 bearer tokens or API keys into MCP requests, enabling MCP clients to connect to OAuth/API-key-protected MCP servers like Amazon Bedrock AgentCore Gateway. It automatically fetches and refreshes credentials using AgentCore Identity or static values.

A proxy server that sits between MCP clients and servers, providing authentication, tool discovery, caching, and guardrail enforcement to protect MCP servers from malicious inputs.

Governs AI agent tool calls by checking them against Agentic Control Plane policies, returning allow/deny/ask decisions with audit logging and identity attribution for MCP clients like Claude and ChatGPT. Exposes acp_check and acp_status tools for policy enforcement and connection verification.

MCP server for Quackr, enabling virtual phone number management including balance checking, pricing, inventory, purchasing numbers, and reading SMS via Claude or any MCP-compatible client.

Provides trust scores, comparisons, and search for software entities, AI tools, packages, and MCP servers using Nerq's Trust Score system.

A template for building MCP servers with optional per-tool authentication using WorkOS AuthKit and Vercel MCP adapter.

Scans MCP servers for security vulnerabilities, prompt injection, and tool poisoning, providing risk scores and protection.

Authenticating reverse proxy for MCP servers providing credential isolation, OAuth2 token management, and composite tool aggregation.

Enables AI agents to safely call enterprise tools through a governed MCP gateway with permission enforcement, blast-radius controls, input validation, and a full audit trail for every invocation.