mcp-abacus
Related Servers
Alternatives to mcp-abacus
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceAn MCP server that performs exact arithmetic calculations, avoiding the pitfalls of float64 and unsafe eval, with resource limits for safe execution.166 PyPIMIT
- AlicenseBqualityDmaintenanceHigh-precision mathematics server for MCP clients, providing exact integer arithmetic, symbolic derivatives, and numerical calculus via LaTeX-style input.65 npm2MIT
- AlicenseAqualityDmaintenanceA stdio MCP server that gives LLMs a safe scientific calculator with infix math, complex numbers, matrices, statistics, unit conversions, and more via tools that return JSON.331MIT
- AlicenseAqualityCmaintenanceSafe MCP server for math operations: evaluate, simplify, and differentiate expressions with configurable precision, using a sandboxed worker thread and strict AST allowlist to block dangerous input.3MIT
- FlicenseNot gradedqualityCmaintenanceA Python-based MCP server that provides mathematical tools like addition and random number generation, plus server metadata.-
- AlicenseAqualityDmaintenanceMCP server for deterministic numeric verification and spreadsheet auditing. Enables AI agents to verify math/finance claims, audit rows, and evaluate covenant rules with signed, independently checkable receipts.4MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct action: calculate evaluates, analyze returns the parse tree, solver finds roots/extrema, curve_fit fits curves, help returns reference text, and info reports server state. The descriptions explicitly cross-reference one another ('for just the final value use calculate; to find variable values use solver'), making boundaries unambiguous even though they share an expression language.
Names mix conventions: verbs (calculate, analyze), nouns (info, solver, help), and snake_case (curve_fit). All are lowercase and readable, but there is no single predictable verb_noun pattern, so an agent cannot infer a naming rule.
Six tools is well-scoped for a numeric evaluation server, with each tool earning its place: value evaluation, AST debugging, solving, curve fitting, and two support tools (help, info). No redundant or filler tools.
The surface covers the full lifecycle of its domain: evaluate (calculate), inspect/debug (analyze), solve (solver), fit (curve_fit), plus discovery (help) and status (info). Minor gaps exist—no explicit unit conversion or matrix/statistics operations—but core numeric workflows are fully covered.