hakowan-mcp
OfficialRelated Servers
Alternatives to hakowan-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceLanguage-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.4Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables LLM and agent hosts to create and manipulate structured game-art documents through typed deterministic MCP operations, render them to SVG/PNG, validate output, inspect visuals, and make targeted edits toward reproducible, game-ready assets.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables 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.1Apache 2.0
- AlicenseAqualityBmaintenanceProvides safe, deterministic inspection, transformation, validation, and diffing of structured data (JSON, CSV, YAML, Parquet) via schema-aware MCP tools.4Apache 2.0
- AlicenseNot gradedqualityBmaintenanceThis MCP server enables clients and agents to validate, compile, inspect, audit, and export hash-locked video production context packs and evidence-chain job records, with optional ComfyUI or HTTP API generation when explicitly invoked.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI hosts to retain evidence, check explicit constraints, plan bounded work, and record outcomes through local-first MCP operations. Optional reconstruction tools also support experimental image-to-3D workflows with local model providers and Blender.68 npmMIT
TDQS
Scored across 13 tools
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.
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.
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.
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.