Skip to main content
Glama
vaddisrinivas

olivetin-mcp

by vaddisrinivas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to olivetin-mcp

No user-submitted related servers found.

    Related Servers

    • enterprise-mcp

      dbett4
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server exposing scoped, read-only enterprise operations tools with fail-closed credential handling. It returns opaque approval IDs for mutations and requires a separate operator approval command to release one-time capabilities.
      MIT

    • agent-security-gateway

      Un1u6ky
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides a security gateway for AI agents, enforcing allow/confirm/deny policies on tool calls and requiring human approval for risky operations, with full audit logging.
      -

    • io.github.AAH20/agent-action

      AAH20
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that gates agent tool calls by normalizing intent, denying unknown/unattended destructive actions, and requiring HITL prove approval for high-risk operations. It maintains an append-only hash-chained Action Ledger and exposes gate_check and ledger_verify tools without ever executing tools.
      MIT

    • Agentrim MCP

      almohtadyg1
      A
      license
      Not graded
      quality
      B
      maintenance
      A least-privilege enforcement proxy for MCP servers. It sits between MCP clients and upstream servers, enforcing tool policies, hiding denied tools, requiring human approval for risky actions, and providing a structured audit trail.
      MIT

    • approval-gate

      yulinlina
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides human-in-the-loop approval for risky AI agent actions, with durable state and audit logs.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 18 tools

    Disambiguation3/5

    The core OliveTin tools are mostly distinct, but the inclusion of unrelated tools (brave_search, render_diagram, render_chart) creates confusion about the server's purpose and could lead to misselection. There is also mild overlap between get_execution_logs and get_execution_status, though descriptions help clarify.

    Naming Consistency4/5

    Most tools follow a clear verb_noun snake_case pattern (e.g., list_olivetin_actions, get_execution_status, kill_action). Minor exceptions like whoami, readyz, and brave_search deviate from the pattern but are still recognizable and don't cause significant inconsistency.

    Tool Count3/5

    At 18 tools, the set is on the heavier side. The 15 OliveTin-specific tools are reasonably scoped for the domain, but the three unrelated utility tools pad the count and make the server feel less focused.

    Completeness4/5

    The OliveTin surface covers the core lifecycle: listing/getting actions, starting/killing/restarting, status/logs, approvals, entities, validation, user/server info, health, and reload. Minor gaps include lack of entity mutations and synchronous action start, but these are not critical for typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources