Skip to main content
Glama
bitatlas-group

@bitatlas/mcp-server

by bitatlas-group
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to @bitatlas/mcp-server

No user-submitted related servers found.

    Related Servers

    • Doc Manager

      giuliohome-org
      A
      license
      A
      quality
      C
      maintenance
      Zero-knowledge document vault backed by Azure Blob Storage with built-in MCP server. Client-side AES-256-GCM encryption, five tools (list, get, search, create, update), and OAuth-gated access for Claude.
      9
      1
      MIT

    • serac

      AikoGilpin
      F
      license
      Not graded
      quality
      D
      maintenance
      Sovereign E2E cloud storage for AI agents. MCP-native, zero-knowledge, RGPD-compliant, built in France.
      -
    • @saihm/mcp-server-pro by SAIHM-Admin

      @saihm/mcp-server-proofficial

      SAIHM-Admin
      A
      license
      A
      quality
      B
      maintenance
      Non-custodial memory MCP server with client-side encryption, enabling secure remember, recall, forget, and share operations with post-quantum security.
      9
      328 npm
      1
      Apache 2.0

    • memlawb

      Gitlawb
      A
      license
      Not graded
      quality
      B
      maintenance
      Zero-knowledge, self-hostable MCP server providing encrypted durable memory for AI agents, with tools to save, recall, search, list, and delete memories.
      55
      MIT

    • API Locker

      apilocker
      A
      license
      Not graded
      quality
      D
      maintenance
      Encrypted credential vault with a 21-tool MCP server. Store and manage LLM API keys, service API keys, and OAuth credentials — then let your AI agent list, reveal, rotate, rename, pause, and proxy calls through them.
      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

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity: create_folder, delete_file, get_file, list_files, search, upload_file, and vault_status all target specific, non-overlapping operations in the file vault domain. The descriptions reinforce these distinctions, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent 'bitatlas_verb_noun' pattern with snake_case throughout (e.g., bitatlas_create_folder, bitatlas_delete_file). This predictability makes the tool set easy to navigate and understand at a glance.

    Tool Count5/5

    With 7 tools, the count is well-scoped for a file vault management server. Each tool earns its place by covering essential operations like CRUD for files/folders, listing, searching, and status checks, without being overly sparse or bloated.

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for the vault domain: create (upload_file, create_folder), read (get_file, list_files, search), update (implied via re-upload), delete (delete_file), and administrative status (vault_status). There are no obvious gaps that would hinder agent workflows.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources