Skip to main content
Glama
SayAMSTASI

alterios-mcp

by SayAMSTASI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to alterios-mcp

No user-submitted related servers found.

    Related Servers

    • Kroki MCP

      pvliesdonk
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server scaffold that features built-in authentication, Docker support, and a comprehensive CI/CD release pipeline. It provides a standardized template for deploying servers with multi-transport support and configurable read-only modes.
      MIT

    • metrc-mcp

      AM253906
      A
      license
      A
      quality
      B
      maintenance
      MCP server for METRC cannabis track-and-trace API, focused on processor workflows like inventory checks, transfer reconciliation, and lab results, with read-only safety defaults.
      8
      MIT

    • Coding MCP Server

      kieutrongthien
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-oriented MCP server for coding agents that enables multi-project management through secure file operations, Git integration, and safe command execution. It supports project discovery across multiple root directories and provides robust audit logging with both STDIO and HTTP transport options.
      15 npm
      2
      MIT

    • AccelMCP

      t-ogawa-dev
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server with HTTP/stdio support, a web admin panel for managing services, capabilities, and user permissions with Bearer token authentication, enabling relay and access control for MCP tools.
      -
    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

    C2.3/5.0

    Scored across 77 tools

    Disambiguation3/5

    Many tools are clearly tied to distinct resources, but there are multiple near-overlapping clusters: seven validate_* tools, several fast_live_bulk_* write paths versus execute/call/rest write tools, and overloaded terms like group (project/user/menu) and field (content type/view/content row). The descriptions help, but an agent would frequently need to read closely to avoid misselection.

    Naming Consistency4/5

    All tool names use snake_case with a consistent alterios_/gitea_/local_ prefix and mostly follow a verb_noun pattern. Minor deviations include mixed write verbs (upsert/update/patch/execute/call/start) and awkward modifiers like fast_live_bulk_, but the overall convention is predictable and readable.

    Tool Count1/5

    With 77 tools, this server is far beyond the 50+ threshold for an extreme count. Even though the server spans CMS, BPMN, reports, security, icons, and workboards, the sheer number creates a heavy and exhausting tool-selection surface rather than a well-scoped one.

    Completeness3/5

    The surface is broad and covers many lifecycles: content types, fields, views, forms, reports, BPMN, security, icons, and workboard operations. However, there are notable gaps: security has delete role/user but no create/update equivalents, content rows lack a generic create tool, and many resource types have no delete or full lifecycle coverage.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources