tif-score-mcp
Related Servers
Alternatives to tif-score-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server for n8n that gives AI agents tools for generating workflows, linting, diagnosing failed executions, and driving live n8n instances.1247 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides AI assistants with access to documentation, schemas, and operations for over 535 n8n workflow automation nodes. It enables models to understand, create, and manage n8n workflows through natural language by connecting to the n8n API.77,070 npmMIT
- AlicenseAqualityAmaintenanceAn MCP server that turns deployed n8n workflows into callable tools for AI agents, enabling discovery and execution of tagged workflows via a standard interface without rewriting integrations.412 npmMIT
- AlicenseBqualityDmaintenanceA comprehensive MCP server that provides full control over n8n automation workflows through natural language. It offers 43 tools for managing workflows, executions, credentials, and data tables, with safety features like write-mode protection and double-validated workflow creation.431MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for integrating with n8n, enabling workflow automation and management through natural language.205 npm1MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server for N8N that allows users to build, manage, and execute workflows through natural language, with 18 tools covering CRUD, execution, and intelligent workflow construction using templates, scaffolds, or LLM-based generation.64 npmMIT
TDQS
Scored across 3 tools
get_lead_score and score_conversation both analyze call transcripts and clearly overlap — get_lead_score even notes it runs the same analysis as score_conversation. This creates real ambiguity about which to call. diagnose_workflow_error is completely distinct, but the two scoring tools blur boundaries significantly.
Tools use a consistent verb_noun pattern (get_lead_score, diagnose_workflow_error, score_conversation) with snake_case throughout. The naming styles are readable and consistent, though the verbs are somewhat varied (get, diagnose, score). No mixing of case conventions or chaotic patterns.
Three tools is at the thin end but not necessarily inappropriate. However, two of the three tools (get_lead_score and score_conversation) perform overlapping transcript analysis, making the actual distinct tool surface effectively two tools. The scope is unclear — the server mixes transcript scoring with completely unrelated n8n workflow diagnosis, suggesting no coherent singular purpose.
The transcript-analysis side lacks balance: it covers extraction and scoring but has no update, correction, or batch-processing capability. The n8n workflow tool appears to be an orphan — a single diagnostic tool with no companion tools for related functionality. The two unrelated domains each feel incomplete, and the overall surface has no clear lifecycle coverage.