atlasent-mcp
OfficialRelated Servers
Alternatives to atlasent-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceStateless enterprise policy firewall & token-cost proxy for MCP. It enforces identity, policy, and budget on every tool call.1MIT
- AlicenseNot gradedqualityCmaintenanceGoverns 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.MIT
- FlicenseNot gradedqualityBmaintenanceProvides a secure MCP boundary for AI agents, intercepting and validating tool calls, redacting secrets, and requiring human approval for sensitive actions with a tamper-evident audit trail.-
- AlicenseNot gradedqualityBmaintenanceGates agent tool execution with human approval, audit trails, and replay-resistant permits, enabling safe use of tools in agent loops.15 PyPIMIT
- AlicenseAqualityAmaintenanceEnables MCP-speaking agents to execute tool calls through an authorization gate, producing signed decision records and reconciled effect rows for accountability.6Apache 2.0
- FlicenseNot gradedqualityCmaintenanceWraps your existing MCP servers and checks each tool call against policy and live state before it runs. Allow, block, or require a refresh, with a reason the agent can act on.5-
TDQS
Scored across 40 tools
Most tools have distinct purposes, but the presence of both `evaluate` and `atlasent_evaluate` (and similarly `verify_permit` and `atlasent_verify_permit`) creates potential ambiguity between V1 endpoints and prefixed versions. Descriptions help differentiate, but the overlap is notable.
The majority of tools follow the `atlasent_verb_noun` pattern, but there are clear exceptions like `deploy_service`, `evaluate`, and `verify_permit`. Additionally, the verb order varies (e.g., `trajectory_verify` vs `create_policy`), and the `vqp_*` prefix adds another subcategory. This mix reduces overall consistency.
With 40 tools, the server is on the heavy side for an MCP server. While each tool covers a specific aspect of the AtlaSent platform (policy evaluation, compliance, SCIM, webhooks, etc.), the high number may overwhelm agents and suggests possible over-fragmentation.
The tool set covers a wide range of operations: CRUD for policies, SCIM users, and webhooks; multiple evaluation modes; compliance evidence; SIEM configuration; VQP tools; audit logs; and permit management. Missing group management (beyond listing) and minor gaps, but overall the core functionality is well-covered.