Skip to main content
Glama
Obsideo MCP server

Obsideo MCP server

by Regan-Milne

Related Servers

Alternatives to Obsideo MCP server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Sovereign E2E cloud storage for AI agents. MCP-native, zero-knowledge, RGPD-compliant, built in France.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent, cloud-based memory for AI agents, letting them remember preferences, skills, and decisions across sessions via an MCP-compatible interface.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Agent-native object storage MCP server with per-agent DID isolation and x402 pay-per-byte metering in real Base USDC, enabling autonomous agents to store and retrieve objects with hot, warm, or cold retention classes.
      MIT

    TDQS

    A3.7/5.0

    Scored across 13 tools

    Disambiguation4/5

    Core object operations (put/get/ls/rm) and verification/backup tools are clearly distinct, and account lifecycle tools separate cleanly along trial vs email signup vs code verification. The only soft overlaps are portal vs upgrade (both mint Stripe links) and plan vs usage (both report account state), and the descriptions do enough to disambiguate them.

    Naming Consistency3/5

    The set mixes terse Unix-style verbs (put, get, ls, rm) with noun-first compounds (signup_start, signup_verify) and noun-only names (plan, portal, usage, trial). Also inconsistent within the same family: signup_start puts the verb second while backup_keys puts it first, so there is no single predictable pattern.

    Tool Count5/5

    13 tools is well inside the sensible range and each one maps to a distinct need: object CRUD, integrity verification, key backup, trial/email signup, usage/plan visibility, and billing links. Nothing looks like a redundant wrapper or an orphan tool.

    Completeness4/5

    Object lifecycle (store, list, retrieve, delete), integrity verification, disaster-recovery backup, and account/quota/billing flows are all covered, so agents won't hit dead ends on core workflows. Gaps are minor: no metadata/stat or copy/move operation, no account deletion or credential-rotation tool exposed outside re-running signup, and no batch operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues