Skip to main content
Glama
shayben

availability_mcp

by shayben

Related Servers

Alternatives to availability_mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Local workstation attention journal that tracks focus, idle, and agent sessions, exposing timeline data via MCP for AI agents to query current or past activity.
      5
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to send notifications to a unified feed, report activity, request input from humans, and manage notification state through MCP tools.
      12 PyPI
      4
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables an MCP client such as Claude to inspect a Mac's battery, memory, CPU, GPU, disk, and most energy-hungry apps, and to shut down, restart, sleep, or lock the screen now or on a schedule with a cancellable 60-second grace period.
      14
      8 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to start and stop local read-only Windows 11 screen observation sessions, then inspect redacted screen state, UI trees, frames, and wait for changes, title matches, or idle periods through stdio tools.
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to monitor screen regions for changes or stillness, returning numeric scores and timestamps instead of pixels, so agents can wait for activity or detect frozen UI without capturing images.
      10
      37 npm
      2
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents to request human-in-the-loop approvals, choices, refinements, and notifications via MCP, with fail-closed semantics and no remote approval surface.
      4
      7
      2,828 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of confusion or misselection between tools. Its purpose (retrieving the local user's idle duration and activity state) is unambiguous.

    Naming Consistency5/5

    The single tool follows a clear verb_noun convention (get_user_activity). With only one tool there is no inconsistency to introduce.

    Tool Count3/5

    A single tool is thin for a server, even one with a narrow scope like availability detection. It works but leaves little room for related queries, making the surface feel minimal.

    Completeness4/5

    For the narrow stated purpose of determining user availability, the tool covers the key signal (idle duration and activity state). Coverage is reasonable, though richer availability context (e.g. session or lock state) is absent.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues