Servidor MCP de Prowler Cloud

• Direcciónhttps://mcp.prowler.com/mcpno está en el registro oficial: respondió al preguntarle

Ninguna entrada del registro oficial de MCP nombra este servidor. Respondió en prowler.com cuando el Atlas preguntó en la dirección donde suelen montarse los servidores, así que es del propio proveedor. Los clientes y catálogos que listan servidores a partir del registro no lo muestran.

• Estadorespondecomprobado el 2026-10-27
• Herramientas100
• El servidor se llamaprowler-mcp-server
• Versión del servidor3.4.4
• Versión del protocolo2025-06-18

El 2026-10-27 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 178 ms.

• Sus herramientas hacen todos los casos de uso comprobados: scan cloud infrastructure for security misconfigurations and compliance violations; automate compliance monitoring against CIS, GDPR, NIST and other frameworks.
• Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
• Qué puede hacer un agente con él2 de 2 casos de uso
• Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta568 ms
• Espacio en el contexto del agente≈ 54.366 tokenslas definiciones de todas sus herramientas (100), que el agente lleva en cada turno
• Definiciones de herramientasB · 83 de 100
• Resultados tipados100 de 100 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Sin indicar si solo lee o puede destruir: 100 de 100

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• prowler_hub_list_checks

  List security Prowler Checks with filtering capabilities. IMPORTANT: This tool returns LIGHTWEIGHT check data. Use this for fast browsing and filtering. For complete details including risk, remediation guidance, and categories use…

• prowler_hub_semantic_search_checks

  Search for security checks using free-text search across all metadata. IMPORTANT: This tool returns LIGHTWEIGHT check data. Use this for discovering checks by topic. For complete details including risk, remediation guidance, and…

• prowler_hub_get_check_details

  Retrieve comprehensive details about a specific security check by its ID. IMPORTANT: This tool returns COMPLETE check details. Use this after finding a specific check ID, you can get it via `prowler_hub_list_checks` or…

