@rotifer/mcp-server
Related Servers
Alternatives to @rotifer/mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP-native evolution control plane that discovers, tests, governs, versions, and promotes improved AI agents. Integrates with LocalLLM-MCP for real or simulated model evaluation.-
- AlicenseNot gradedqualityDmaintenanceMCP 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
- AlicenseAqualityFmaintenanceAgent-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.184MIT
- AlicenseNot gradedqualityDmaintenanceA self-improving coding agent MCP server that enables code execution, semantic memory, and reusable skills via sub-agents, turning your AI client into a meta-operating system.2AGPL 3.0
- AlicenseAqualityFmaintenanceUnified MCP and skill management gateway for AI agents, enabling tool discovery, installation, and sharing with 99% context token savings.842 npm91Apache 2.0
- AlicenseNot gradedqualityDmaintenanceTrust infrastructure for AI agents enabling directory browsing, agent submission/verification, job applications, and peer feedback exchange via MCP.MIT
TDQS
Scored across 31 tools
Most tools have clearly distinct purposes (search, install, compile, run, publish, arena, auth). However, the cluster of read-only stats/reputation tools (get_gene_stats, get_gene_reputation, get_my_reputation, get_leaderboard, get_developer_profile) could cause some hesitation, though descriptions differentiate them.
Predominantly snake_case with verb_noun pattern (search_genes, install_gene, compile_gene). Minor deviations like doctor (noun), agent_run/arena_submit (noun_verb order), auth_status (noun_noun) and vg_scan are readable but slightly inconsistent.
31 tools is heavy for the server's scope, exceeding the typical 15-tool threshold. While many operations are distinct, several could be consolidated (e.g., stats/reputation variants, auth group) or exposed as subcommands rather than separate tools.
The surface covers discovery, local lifecycle (init, scan, wrap, compile, run, test, install, rollback, publish), agents (list, create, run), auth, arena, analytics, and security scanning. Missing explicit uninstall/delete or update operations for genes/agents, but core workflows are well-covered.