Skip to main content
Glama
ousqi

mcp-tuya-close-door

by ousqi

Related Servers

Alternatives to mcp-tuya-close-door

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables secure remote control of Home Assistant and Life Dashboard/DSH via MCP, supporting entity state queries, whitelisted entity/scene control, lifecycle overview reading, DSH workspace summaries, and follow-up sending.
      1
      GNU Lesser General Public v2.1 only
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables smart home automation via MCP with human-in-the-loop approval gates, providing device discovery, state queries, policy checks, and proposal-based execution of actions and scenes that only proceed after explicit user confirmation, with full audit logging.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables control of local Xiaomi smart home devices via MCP, allowing reading real-time status and setting properties through natural language, without relying on the Xiaomi cloud.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP approval gate that ensures agents execute only human-approved, hash-verified actions, providing fail-closed consent for consequential operations.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables safely inspecting and configuring Hikvision cameras via a local MCP server, with permission enforcement, read-only diagnostics, and supervised mutation flows.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server for managing Eufy smart-lock access codes across rental properties, with safety features like dry-run planning and explicit confirmation for write operations.
      AGPL 3.0

    TDQS

    A4.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlapping purposes. The tool is trivially distinct and unambiguous.

    Naming Consistency5/5

    The single tool follows a clear snake_case verb_noun convention with a vendor prefix (tuya_close_door), matching the server name. There are no competing conventions to create inconsistency.

    Tool Count5/5

    One tool is exactly appropriate for a server whose stated purpose is a single specific action: closing a door via Tuya. The narrow scope justifies the minimal count, and the tool clearly earns its place.

    Completeness5/5

    For the declared domain of closing a door, the tool fully covers the action and even embeds the explicit confirmation requirement into its behavior. A status or dry-run tool would be a minor enhancement, not an obvious gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues