Skip to main content
Glama
quzhiii

ai-disk-doctor-integrations

by quzhiii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to ai-disk-doctor-integrations

No user-submitted related servers found.

    Related Servers

    • github-assistant-mcp

      imshashwatsingh
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that lets AI assistants inspect local workspace files, search context, view git diffs, and fetch a fixed GitHub profile, all within a sandboxed stdio transport.
      5
      ISC

    • local-tools-mcp-server

      fenhuayue
      F
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that enables AI assistants to search files, list directories, retrieve system info, and get file metadata on the local file system.
      4
      -

    • @asitis/mcp

      Katta041
      A
      license
      Not graded
      quality
      A
      maintenance
      Read-only MCP server that enables inspecting and auditing markdown agent steering files such as CLAUDE.md, AGENTS.md, GEMINI.md, SKILL.md, rules, commands and memory files. It reads files byte-exactly, outlines headings, lints frontmatter, invisible characters and broken links, estimates per-session token budgets, and locates steering files by when they load, all without ever writing, deleting or making network calls.
      MIT

    • autopsy-mcp

      th0r10293847
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server that exposes Autopsy digital forensics case data as tools, enabling LLM clients like Cline to browse filesystems, query artifacts, and search keywords without modifying the case.
      1
      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

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: scan_summary runs a scan, core_status checks the Core installation, ai_model_inventory lists models, and latest_diff computes diffs. No overlap or ambiguity in their responsibilities.

    Naming Consistency3/5

    All names are lowercase snake_case, but they do not follow a consistent verb_noun pattern. scan_summary starts with a verb, while core_status, ai_model_inventory, and latest_diff are noun-led or adjective-noun, creating slight inconsistency.

    Tool Count4/5

    With 4 tools, the set is small but well-focused on the disk doctor integration's core needs: scanning, status, inventory, and diffing. It is neither bloated nor insufficient for the stated purpose.

    Completeness4/5

    The tools cover primary operations (scan, check status, list models, diff latest snapshots), but lack explicit snapshot management or detailed per-file reporting. Minor gaps that an agent could potentially work around.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources