Skip to main content
Glama
CYAN-ECLIPSE-TECHNOLOGIES-LLC

Cyan Eclipse Apply MCP

Official
by CYAN-ECLIPSE-TECHNOLOGIES-LLC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Cyan Eclipse Apply MCP

No user-submitted related servers found.

    Related Servers

    • ChangeWarden

      Mehdi1Hajjaji
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to request bounded GitHub changes through a default-deny policy, independent human approval, one-time execution with a GitHub App credential, and verifiable receipts.
      1
      -
    • mcp-vaara by vaaraio

      mcp-vaaraofficial

      vaaraio
      A
      license
      A
      quality
      A
      maintenance
      Gates every AI agent tool call against your policy before it runs, then writes a hash-chained, tamper-evident record of what was decided and what happened. Anyone can verify that record offline, without your software, your systems or any key you hold.
      4
      529 PyPI
      15
      AGPL 3.0
    • ERDL Guard by OpenOBA

      ERDL Guardofficial

      OpenOBA
      A
      license
      Not graded
      quality
      A
      maintenance
      Enforces deterministic policy decisions on AI agent tool calls, supporting allow, deny, correct, escalate, and human review actions with verifiable audit receipts.
      10 npm
      MIT

    • kube-handrail

      bcfmtolgahan
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform safe, auditable Kubernetes write actions such as scaling, restarting and rolling back Deployments through a plan → policy-check → approve → apply → audit flow, with server-side guards, single-use plans and scoped RBAC. Read-only planning and Prometheus SLO/alert tools support the same guarded workflow.
      Apache 2.0
    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

    B3.3/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct stage or control: search vs. match vs. prepare vs. approve/reject are clearly separated, and policy get/set, pause/resume, tracker vs. receipts are also easy to distinguish. No two tools appear to do the same thing, and the descriptions reinforce the boundaries.

    Naming Consistency4/5

    Nearly all tools follow a consistent snake_case verb_noun pattern (search_jobs, prepare_application, set_policy). The global pause/resume actions omit an explicit noun, which is a minor but reasonable deviation.

    Tool Count5/5

    With 13 tools, the set is well-scoped for a job-application workflow that includes search, matching, preparation, approval, receipts, policy, and safety controls. Each tool appears to earn its place, and the count is comfortably within the ideal range.

    Completeness4/5

    The core lifecycle is covered: search, match, prepare, approve/reject, track, receipt, policy, pause/resume, and data purge. Minor gaps remain, such as no standalone tool to view or update a profile after ingestion, and no explicit job-detail or cached-job listing tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources