Skip to main content
Glama
Rhodium11

rhodium11-mcp

by Rhodium11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to rhodium11-mcp

No user-submitted related servers found.

    Related Servers

    • Junction41 MCP Server

      autobb888
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the Junction41 platform, providing 125 tools for agent lifecycle, jobs, workspace, payments, bounties, and more, enabling LLMs to interact with Junction41.
      21 npm
      MIT

    • MCP Enterprise Architecture

      kimji9663
      F
      license
      Not graded
      quality
      C
      maintenance
      Enterprise MCP server providing a suite of tools including file, database, GitHub, Slack, calendar, email, vector search, and Python execution, with safe defaults and OpenAI integration for automatic tool selection.
      -

    • MCP HUB V12

      0xC1pher
      F
      license
      Not graded
      quality
      D
      maintenance
      A centralized MCP server providing over 40 tools for contextual intelligence, code analysis, vision, and memory management via MemPalace, enabling efficient project development and agent orchestration.
      -

    • coding-os

      kouroshez
      A
      license
      B
      quality
      A
      maintenance
      MCP server for coding-os, a cognitive operating system that gives AI agents memory, structure, and discipline. It exposes tools for project management, task tracking, knowledge graphs, and cognition traces to Claude Code and Codex.
      87
      6
      Apache 2.0
    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

    A4.1/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool is clearly scoped to a specific resource and action, with distinct names like projects_get_projection vs keywords_projection. The descriptions further clarify any potential overlap, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a strict rh11_<resource>_<action> pattern with consistent snake_case. Actions are predictable (get, list, create, update, archive), and even the less common ones (quick_set, report_issue) fit the pattern.

    Tool Count4/5

    21 tools is on the heavier end but justified given the broad domain (account, wallet, projects, keywords, schedules, orders, feedback). Each tool addresses a distinct need, and the count remains manageable for an agent to navigate.

    Completeness4/5

    The surface covers core lifecycle operations for projects (list, create, get, update, archive), schedules (get, set, quick_set), and orders (list, get, report_issue). Minor gaps like subscription cancellation or wallet top-up exist but don't block primary workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources