Skip to main content
Glama
Agaveis

hiberden-mcp

by Agaveis
OverviewSchemaSourceRelated ServersDiscussionsAdmin

Related Servers

Alternatives to hiberden-mcp

No user-submitted related servers found.

    Related Servers

    • Boxes MCP

      Alex-Keyes
      F
      license
      A
      quality
      C
      maintenance
      Enables local-first search and analysis of Boxes home inventory exports and images, with tools for inventory queries, documentation audits, and signed webhook verification.
      7
      -

    • studyproof

      Lapmlnex
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only search and context-pack creation over a local source library, letting AI assistants retrieve relevant excerpts and audit cited quotations.
      MIT

    • MCP Memory

      PascalNoisette
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Kilo Code and Opencode conversation history stored in a local SQLite database, allowing users to list projects and sessions, read messages, and perform full-text keyword searches across all messages.
      -

    • LegalQuants MCP

      onurkafk
      F
      license
      A
      quality
      C
      maintenance
      Enables searching a local catalog of LegalQuants community builds, inspecting individual listings and indexing status, and retrieving exact cited source excerpts from indexed GitHub repositories. All tools run locally and read-only, returning ranked results with revision, line numbers, and links while disclosing anything unavailable.
      4
      -
    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.3/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource and granularity: list_* for enumeration, *_detail for single-resource lookup, find_file/list_archive_files for file-level search versus manifest, and the two roll-ups (coverage_status vs catalog_stats) explicitly cross-reference each other. There is no realistic query where an agent would be torn between two tools.

    Naming Consistency4/5

    The dominant patterns are clear: list_<plural> for enumeration and <noun>_detail for single-item views. The remaining names (coverage_status, catalog_stats, recent_activity, find_file, verify_copy) are descriptive and snake_case, but mix noun-noun and verb-noun forms, so the convention is mostly consistent rather than fully uniform.

    Tool Count5/5

    14 tools map cleanly onto the archive library's resource types—projects, collections, archives, files, destinations, tapes, jobs—plus cross-cutting views for coverage, activity, stats, and verification. Each tool has a clear purpose and none feels redundant or like filler.

    Completeness4/5

    The read/verify surface is strong: every major resource has a listing, most have detail views, file-level search and manifests exist, and job/tape/coverage states are covered. The notable gap is lifecycle management—no restore, policy editing, destination creation, or backup triggers—so agents can inspect and verify but cannot act beyond verification.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources