Changelog.

Every fix and release, in the open.

Beta — small, careful, and shipping continuously. Newest first.

Fixes and releases, newest first. Package releases are also tagged on npm and GitHub.

Validation

Benchmarked against DeepMind's mathematics dataset

  • 10,000 nested arithmetic expressions from Google DeepMind’s mathematics_dataset (arithmetic module, test split), evaluated by all five engines: 10,000 correct answers, zero errors.
  • The rational-capable engines (FLINT, decimal, MPFI) returned the exact expected fraction on every single case — -3/17 means −3/17, not an approximation of it.
  • The floating-point engines (C++ double, NTL) agreed within their native precision, exact wherever the answer terminates — the expected, honest divergence between exact and floating arithmetic.
  • The reference answers come from DeepMind, not from us: an external check on the whole chain, from parser to printed result.
Engine

Exact complex rationals ℚ(i)

  • Exact arithmetic now extends to the complex plane on the rational-capable engines (FLINT, decimal, MPFI): (1+2i)/4 answers 1/4+i/2 — Gaussian rationals, no rounding at all while a value stays in ℚ(i).
  • The exact tower ℤ ⊂ ℚ ⊂ ℚ(i) is closed under +, −, ×, ÷ and exact comparisons; a value converts to floating point only when it leaves the tower (sqrt, sin, π, …).
  • Mixing exact and floating-point values ((1+2i)/4 + 0.5) converts the exact side at the operator, at native precision — no more rejected expressions at the ℚ(i)/ℝ boundary.
  • Every exact result is printed in a form you can paste straight back: 1/4+i/2 re-evaluates to exactly itself. An automated round-trip test now checks this across all five engines.
Engine

Exact rational arithmetic

  • Engines with a native rational primitive (FLINT, decimal, MPFI) now compute integer expressions in exact ℚ: 1/3 answers 1/3, 1/3 + 1/6 answers 1/2 — no rounding at all until a value leaves the rationals.
  • Exact comparisons on rationals: (1/3)*3 == 1 is a certain verdict, not a floating-point coincidence.
  • Division by an exact zero (1/0) is now a clear domain error on these engines — an exact type has no infinity to hide behind.
  • Engines without a rational primitive (C++ double, NTL) keep answering in their native floating point: the divergence between 1/3 and 0.333… is itself the signal.
Engine

Fifth engine: NTL

  • A fifth independent engine joins the panel: NTL (Victor Shoup) — arbitrary-precision binary floating point with an exact integer mantissa, computed at your requested precision.
  • Same catalog as the other engines: every function and operator, nothing disabled.
  • Point semantics with exact comparisons; when two values agree to within your requested digits, the verdict carries a within-precision diagnostic instead of silent confidence.
  • No infinities, no NaN: a singular input (like 1/0) returns an explicit error — an honest divergence from engines that answer inf.
MCP · 0.1.5

Discoverable without a key

  • The server now starts and lists its tools even with no API key set — the key is required only when a tool is actually called, so MCP registries can inspect the tool definitions. The missing-key case now returns a clear error instead of exiting silently.
MCP · 0.1.4

Framed for numeric verification

  • The evaluate tool is now described as a numeric-reliability check, not just a calculator — so the assistant reaches for it when a result must be trusted (catastrophic cancellation, branch cuts, floating-point-sensitive values) rather than computing the number itself.
MCP · 0.1.3

MCP follows the MPFI engine

  • The MCP server now reads the fourth engine as mpfi and the structured diagnostics array — the published 0.1.2 still expected the old interval/warnings shape.
Engine

New interval engine: MPFI

  • The interval engine now runs on MPFI (MPFR-backed) — multi-precision enclosures at your requested precision, not fixed double precision.
  • Rigorous transcendentals and outward-rounded bounds: the displayed interval always contains the true value.
  • A comparison it cannot certify (e.g. sqrt(2) == sqrt(2)) now returns a result plus a diagnostic instead of failing the request.
  • API: per-engine reliability signals are now in a single diagnostics array (the old warnings array is merged into it).
MCP · 0.1.2

MCP polish

  • Read-only annotations and clearer titles on both tools.
  • Sharper, engine-agnostic tool descriptions; precision capped at 50 digits.
  • README now credits the underlying open-source engines.
Web

New look & a security pass

  • New brand mark and social-share preview card.
  • Search-engine metadata: structured data, sitemap, and link previews.
  • Security hardening across the site and API (Content-Security-Policy, stricter headers).
Onboarding

Smoother Claude Desktop setup

  • Step-by-step Claude Desktop setup guide, with screenshots.
  • Your API key is now auto-copied to the clipboard the moment it is revealed.
MCP · 0.1.1

Instant API keys

  • Get a working API key in one click — no email or password required.
  • ultimath-mcp published to npm: one-line install for Claude Desktop.
Web

Faster site

  • Rebuilt the landing as a static site for near-instant loads.
  • Live in-page demo running against the real API.
Engine

More functions, clearer errors

  • Added round and trunc — 30 functions, identical across all four engines.
  • Clearer error messages with “did you mean…?” suggestions.
  • Core constants (π, e, φ, …) cross-checked against Wolfram.

Last updated: July 2026