Skip to main content
Glama
houtini-ai

Houtini-lm

by houtini-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Houtini-lm

No user-submitted related servers found.

    Related Servers

    • Converse MCP Enhanced

      justmy2satoshis
      A
      license
      Not graded
      quality
      D
      maintenance
      Multi-model AI conversation MCP for Claude Desktop. Seamlessly integrate with GPT-4, Gemini, xAI, Perplexity, and local models via Ollama.
      MIT

    • mcp-local-llama

      chrishorne74
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that delegates mechanical tasks like summarization, classification, extraction, and drafting to a local Llama.cpp LLM, serving as a cost-optimization layer while Claude handles reasoning and quality control.
      MIT

    • local-llm-mcp

      drangoht
      A
      license
      A
      quality
      C
      maintenance
      MCP server connecting Claude Code to LM Studio, delegating token-expensive tasks to a local model while keeping the cloud model in control. It reduces cloud context usage by reading files locally and returning only the processed results.
      4
      MIT
    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

    B3/5.0

    Scored across 34 tools

    Disambiguation2/5

    Multiple tools have overlapping purposes that could cause confusion. For example, analyze_code_quality, analyze_single_file, and suggest_refactoring all seem to analyze code quality with unclear boundaries, while audit_wordpress_plugin and wordpress_plugin_readiness both audit WordPress plugins. The descriptions are similar across many analysis tools, making it hard to distinguish when to use each one.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., analyze_code_quality, generate_unit_tests), with clear and descriptive names. There are minor deviations like arcade_game (noun-only) and custom_prompt (adjective_noun), but the overall pattern is readable and predictable across the set.

    Tool Count2/5

    With 34 tools, the count is too high for a coherent set, feeling bloated and unfocused. The server mixes code analysis, WordPress-specific tools, game generation, and system diagnostics without a clear unified scope, making it difficult for an agent to navigate effectively.

    Completeness3/5

    The toolset covers various domains like code analysis, WordPress, and generation, but within each area, there are gaps. For example, in code analysis, there's no tool for updating or deleting code, and in WordPress, missing tools for core operations like installing or managing plugins. The surface is broad but not deep, with notable missing operations for full lifecycle coverage.

    Maintenance

    ActivitySlowing
    ResponsivenessSlow

    Resources