Loading ToolBench

Reading the current corpus…

hex-core MCP server · F · ToolBench

hex-core

Universal MCP server for Hex Core — runs on Claude Code, Cursor, Continue, Gemini CLI, ChatGPT Desktop, and Zed. 19 tools over the component registry. Thin transport shell — pure-function builders live in @hex-core/payload.

2026-07-28+STDIO2 tools

38/100

Definition Quality48

Protocol Readiness0

Supportability47

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

This is not an MCP server, it is a React component library (Hex Core) with UI components for AI applications. The two 'tools' listed (tool-call, composer) are React component definitions, not MCP tool definitions. They lack MCP registration, are not callable via the MCP protocol, and exist only as TypeScript/React code in a monorepo. The schema definitions shown are React prop interfaces, not MCP input schemas. No actual MCP server implementation is present in the source.

Tools (2)

composerread onlysource verified48/100

Multi-line input + submission shell for chat. Submits on Enter (Shift+Enter inserts newline). Trailing slot for attachment + send buttons.

tool-callread onlysource verified48/100

Collapsible card showing a tool/function invocation — name, lifecycle state badge, expandable args + result body.

Issues (5)

CRITICALtool ↗

Not an MCP server. Hex Core is a React component library, not a Model Context Protocol server. The 'tools' are React components with prop interfaces, not MCP-callable tools.

tool-callcomposer

CRITICALtool ↗

No MCP tool registration visible. Tools are not registered via MCP SDK (no Server.tool() calls, no tool definitions in MCP protocol format).

tool-callcomposer

CRITICALtool ↗

Schemas are React prop interfaces, not MCP input schemas. They use React-specific types (ReactNode, function callbacks) incompatible with MCP protocol.

tool-callcomposer

HIGHtool-description ↗

No error handling, no output schema documentation, no pagination support. Descriptions lack WHEN/WHY context for LLM selection.

tool-callcomposer

HIGH

Recommendations

Clarify: Is this repository intended to be an MCP server? If yes, implement actual MCP tool definitions using the mcp-sdk (Server.tool() registration with proper JSON Schema input/output).
If this is a component library only, remove the 'MCP server' claim from the repo description. Hex Core appears to be a UI component library for AI applications, not an MCP server.
If you intend to expose Hex Core components as MCP tools, create a separate MCP server package that wraps the components and exposes them via the MCP protocol with proper tool definitions.
Add comprehensive tool descriptions explaining WHAT each tool does, WHEN to use it, and WHAT it returns. Current descriptions are UI-focused, not LLM-selection-focused.
Document output schemas for all tools. Specify what fields are returned, their types, and what downstream tools can consume them.

Score history

Overall score trend

First recorded score · v2 rubric

38/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	38	2026-07-28+	v2