mcp-registry/io.github.sicxz/axcess/evaluate_typography / alternatives
mcp-registry/io.github.sicxz/axcess/evaluate_typographyThe best live alternatives to mcp-registry/io.github.sicxz/axcess/evaluate_typography right now are mcp-registry/io.github.digbyo/colour-memory/accessibility_check, mcp-registry/io.standoutmcp/standout/critique_design, mcp-registry/io.github.digbyo/colour-memory/accessibility_font, mcp-registry/online.jinero/jinero/check_contrast, mcp-registry/com.googleapis.design/mcp/typeset — capability-matched and ranked by current reliability. mcp-registry/io.github.sicxz/axcess/evaluate_typography itself is currently "healthy".
mcp-registry/io.github.digbyo/colour-memory/accessibility_check is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.standoutmcp/standout/critique_design, mcp-registry/io.github.digbyo/colour-memory/accessibility_font, mcp-registry/online.jinero/jinero/check_contrast, mcp-registry/com.googleapis.design/mcp/typeset. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.sicxz/axcess/evaluate_typography's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.sicxz%2Faxcess%2Fevaluate_typography.
By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.sicxz%2Faxcess%2Fevaluate_typography
or MCP find_alternatives. Check mcp-registry/io.github.sicxz/axcess/evaluate_typography's live status: https://glimind.com/tool/mcp-registry/io.github.sicxz/axcess/evaluate_typography.