| 0 |
| Ecosystem | 1 | 0 |
| Match Graph | 0 | 0 |
| Pricing | Free | Free |
| Capabilities | 22 decomposed | 9 decomposed |
| Times Matched | 0 | 0 |
Wraps 19 battle-tested security tools (Nmap, SQLmap, Nuclei, FFUF, etc.) behind a unified Model Context Protocol interface, enabling AI assistants to invoke security operations through standardized tool schemas rather than direct CLI invocation. Each tool maintains its native functionality while exposing capabilities through MCP's resource and tool calling mechanisms, allowing clients to discover available security operations via introspection without tool-specific knowledge.
Unique: Implements MCP servers as thin wrappers around CLI tools using child_process execution with structured argument building and output parsing, rather than reimplementing tool logic or requiring native language bindings. Each tool directory contains independent MCP server with its own package.json, enabling modular deployment and version management.
vs alternatives: Provides standardized MCP interface to security tools without requiring tool vendors to implement MCP natively, whereas alternatives like direct API integration require tool-specific SDKs or REST wrappers for each tool.
Implements reconnaissance tools (Amass, Assetfinder, Certificate Search, Waybackurls, shuffledns) that gather attack surface information without active network traffic, using public data sources like SSL certificate transparency logs, DNS historical records, and archive.org. Amass provides advanced passive/active mode switching with configurable data source selection, while Assetfinder performs lightweight enumeration using only public sources for speed. These tools feed domain discovery into downstream scanning workflows.
Unique: Combines multiple independent reconnaissance tools (Amass, Assetfinder, Certificate Search, Waybackurls, shuffledns) into a unified MCP interface, allowing agents to orchestrate multi-source enumeration and deduplicate results across tools. Amass integration specifically exposes passive/active mode switching and data source configuration through MCP parameters.
vs alternatives: Aggregates results from multiple public data sources through a single MCP interface, whereas standalone tools like Assetfinder only query one source type, requiring manual orchestration to combine results.
Integrates Smuggler's HTTP request smuggling detection capabilities through MCP, enabling agents to identify desynchronization vulnerabilities between frontend and backend HTTP parsers. Smuggler tests various HTTP request formatting techniques (CL.TE, TE.CL, TE.TE) to detect parser inconsistencies. The MCP wrapper handles test case generation and result interpretation, allowing agents to assess HTTP parsing security without understanding smuggling techniques.
Unique: Provides HTTP request smuggling detection through MCP by wrapping Smuggler's test case generation and response analysis. Handles interpretation of timing-based and behavior-based detection results, enabling agents to identify desynchronization vulnerabilities without understanding HTTP parsing internals.
vs alternatives: Offers specialized HTTP smuggling detection, whereas generic web scanners like Nuclei require custom templates and manual testing for smuggling vulnerabilities.
Exposes Scout Suite's multi-cloud security assessment capabilities through MCP, enabling agents to audit AWS, Azure, GCP, and other cloud provider configurations for security misconfigurations. Scout Suite performs API-based reconnaissance to enumerate cloud resources and assess compliance with security best practices. The MCP wrapper handles cloud provider authentication, resource enumeration, and result parsing, converting Scout Suite's detailed findings into structured security assessments.
Unique: Provides multi-cloud security assessment through MCP by wrapping Scout Suite's API-based enumeration and compliance checking. Handles cloud provider authentication and resource discovery, enabling agents to audit cloud infrastructure without understanding cloud provider APIs.
vs alternatives: Offers multi-cloud security assessment with API-based resource enumeration, whereas manual cloud auditing requires deep knowledge of each cloud provider's API and security best practices.
Integrates MobSF (Mobile Security Framework) through MCP for automated mobile application security assessment. MobSF performs static and dynamic analysis on Android and iOS applications, identifying security vulnerabilities, insecure configurations, and code quality issues. The MCP wrapper handles APK/IPA file upload, analysis execution, and result parsing, converting MobSF's detailed findings into structured security assessments.
Unique: Provides mobile application security assessment through MCP by wrapping MobSF's static and dynamic analysis engines. Handles APK/IPA file processing and result parsing, enabling agents to analyze mobile applications without understanding mobile security testing methodologies.
vs alternatives: Offers automated mobile security testing with both static and dynamic analysis, whereas manual mobile security testing requires expertise in Android/iOS security and reverse engineering.
Exposes Katana's web crawling capabilities through MCP, enabling agents to discover web application endpoints and parameters through hybrid crawling that parses JavaScript. Katana performs both traditional link-following crawling and JavaScript execution to discover dynamically-generated endpoints. The MCP wrapper handles crawl configuration, scope management, and result parsing, allowing agents to map application attack surface without manual crawling.
Unique: Provides JavaScript-aware web crawling through MCP by wrapping Katana's hybrid crawling engine that executes JavaScript to discover dynamically-generated endpoints. Handles crawl scope management and result parsing, enabling agents to map SPA attack surface without understanding JavaScript execution.
vs alternatives: Offers JavaScript-aware crawling that discovers dynamically-generated endpoints, whereas traditional crawlers like Burp Suite only follow static links and miss JavaScript-generated content.
Integrates shuffledns's high-speed DNS brute-forcing and mass resolution capabilities through MCP, enabling agents to discover subdomains through wordlist-based DNS queries and resolve large subdomain lists efficiently. shuffledns uses concurrent DNS queries with configurable resolver lists to achieve high-speed resolution. The MCP wrapper handles wordlist selection, resolver configuration, and result parsing, allowing agents to enumerate DNS records without manual DNS tool configuration.
Unique: Provides high-speed DNS brute-forcing and mass resolution through MCP by wrapping shuffledns's concurrent DNS query engine. Handles resolver configuration and result parsing, enabling agents to enumerate DNS records without understanding DNS protocol or resolver selection.
vs alternatives: Offers high-speed DNS brute-forcing with concurrent query support, whereas sequential DNS tools like dig are significantly slower for large-scale enumeration.
Exposes Waybackurls's integration with Archive.org's Wayback Machine through MCP, enabling agents to discover historical URLs and archived versions of web applications. Waybackurls queries the Wayback Machine API to retrieve all captured URLs for a domain, providing insight into application evolution and potentially exposing forgotten endpoints or parameters. The MCP wrapper handles Wayback Machine API queries and result parsing.
Unique: Provides historical URL discovery through MCP by querying Archive.org's Wayback Machine API and parsing results. Enables agents to discover forgotten endpoints and parameters through archived versions without understanding Wayback Machine API mechanics.
vs alternatives: Offers historical URL discovery through Archive.org integration, whereas manual Wayback Machine browsing is time-consuming and difficult to automate at scale.
+14 more capabilities
Executes SQL queries against Supabase PostgreSQL instances through the Model Context Protocol, translating natural language or structured query requests into parameterized SQL statements. Uses MCP's tool-calling interface to expose database operations as callable functions with schema validation, enabling LLM agents to perform CRUD operations, joins, and aggregations with automatic connection pooling and credential management through Supabase client SDK.
Unique: Exposes Supabase PostgreSQL as MCP tools with automatic credential injection from Supabase client SDK, eliminating manual connection string management and enabling seamless LLM-to-database queries within Claude or compatible agents
vs alternatives: Tighter integration than generic SQL MCP servers because it leverages Supabase's built-in authentication and connection pooling rather than requiring separate database credential configuration
Exposes Supabase Auth session state and user metadata through MCP tools, allowing agents to inspect current authentication context, retrieve user profiles, and trigger auth-related operations. Integrates with Supabase's JWT-based auth system to validate sessions and access user claims without re-authenticating, using the Supabase client's built-in session management.
Unique: Integrates Supabase's JWT-based auth system directly into MCP tool interface, allowing agents to inspect and act on auth state without managing separate credential stores or re-authentication flows
vs alternatives: More seamless than generic auth MCP servers because it leverages Supabase's built-in session management and avoids redundant credential passing between agent and auth system
Invokes Supabase Edge Functions (serverless TypeScript/JavaScript functions) through MCP tools, passing parameters and receiving results with optional streaming support. Uses Supabase's edge function HTTP API to trigger functions with automatic authentication headers and response parsing, enabling agents to execute custom business logic without embedding it in the agent itself.
Supabase scores higher at 42/100 vs mcp-for-security at 35/100.
Need something different?
Search the match graph →© 2026 Unfragile. Stronger through disorder.
Unique: Exposes Supabase Edge Functions as MCP tools with automatic authentication and response parsing, allowing agents to invoke custom serverless logic without managing HTTP clients or credential injection
vs alternatives: More integrated than generic HTTP MCP tools because it handles Supabase-specific authentication, error handling, and response formatting automatically
Subscribes to real-time changes on Supabase tables through MCP's event streaming interface, using Supabase's PostgreSQL LISTEN/NOTIFY mechanism to push INSERT, UPDATE, and DELETE events to agents. Maintains persistent WebSocket connections and filters events by table and row-level policies, enabling agents to react to database changes without polling.
Unique: Bridges Supabase's PostgreSQL LISTEN/NOTIFY real-time system with MCP's tool interface, enabling agents to subscribe to database changes without managing WebSocket connections or event serialization
vs alternatives: More efficient than polling-based approaches because it uses Supabase's native real-time infrastructure rather than repeated database queries
Manages files in Supabase Storage buckets through MCP tools, supporting upload, download, list, and delete operations with automatic authentication and path-based access control. Uses Supabase's S3-compatible storage API with built-in support for public/private buckets and signed URLs for temporary access, enabling agents to handle file I/O without managing cloud storage credentials.
Unique: Exposes Supabase Storage's S3-compatible API as MCP tools with automatic authentication and signed URL generation, eliminating the need for agents to manage cloud storage credentials or generate temporary access tokens
vs alternatives: More integrated than generic S3 MCP tools because it leverages Supabase's built-in bucket policies and authentication rather than requiring separate AWS credentials
Performs semantic similarity searches on vector embeddings stored in Supabase PostgreSQL using pgvector extension, translating natural language queries into embedding vectors and executing cosine/L2 distance searches. Integrates with embedding providers (OpenAI, Cohere) or uses pre-computed embeddings, enabling agents to retrieve semantically similar documents or records without full-text search limitations.
Unique: Integrates pgvector directly into MCP tools with automatic embedding generation and distance calculation, enabling agents to perform semantic search without managing separate vector database infrastructure
vs alternatives: More efficient than external vector databases (Pinecone, Weaviate) for Supabase users because it colocates embeddings with relational data, reducing network latency and simplifying data synchronization
Exposes Supabase database schema information through MCP tools, allowing agents to discover table structures, column types, constraints, and relationships without manual schema documentation. Queries PostgreSQL information_schema and Supabase metadata tables to dynamically generate schema descriptions, enabling agents to construct valid queries and understand data relationships.
Unique: Queries Supabase's PostgreSQL information_schema directly through MCP tools, enabling agents to dynamically discover and adapt to database schemas without pre-configured schema definitions
vs alternatives: More flexible than static schema definitions because it reflects live database state, including recent migrations or schema changes
Enforces Supabase Row-Level Security policies within agent queries, ensuring that agents can only access rows permitted by RLS rules defined in the database. Evaluates policies based on authenticated user context (JWT claims, user ID) and applies WHERE clause filters automatically, preventing unauthorized data access at the database layer rather than application layer.
Unique: Delegates authorization enforcement to PostgreSQL RLS policies rather than implementing authorization in agent code, ensuring that data access rules are centralized and cannot be bypassed by agent logic
vs alternatives: More secure than application-level authorization because RLS is enforced at the database layer, preventing accidental data leaks even if agent code has bugs
+1 more capabilities