Skip to main content
Glama
Atlasent

atlasent-mcp

Official
by Atlasent

Related Servers

Alternatives to atlasent-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Stateless enterprise policy firewall & token-cost proxy for MCP. It enforces identity, policy, and budget on every tool call.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      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.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides 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.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Gates agent tool execution with human approval, audit trails, and replay-resistant permits, enabling safe use of tools in agent loops.
      15 PyPI
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables MCP-speaking agents to execute tool calls through an authorization gate, producing signed decision records and reconciled effect rows for accountability.
      6
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Wraps 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

    A3.6/5.0

    Scored across 40 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive