F
licenseNot graded
qualityD
maintenanceProvides D3 visualization documentation, chart recommendations, and code generation through the MCP protocol.
18
-
nteract/semiotic
by nteract
Related Servers
Alternatives to nteract/semiotic
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for creating interactive Vega-Lite data visualizations that render inline in chat via MCP Apps.21MIT
- AlicenseAqualityAmaintenanceMCP server that turns AI into an SVG artist. One rendering engine with a rich JSON schema, AI controls all design parameters. Renders animated SVGs with CSS @keyframes and SMIL animations. Supports 16+ element types, parametric curves, pattern groups, gradient/filter/clip/mask definitions, and PNG preview. No external dependencies, runs locally via npx.381 npm22MIT
- AlicenseAqualityBmaintenanceAn MCP server that lets agents draw 18 diagram types from JSON (no SVG, no headless browser)225 npm10MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for creating and manipulating generative art with p5.js, Three.js, GLSL, Canvas2D, and SVG, featuring workspace management, parameter control, and screenshot capture.78 npmMIT
- FlicenseNot gradedqualityFmaintenanceA Model Context Protocol (MCP) server implementation that provides the LLM an interface for visualizing data using Vega-Lite syntax.100-
TDQS
A3.8/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: diagnoseConfig for configuration validation, getSchema for component schema retrieval, renderChart for SVG chart generation, reportIssue for GitHub issue creation, and suggestChart for chart type recommendations. There is no overlap or ambiguity in their functions.
Naming Consistency4/5
The naming follows a consistent verb_noun pattern (e.g., diagnoseConfig, getSchema, renderChart, reportIssue, suggestChart), with all tools using camelCase. However, the pattern is slightly inconsistent as some tools use verb+noun (e.g., renderChart) while others use verb+noun combinations that are less standard (e.g., diagnoseConfig, reportIssue), but overall it remains readable and predictable.
Tool Count5/5
With 5 tools, this server is well-scoped for its purpose of chart configuration and rendering in Semiotic. Each tool serves a specific role in the workflow, from diagnosis and schema retrieval to rendering and issue reporting, making the count appropriate and efficient.
Completeness4/5
The tool surface covers the core chart lifecycle: diagnosis, schema exploration, rendering, issue reporting, and chart type suggestion. Minor gaps exist, such as the lack of tools for updating or deleting chart configurations, but these are not critical for the server's stated purpose, and agents can work around them effectively.
Maintenance
ActivityActive
ResponsivenessWithin a week