AgentStack MCP
Related Servers
Alternatives to AgentStack MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceA deterministic what-if scenario simulation MCP server that projects business metrics over time with exact decimal arithmetic, offering sensitivity analysis and break-even solving.625 npmMIT
- AlicenseAqualityAmaintenanceAn MCP server that provides deterministic, high-precision business, finance, and operational calculations such as SaaS metrics, currency conversion, business days, and financial formulas, returning structured JSON results.1130 npmMIT
- AlicenseNot gradedqualityDmaintenanceAgent-to-agent reasoning-as-a-service providing structured reasoning, data analysis, decision support, and code/document review via REST API and MCP protocol.MIT

Sablier MCP Serverofficial
AlicenseAqualityDmaintenanceAn MCP server that lets AI assistants analyze portfolios, stress-test scenarios, generate synthetic market paths, and scan SEC filings — in under 2 minutes.833MIT
Cruxible Coreofficial
AlicenseNot gradedqualityAmaintenanceDeterministic decision engine with DAG-based receipts. Build entity graphs, query with MCP, get auditable proof.17Apache 2.0- AlicenseNot gradedqualityCmaintenanceEnables financial modeling for SaaS and other assets via MCP tools, including simulation, scenario comparison, sensitivity analysis, semantic knowledge search, and persistent context memory.MIT
TDQS
Scored across 24 tools
Most tools are cleanly separated by domain prefixes (sim_, decide_, calc_) with distinct actions. However, decide and decide_score have overlapping outputs, and calc_metric overlaps conceptually with specific calc_npv and calc_irr tools, creating potential confusion.
Domain prefixes give structure, but the suffixes mix verbs and nouns inconsistently (sim_run vs sim_sensitivity, calc_metric vs calc_list_metrics). Composite tools use a completely different naming style, breaking the pattern.
At 24 tools, the server is on the heavy side, but the three domains each justify several tools. Some redundancy (decide vs decide_score) could reduce the count, making it borderline.
Core workflows for simulation, decision, and calculation are well covered, including composite tools that span domains. Minor gaps exist, such as no way to create or edit scenario templates and no persistence for decisions, but these are not critical.