• prowler_hub_get_check_code

  Fetch the Python implementation code of a Prowler security check. The check code shows exactly how Prowler evaluates resources for security issues. Use this to understand check logic, customize checks, or create new ones. Returns: {…

• prowler_hub_get_check_fixer

  Fetch the auto-remediation (fixer) code for a Prowler security check. IMPORTANT: Not all checks have fixers. A check with no auto-remediation code fails with a message saying so - this is normal for many checks and not a problem to report…

• prowler_hub_list_compliances

  List compliance frameworks supported by Prowler. IMPORTANT: This tool returns LIGHTWEIGHT compliance data. Use this for fast browsing and filtering. For complete details including requirements use `prowler_hub_get_compliance_details`…

• prowler_hub_semantic_search_compliances

  Search for compliance frameworks using free-text search. IMPORTANT: This tool returns LIGHTWEIGHT compliance data. Use this for discovering frameworks by topic. For complete details including requirements use…

• prowler_hub_get_compliance_details

  Retrieve comprehensive details about a specific compliance framework by its ID. IMPORTANT: This tool returns COMPLETE compliance details. Use this after finding a specific compliance via `prowler_hub_list_compliances` or…

• prowler_hub_list_providers

  List all providers supported by Prowler. This is a reference tool that shows available providers (aws, azure, gcp, kubernetes, etc.) that can be scanned for finding security issues. Use the provider IDs from this tool as filter values in…

• prowler_hub_get_provider_services

  Get the list of services IDs available for a specific cloud provider. Services represent the different resources and capabilities that Prowler can scan within a provider (e.g., s3, ec2, iam for AWS or keyvault, storage for Azure). Use…

• prowler_get_attack_paths_cartography_schema

  Retrieve the Cartography graph schema for a completed attack paths scan. This tool fetches the full Cartography schema (node labels, relationships, and properties) so the LLM can write accurate custom openCypher queries for attack paths…

• prowler_list_attack_paths_queries

  Discover available Attack Paths queries for a completed scan. IMPORTANT: The scan must be in 'completed' state to list queries. Attack Paths covers AWS providers only, so only an AWS provider has an Attack Paths scan to name here, and…

• prowler_list_attack_paths_scans

  List Attack Paths scans with filtering capabilities. Default behavior: - Returns COMPLETED scans (ready for attack paths analysis) - Returns 50 scans per page - Shows the latest scan per provider Each scan includes: - Core identification…

• prowler_run_attack_paths_query

  Execute an Attack Paths query and analyze the results. IMPORTANT: This is the PRIMARY tool for attack paths analysis. It executes a Cypher query against the Neo4j graph database and returns the attack path graph with security findings…

• prowler_get_compliance_framework_state_details

  Get detailed requirement-level breakdown for a specific compliance framework. IMPORTANT: This tool returns DETAILED requirement information for a single compliance framework, focusing on FAILED requirements and their associated FAILED…

• prowler_get_compliance_overview

  Get high-level compliance overview across all frameworks for a specific scan. This tool provides a HIGH-LEVEL OVERVIEW of compliance status across all frameworks. Use this when you need to understand overall compliance posture before…

• prowler_get_finding_group_details

  Get complete details for one finding group by exact check ID. Uses `filter[check_id]` exact matching against latest data by default, or historical data when dates are provided. Fully muted groups are included by default so accepted risk…

• prowler_list_finding_group_resources

  List resources affected by a finding group. Without dates this uses `/finding-groups/latest/{check_id}/resources`. With `date_from` or `date_to`, this uses `/finding-groups/{check_id}/resources` with a maximum 2-day date window. Default…

• prowler_list_finding_groups

  List finding groups aggregated by check ID. Default behavior returns the latest non-muted FAIL groups for fast triage. Without dates this uses `/finding-groups/latest`. With `date_from` or `date_to`, this uses `/finding-groups` with a…

• prowler_get_finding_details

  Retrieve comprehensive details about a specific security finding by its ID. IMPORTANT: This tool returns COMPLETE finding details. Use this after finding a specific finding via prowler_search_security_findings This tool provides ALL…

• prowler_get_findings_overview

  Get aggregate statistics and trends about security findings as a markdown report. This tool provides a HIGH-LEVEL OVERVIEW without retrieving individual findings. Use this when you need to understand the overall security posture, trends…

• prowler_search_security_findings

  Search and filter security findings across all cloud providers with rich filtering capabilities. IMPORTANT: This tool returns LIGHTWEIGHT findings. Use this for fast searching and filtering across many findings. For complete details use…

• prowler_create_amazon_s3_integration

  Create an Amazon S3 integration to export scan outputs to an S3 bucket. After every scan of an attached provider, Prowler uploads the generated reports to 's3://{bucket_name}/{output_directory}/'. IMPORTANT: The connection is checked…

• prowler_create_aws_security_hub_integration

  Create an AWS Security Hub integration to send findings to Security Hub in ASFF format. After every scan of the attached provider, Prowler pushes its findings to Security Hub in every region where the Prowler partner integration is…

• prowler_create_jira_integration

  Create a Jira integration to open Jira work items from Prowler findings. Unlike the other integration types, Jira is tenant-wide: it is not attached to any provider and applies to every finding the role can see. IMPORTANT: Jira…

• prowler_delete_integration

  Permanently remove an integration from Prowler. WARNING: This is a destructive operation that cannot be undone. The stored credentials are destroyed with it, so the integration has to be recreated from scratch, with its credentials, to be…

• prowler_get_integration

  Retrieve an integration with its complete, integration-type specific configuration. IMPORTANT: Credentials are never returned by Prowler, only the configuration. This tool provides ALL information that prowler_list_integrations returns…

• prowler_get_jira_issue_types

  List the issue types available in a Jira project. Prowler fetches them live from Jira and stores them in the integration configuration, so the answer is always current. IMPORTANT: The project key must already be present in the 'projects'…

• prowler_list_integrations

  List the integrations configured in Prowler, with their connection state. Integrations are the destinations Prowler sends its results to. They are configured per tenant and require the 'manage_integrations' permission. IMPORTANT: This…

• prowler_send_findings_to_jira

  Create Jira work items from Prowler findings. Each work item carries the finding's check title, severity, status, provider, region, resource, risk description and remediation steps. Selecting the findings, exactly one of the two is…

• prowler_test_integration_connection

  Check that Prowler can reach an integration with its stored credentials. This also refreshes the parts of the configuration that Prowler discovers from the remote system, so it is the way to repair a stale configuration: - jira…

• prowler_update_integration

  Update an integration's credentials, configuration, providers or enabled state. The integration type cannot be changed. To switch types, delete the integration and create a new one. Default behavior: - Only the parameters provided are…

• prowler_create_mute_rule

  Create a new mute rule to mute specific findings with documentation and audit trail. IMPORTANT: This immediately mutes the specified findings AND all previous findings with matching UIDs (this could take some time to complete). The rule…

• prowler_delete_mute_rule

  Delete a mute rule from the system. WARNING: Findings that were muted by this rule REMAIN MUTED after deletion. This only removes the rule itself from management, not the muting effect on findings. The muted findings will stay muted…

• prowler_delete_mutelist

  Remove the mutelist configuration from the tenant. WARNING: This is a destructive operation that cannot be undone. - The mutelist will need to be re-created with prowler_set_mutelist - New findings from future scans will NOT be muted by…

• prowler_get_mute_rule

  Retrieve comprehensive details about a specific mute rule by its ID. IMPORTANT: This tool returns COMPLETE mute rule details including the full list of finding UIDs. Use this after finding a rule via prowler_list_mute_rules. This tool…

• prowler_get_mutelist

  Retrieve the current mutelist configuration for the tenant. IMPORTANT: Only one mutelist can exist per tenant. Fails with a message saying so if no mutelist exists. For detailed information about mutelist structure and configuration…

• prowler_list_mute_rules

  Search and filter mute rules with pagination support. IMPORTANT: This tool returns LIGHTWEIGHT mute rules without the full list of finding UIDs. Use prowler_get_mute_rule to get complete details including all finding UIDs and creator…

• prowler_set_mutelist

  Create or update the mutelist configuration for pattern-based bulk muting. IMPORTANT: Automatically creates a new mutelist or updates the existing one (only one mutelist per tenant). The configuration completely replaces any existing…

• prowler_update_mute_rule

  Update a mute rule's name, reason, or enabled status. IMPORTANT: Cannot change which findings are muted (finding_uids are immutable). Disabling a rule does NOT un-mute findings - they remain muted permanently. Default behavior: - Only…

• prowler_connect_provider

  Register a provider to be scanned with Prowler. This tool will register a provider in Prowler, even if the UID is wrong. If the provider is already registered, it will be updated with the new provided alias or credentials if provided. If…

• prowler_delete_provider

  Permanently remove a registered provider from Prowler. WARNING: This is a destructive operation that cannot be undone. The provider will need to be re-added with prowler_connect_provider if you want to scan it again. Prowler removes the…

• prowler_search_providers

  Search and view configured providers to be scanned with Prowler. This tool returns a unified view of all providers configured in Prowler. For getting more details about what types of providers are available to be scanned with Prowler or…

• prowler_get_resource

  Retrieve comprehensive details about a specific resource by its ID. IMPORTANT: This tool provides COMPLETE resource details with all available information. Use this after finding a specific resource via prowler_list_resources. This tool…

• prowler_get_resource_events

  Get the timeline of cloud API actions performed on a specific resource. IMPORTANT: Currently only available for AWS resources. Uses CloudTrail to retrieve the modification history of a resource, showing who did what and when. Each event…

• prowler_get_resources_overview

  Generate a markdown overview of your resources with statistics and insights. IMPORTANT: This tool provides HIGH-LEVEL STATISTICS without returning individual resources. Use this when you need a summary view before drilling into details…

• prowler_list_resources

  List and filter all resources scanned by Prowler. IMPORTANT: This tool returns LIGHTWEIGHT resource information. Use this for fast searching and filtering across many resources. For complete configuration details, metadata, and finding…

• prowler_get_role

  Retrieve detailed information about a specific role by its ID. Returns everything `prowler_list_roles` returns PLUS: - permissions: The management capabilities the role grants (only the enabled ones). Read `permission_state` for the…

• prowler_get_user_roles

  List the roles currently assigned to a specific user. Returns the user's roles with the concrete capabilities each one grants, so you can see what the user is allowed to do in the tenant. A user normally holds a single role. Note: this…

• prowler_list_roles

  List the RBAC roles defined in the authenticated tenant. Use this to discover which roles exist and their permission scope before assigning one to a user. Returns LIGHTWEIGHT role information. Each role includes: - id: Prowler internal…

• prowler_set_user_role

  Set the role a user holds, replacing the role they had before. A user holds exactly one role in Prowler: their permissions are resolved from a single role, so granting a new one REPLACES the previous one instead of adding to it. To change…

• prowler_get_scan

  Retrieve comprehensive details about a specific scan by its ID. IMPORTANT: This tool returns COMPLETE scan details. Use this after finding a specific scan via prowler_list_scans. This tool provides ALL information that prowler_list_scans…

• prowler_list_scans

  List and filter security scans across all providers with rich filtering capabilities. IMPORTANT: This tool returns LIGHTWEIGHT scan information. Use this for fast searching and filtering across many scans. For complete scan details…

• prowler_trigger_scan

  Trigger a manual security scan for a provider. IMPORTANT: This tool returns immediately once the scan is created. The scan will continue running in the background. Use `prowler_get_scan` with the returned scan ID to monitor progress and…

• prowler_update_scan

  Update a scan's name for better organization and tracking. IMPORTANT: Only the scan name can be updated. Other scan attributes (state, progress, duration, etc.) are read-only and managed by the system. Example Useful Workflow: 1. Use…

• prowler_get_current_user

  Identify which user the current credentials authenticate as. Use this to determine the identity behind the credentials this MCP server is currently using, e.g. before performing actions on behalf of that user or when reporting who is…

• prowler_get_user

  Retrieve detailed information about a specific user by their ID. Returns everything `prowler_list_users` returns PLUS: - date_joined: When the user joined - is_verified: Whether the user confirmed their email address (Prowler Cloud only…

• prowler_list_users

  List the users that belong to the authenticated tenant. Use this to see who has access to the tenant and to look up their email addresses. Returns LIGHTWEIGHT user information optimized for browsing. Each user includes: - id: Prowler…

• prowler_cloud_build_alert_rule_condition

  Build and dry-run an alert-rule condition in one call. Nothing is persisted. This combines the two preparation steps for an alert rule: 1. SEED: translate a findings `filter_bag` into a condition DSL (skipped when you pass a `condition`…

• prowler_cloud_create_alert_rule

  Create a tenant-scoped alert rule. SIDE EFFECT: recipients that are not yet confirmed will receive a confirmation email. Requires the `manage_alerts` permission on the API key/role. Workflow: 1. Use…

Las primeras 60 de 100, en el orden del servidor.