Skip to main content
Glama
Hakowan
by Hakowan

Related Servers

Alternatives to hakowan-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Language-owned MCP gateway and execution-host coordination for Hara, exposing read-only tools for runtime introspection, evaluation, calls, and checks, with an optional deterministic test fixture for development.
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and software to create, edit, inspect, validate, and export CAD geometry through MCP using backend-neutral typed operations, with FreeCAD/OpenCascade as the authoritative B-rep backend and JSCAD preview.
      1
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Provides safe, deterministic inspection, transformation, validation, and diffing of structured data (JSON, CSV, YAML, Parquet) via schema-aware MCP tools.
      4
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents and MCP clients to perform 3D asset creation and verification: exact b-rep CAD, GLB validation with embedded certificates, mesh inspection, and physics scenes, with most tools running without Blender.
      36
      81 npm
      MIT

    TDQS

    B3.1/5.0

    Scored across 13 tools

    Disambiguation4/5

    The tools are mostly distinct by resource and action, especially the pipeline stages: validate, compile, observe, render, patch, and evaluate. The only mild ambiguity is among get_schema, get_spec_template, and get_spec, though their descriptions do enough to guide selection.

    Naming Consistency5/5

    Every tool follows a consistent verb_noun snake_case pattern, such as get_spec, validate_spec, compile_spec, and apply_patch. There are no vague single-word names or mixed conventions.

    Tool Count5/5

    Thirteen tools is within the ideal scope for a specification-and-rendering server. Each tool maps to a distinct stage in the workflow, from schema exploration and validation to rendering and patch evaluation.

    Completeness5/5

    The tool surface covers the full FigureSpec lifecycle: creation from templates, validation, retrieval, compilation, observation, rendering, patching, and visual evaluation. No critical workflow dead ends are evident for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues