Skip to main content
Glama
informatics-isi-edu

Deriva MCP Server

Official
by informatics-isi-edu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Deriva MCP Server

No user-submitted related servers found.

    Related Servers

    • Verodat MCP Server

      mcpflow
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI systems to manage Verodat accounts, workspaces, and datasets, including creating datasets, querying data, and executing AI-powered queries through natural language.
      9 npm
      Apache 2.0

    • Databricks MCP Server

      nainikayakkali
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Databricks workspaces programmatically, providing comprehensive tools for cluster management, notebook operations, job orchestration, Unity Catalog data governance, user management, permissions control, and FinOps cost analytics.
      188 npm
      MIT

    • mlops-mcp-server

      anant-patankar
      A
      license
      D
      quality
      D
      maintenance
      Enables AI assistants to perform MLOps workflows such as experiment tracking, model registry, dataset management, pipeline orchestration, and data lineage by wrapping DVC, MLflow, and Git.
      100
      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

    B3.4/5.0

    Scored across 101 tools

    Disambiguation2/5

    The annotation tools heavily overlap: set_visible_columns vs. add/remove/reorder_visible_column, set_display_annotation vs. set_table_display/set_column_display, and set_table_display vs. set_table_display_name are easy to confuse. There are also near-duplicate pairs like clone_catalog/clone_catalog_async and create_dataset_type_term/add_term, plus similar-sounding create_execution and create_execution_dataset. With 101 tools, an agent would frequently struggle to pick the right one.

    Naming Consistency3/5

    Most names use snake_case with a verb prefix, but the conventions are mixed: set_*, add_*, remove_*, create_*, delete_*, update_*, and apply_* are used inconsistently for parallel operations (e.g., set_visible_columns vs. add_visible_column). Some names break the pattern entirely (bag_info, rag_update, cite), and the RAG tools mix noun-first and verb-first naming. Overall it is readable but not predictable.

    Tool Count1/5

    101 tools is an extreme count for a single MCP server and creates a massive selection burden. Even accounting for the broad DerivaML domain, many tools are convenience variants or specialized duplicates that bloat the surface. This is well beyond the range where an agent can efficiently discover and choose the correct tool.

    Completeness2/5

    The server covers many workflows but has notable gaps: tools referenced in examples like get_table_annotations, list_foreign_keys, and lookup_feature are not actually provided, and there are no direct list/get tools for core entities such as datasets, workflows, or features. These missing read/discovery operations force agents to use workarounds like preview_table or rag_search, and can cause failures when following described workflows.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources