Skip to main content
Glama
Sign In
@rotifer/mcp-server

@rotifer/mcp-server

by rotifer-protocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @rotifer/mcp-server

No user-submitted related servers found.

    Related Servers

    • hiveforge

      srotzin
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for autonomous agent minting, crossbreeding, and evolution. Mint new AI agents with genetic lineage tracking, cross-breed capabilities between agents, run evolution cycles, and discover complementary agents in the HiveBazaar marketplace.
      MIT

    • aiskillstore

      garasegae
      A
      license
      A
      quality
      D
      maintenance
      Agent-first skill marketplace MCP server. AI agents discover, install, and share skills across 7 platforms via MCP protocol. 15 tools including skill search, download, upload, and agent discovery.
      18
      4
      MIT

    • aai-gateway

      gybob
      A
      license
      A
      quality
      D
      maintenance
      Unified MCP and skill management gateway for AI agents, enabling tool discovery, installation, and sharing with 99% context token savings.
      8
      47 npm
      91
      Apache 2.0
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.3/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools have clearly distinct resource+action targets across local genes, agents, cloud registry, arena, auth, and analytics. Minor overlap exists around test_gene vs compile_gene/run_gene, publish_gene's optional arena submission vs arena_submit, and the trio get_gene_detail/get_gene_stats/get_gene_reputation, but descriptions make the boundaries workable.

    Naming Consistency3/5

    Casing is consistently snake_case and most names are verb_noun (list_local_genes, install_gene, create_agent). However, ordering is mixed: arena_submit, agent_run, and vg_scan are noun-first, while doctor, login, and logout are bare verbs/nouns, so the pattern is readable but not fully predictable.

    Tool Count2/5

    At 31 tools, the surface is heavy for one server and several could be consolidated (e.g., gene detail/stats/reputation, and test/compile/run checks). Each tool is individually meaningful, but the count exceeds a well-scoped set.

    Completeness4/5

    The lifecycle is well covered: scan/wrap/init, compile/run/test, publish, install/rollback, arena ranking/submission, plus agent creation and execution, auth, and analytics. Gaps are minor but real—no uninstall/delete Gene, no update/delete Agent, and no local Gene detail operation.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data

    Resources