Skip to main content
Glama
Regan-Milne

Obsideo MCP server

by Regan-Milne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Obsideo MCP server

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • ViBo MCP Server

      vnbochkarev-netizen
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent memory (L1/L2/L3 encrypted), web-search savings, and thread memory for AI agents, enabling token savings and context retention across MCP clients.
      48 npm
      1
      MIT

    • HippoDid MCP Server

      SameThoughts
      A
      license
      Not graded
      quality
      C
      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

    • hive-mcp-agent-storage

      srotzin
      A
      license
      Not graded
      quality
      C
      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
    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.8/5.0

    Scored across 13 tools

    Disambiguation4/5

    The storage commands (put/get/ls/rm/verify) and account/billing tools are largely distinct, and the long descriptions clearly disambiguate the signup flow. Minor overlap remains between trial and signup_start (both can bootstrap an account) and between plan/upgrade/portal, but their roles are clear enough to avoid serious misselection.

    Naming Consistency3/5

    Names are consistently lowercase and terse, with signup_start/signup_verify and backup_keys using underscores, but the set mixes verb commands (put/get/rm), noun commands (usage/plan/portal), and noun-as-action commands (trial). It is readable, but no single predictable verb_noun grammar is maintained.

    Tool Count5/5

    Thirteen tools cover storage, account lifecycle, and billing without bloat; each tool addresses a distinct operation or workflow. The count is squarely in the ideal 3–15 range for this server's scope.

    Completeness5/5

    The surface covers account creation/claiming/verification, plan and quota inspection, upgrades and cancellations via portal, full object CRUD with encryption, independent integrity verification, and key backup. No obvious dead ends remain for the stated storage and account-management purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources