blacksmith-mcp
Related Servers
Alternatives to blacksmith-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables querying Rybbit Analytics data directly through MCP-compatible clients like Claude Code. It provides tools for monitoring website statistics, user sessions, error logs, funnels, and performance metrics via natural language.4013 npm4MIT
- AlicenseBqualityDmaintenanceEnables querying Langfuse analytics, cost metrics, and usage data across multiple projects. Provides tools for trace analysis, model/service cost breakdowns, and daily usage trends through natural language queries.2430 npmMIT
- FlicenseNot gradedqualityCmaintenanceProvides GitHub repository analysis tools for Claude, including repo summaries, commit history, issue tracking, contributor stats, and code quality assessment. Enables natural language queries about code quality, contributor activity, and repository comparisons.-
- FlicenseNot gradedqualityDmaintenanceProvides statistical analysis and usage tracking for Claude Code, enabling users to query daily/monthly stats, compare users, analyze trends, detect anomalies, and generate usage reports through natural language.1-
- FlicenseNot gradedqualityCmaintenanceProvides access to PyTorch CI/CD analytics data including workflows, jobs, test runs, and log analysis through an MCP interface.4-
- AlicenseAqualityCmaintenanceExposes analytics from Claude Code transcripts as MCP tools, enabling cost, audit, safety, and efficiency queries through natural language.4MIT
TDQS
Scored across 37 tools
Most tools have distinct purposes (runs, jobs, tests, usage, logs, etc.), but there are several test-related tools (get_failed_tests, get_failures_by_pattern, get_flaky_tests, get_slow_tests, get_test_history) that could cause confusion despite detailed descriptions.
The predominant pattern is 'get_*', but there are exceptions like 'list_jobs', 'list_orgs', 'list_runs', 'compare_test_runs', and 'search_logs', mixing verbs and styles.
With 37 tools, the server is overloaded for a CI analytics domain. While each tool has a clear purpose, the sheer number can overwhelm agents and suggests insufficient consolidation.
The tool surface covers monitoring, debugging, and analytics (runs, jobs, tests, logs, cache, usage) well, but lacks management actions like triggering runs or updating settings, leaving the domain partially incomplete.