Epoch
Related Servers
Alternatives to Epoch
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for estimating LLM token consumption and costs from project documents, code, and materials. Provides 8 tools including project budget planning, token/cost estimation, GitHub repo analysis, and pricing refresh.MIT
- AlicenseAqualityCmaintenanceMCP server that scores tool descriptions, estimates token costs, simulates agent tool selection, and generates reliability reports to help AI agents choose the right tools and reduce wasted tokens.59 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to produce calibrated time estimates by mining your own finished session history, estimating whole multi-step plans over dependency-aware schedules, recording actuals to correct later forecasts, and backtesting the numbers against past sessions. Runs locally over Claude Code transcripts or Cortex databases, giving quantile ranges (P50/P80/P95) with confidence labels instead of human-timeline guesses.MIT
- AlicenseNot gradedqualityDmaintenanceThe Time MCP Server is a Model Context Protocol (MCP) server that provides AI assistants and other MCP clients with standardized tools to perform time and date-related operations. This server acts as a bridge between AI tools and a robust time-handling back167 npm25MIT
- AlicenseNot gradedqualityDmaintenanceFull autonomous project management MCP server enabling AI assistants to manage projects, sprints, tasks, bugs, proposals, and team collaboration via natural language.10 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables agile sprint backlog velocity calculation and milestone completion prediction for Linear, integrating with MCP-compatible clients through a zero-dependency Python server.-
TDQS
Scored across 26 tools
Several tools genuinely overlap: cocomo_validate vs cocomo_ground_truth, token_time_bridge vs token_cost_estimate, record_actual vs batch_record_actuals, and time_math which explicitly re-dispatches to convert_timezone/parse_duration/add_business_days/count_business_days. The descriptions do a good job of naming the sibling tool and when to prefer each, and estimate_from_context clearly states it delegates to reference_class_estimate, so an agent can usually resolve the choice — but it must read the description every time rather than relying on distinct surfaces.
All names are snake_case with no camelCase leakage. There is a mild split between subject-first estimation names (cocomo_estimate, pert_estimate, sprint_forecast, monte_carlo_schedule, token_cost_estimate) and verb-first utility names (get_current_time, add_business_days, compare_models, calibrate_estimates), plus a small inconsistency between record_actual and batch_record_actuals — readable but not a single uniform verb_noun pattern.
26 tools is heavy for what is essentially an estimation + time-math + token-economics server, and the count is inflated by redundancy rather than breadth: two COCOMO validators, two token-time tools, time_math duplicating four single-purpose time tools, and record_actual alongside batch_record_actuals. Trimming the overlap could bring this to a much tighter 15-18 tool surface without losing capability.
The domain lifecycle is well covered: multiple estimation strategies (PERT, COCOMO II, reference-class, Monte Carlo, critical path, sprint forecast), a full feedback loop (record_actual, batch_record_actuals, get_pending_estimates, calibrate_estimates, feedback_health, accuracy_trend), risk assessment, and supporting time arithmetic. Minor gaps remain — there is no way to list, inspect, or correct/delete an existing estimate or submitted actual, only add new feedback.