Skip to main content
Glama
red-castle

red-castle

by babayaga370

Related Servers

Alternatives to red-castle

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to inspect and manage video renders, templates, generation models, hosted assets, and ingest sources while using isolated private account profiles. It requires explicit approval for mutation operations and supports both MCP and CLI access.
      23
      106 npm
      AGPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read typed objects and propose, approve, and apply audited actions with permission-aware retrieval, enforcing visibility inside queries so each principal sees only authorized data and properties.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP-capable AI clients to read a local AI ticket triage queue and human decision log through four read-only tools for checking queue status, listing pending review items, viewing recent decisions, and searching decisions. It does not allow approving, rejecting, or sending anything.
      4
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables agents to perform workspace-scoped file deletion through a ticket-gated workflow: preview paths and risks, move approved files into a recoverable .del batch, then permanently purge them after confirmation.
      3
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to manage App Store Connect releases—versions, builds, TestFlight groups, metadata, pricing, reviews, and submission—while staying read-only by default and requiring human approval before any public or destructive action.
      23
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Empowers AI agents to keep lists of records—adding, showing, noting on, attaching to, and moving items through states—while the binder itself stays outside the agent's reach. Human approval gates, per-list read/change access, and archive-only deletion keep agents from approving, seeing ungranted lists, or deleting anything.
      1,893 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: requesting deletion, listing visible objects, checking one request, and listing all of the user's requests. The single-request vs list-request distinction is explicitly clarified by the descriptions.

    Naming Consistency5/5

    All tool names use snake_case with a predictable verb-object pattern: request_deletion, list_objects, get_deletion_request, list_my_deletion_requests. The slight inclusion of 'my' is readable and consistent with the possessive scope.

    Tool Count5/5

    Four tools is well-scoped for a deletion-request workflow. Each tool earns its place by covering requesting, browsing targets, checking status, and listing requests.

    Completeness4/5

    The core deletion-request lifecycle is covered: create a request, inspect status, list requests, and view visible objects. A cancellation or withdrawal operation for pending requests is a minor gap, but human approval/restore is intentionally outside the agent surface.