Skip to main content
Glama
Barthelemy-Drabczuk

champollion-sulcal-mcp

by Barthelemy-Drabczuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to champollion-sulcal-mcp

No user-submitted related servers found.

    Related Servers

    • consulting-mcp-server

      Brinkv3
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes RAG and document intelligence pipelines as 8 composable tools for MCP-compatible clients, enabling querying, indexing, classifying, extracting, and assessing documents.
      1
      MIT

    • robosimtools-mcp

      RahulRajelli
      A
      license
      A
      quality
      B
      maintenance
      Exposes 12 robotics/simulation tools from robosimtools.com as MCP tools, enabling AI agents to perform conversions (quaternion, URDF, MJCF), validation, and CAD imports locally.
      12
      1
      MIT

    • omp-mcp

      arosyihuddin
      A
      license
      Not graded
      quality
      C
      maintenance
      Wraps Oh My Pi built-in tools (read, write, edit, bash, grep, etc.) as MCP tools, enabling file operations, shell commands, web search, and agent coordination.
      5 npm
      Apache 2.0

    • neurograph

      InsideProxy
      F
      license
      A
      quality
      B
      maintenance
      Exposes NeuroGraph's scientific API to AI models as MCP tools, enabling them to query, analyze, and visualize brain networks — regions, tracts, connectivity, literature, and cross-species homologies — drawn from a portable SSD-based neuroimaging data library. Lets models read real atlas data, load datasets, compute graph metrics, and produce visualization scene descriptors without acting as the scientific engine itself.
      12
      2
      -
    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.5/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct operation: launching pipeline stages (start_*), subject management (purge_subject, prune_failed_subjects), job control (get_job_status, list_jobs, cancel_job, get_job_log), and pipeline info (get_pipeline_info, preflight_check). Minimal overlap; even similar tasks like subject removal are differentiated by scope.

    Naming Consistency4/5

    Most tools follow a consistent pattern: launch verbs (start_*) for pipeline stages, get_* for retrieval, and descriptive verbs for actions. Deviations include 'purge_subject' vs. 'prune_failed_subjects' (different delete verbs) and 'preflight_check' (no prefix), but overall naming is clear and predictable.

    Tool Count5/5

    17 tools is appropriate for a multi-stage neuroimaging pipeline with job management and utility functions. Each tool earns its place, covering all stages and supporting operations without being excessive or sparse.

    Completeness5/5

    The tool set covers the full pipeline lifecycle: stage launches, job monitoring, subject cleanup, and configuration checks. All essential operations are present with no obvious gaps for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources