v0.6.0 — eight engines

Every expression is now evaluated by eight independent engines, and every result carries the name of the engine that produced it.

pari, ntl and symengine were already answering — the client just did not know them: they fell through the fallback path, returned unlabelled and out of order, while the tool description still announced five. Engine labels are now derived in code, so the next engine is a one-line change.

The eight: exact symbolic · multiprecision balls · interval · arbitrary-precision binary floats · PARI/GP (built without GMP) · NTL RR · deferred symbolic (rewrites before evaluating) · IEEE-754 double.

Also included, never released here (0.3.0): symbolic / symbolic_latex in the output schema — the closed form, published when the printed digits are only a truncation of it — and the per-engine exact / digits precision contract.

Published on npm as ultimath-mcp@0.6.0.

0.2.0 — Fifth engine: NTL

A fifth independent engine joins the panel: ntl — NTL (Victor Shoup), arbitrary-precision binary floating point with an exact integer mantissa, computed at your requested precision.

• Same function catalog as the other engines — nothing disabled.
• Exact comparisons, with a within-precision diagnostic when two values agree to (almost) all of your requested digits.
• No infinities, no NaN: singular inputs (like 1/0) return an explicit error — an honest divergence from engines that answer inf.
• evaluate now shows five columns (flint, dec, cpp, mpfi, ntl); structuredContent carries the new engine automatically. No client-side change required.

v0.1.5

Require the API key at call time, not at startup.

The server now starts and lists its tools even with no API key set —
the key is enforced only when a tool is actually called. This lets MCP
registries inspect the tool definitions. Missing-key now returns a
clean error instead of a silent exit.