forcepointDSC-mcp
Related Servers
Alternatives to forcepointDSC-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for the Forcepoint DLP 9.0 REST API. Enables incident management, policy management, and authentication via natural language, with multi-user support and persistent storage in Postgres and Vault.MIT
- FlicenseBqualityNot gradedmaintenanceAn MCP server that enables interaction with SailPoint IdentityNow and Identity Security Cloud for identity governance and access management. It provides comprehensive tools to manage identities, accounts, roles, workflows, and certifications through API integration.36-
- AlicenseAqualityDmaintenanceMCP server for Thales CipherTrust Secrets Management (powered by Akeyless) enabling secrets, DFC keys, authentication methods, roles, targets, analytics management, and intelligent app development with hardcoded secret migration.12MIT

DelineaMCPofficial
AlicenseNot gradedqualityBmaintenanceMCP server for the Delinea Secret Server and Platform APIs, enabling AI agents to manage secrets, users, groups, folders, roles, and access requests through natural language commands.46MIT- FlicenseNot gradedqualityBmaintenanceMCP server that exposes 236 iikoCloud API methods across 22 domains as configurable tools, supporting multi-tenancy with credentials passed through transport channels (HTTP headers or environment variables) for security.1-
- AlicenseNot gradedqualityDmaintenanceMCP server that integrates with ARXsec.io API to execute security scans, compliance checks, secrets management, and remediation actions with policy enforcement, audit logging, and human approval workflows.MIT
TDQS
Scored across 25 tools
Tools are grouped by domain (users, groups, tokens, config, metadata) with distinct actions. The four read-only metadata tools (query_suggestion, connection_info, scope_info, endpoint_inventory) share an 'info' nature but serve different purposes, and the token tools are clearly separated by credential type.
All tools share the forcepoint_ prefix, and most follow an object_verb pattern (e.g., user_get, group_add_members). However, a few meta-tools break this pattern (query_suggestion, connection_info, scope_info, endpoint_inventory, health_check, api_request), so the convention is not perfectly uniform.
With 25 tools, the server is at the upper boundary of what feels heavy. The breadth is justified by covering multiple Forcepoint domains (users, groups, tokens, config, system info), but the four meta-tools could arguably be consolidated, making the count feel slightly excessive.
The tool surface provides solid CRUD coverage for users and groups, token management, connection config, and a generic API request fallback. The only notable gap is the lack of a dedicated user_list tool, but this is workable via forcepoint_api_request, so the gap is minor.