Release notes

v1.0 — first public release

Everything built since inception, shipped as one release: an MCP-native valuation app for wealth-management practices. Agents gather the facts from the platforms you already run, ValuationMCP supplies the benchmarks and the math.

MCP server

The primary interface to ValuationMCP. Agents connect over Streamable HTTP at /mcp and authenticate with OAuth 2.1, so every tool call runs as the signed-in user.

  • OAuth 2.1 authorization with dynamic client registration, an in-app consent screen, and per-user scoping on every read and write.
  • `list_practices` — enumerate the practices on the account with current data coverage.
  • `upsert_practice` — create a practice or merge newly gathered facts into one; omitted fields are left untouched.
  • `list_data_requirements` — the full checklist of facts a valuation needs, which method each fact drives, and which kind of platform normally holds it.
  • `record_data_source` — log provenance: which platform supplied which field, and when.
  • `get_benchmarks` — sourced SEC Form ADV percentiles and published operating medians for sanity-checking gathered figures.
  • `compute_valuation` — run the blend and save the result, returning every method's arithmetic, the quality multiplier, the weighted blend, and the headline.
  • Raw-metric intake: recurring revenue %, organic growth %, retention %, average client age, top-10 revenue share %, and advisor tenure are converted to the six 0–100 quality scores server-side with fixed, published anchors, so identical inputs always score identically across runs and clients.
  • Composite quality factors: `quality_longevity` is a succession-readiness score weighted across successor presence, written plan, funded buy-sell, owner relationship share, advisor tenure, and years to retirement; `quality_demographics` blends average client age with the asset-weighted decumulator share.
  • Server-side derivation of `value_per_client`: capitalizes revenue per household at the firm's revenue multiple, falling back to the tier median when the firm's own figures are missing, so agents no longer invent a capitalization factor.
  • Server instructions that steer agents away from inventing figures — a missing field lowers reported data confidence instead of producing a confident-looking guess.

Valuation engine

Seven methods, each reported with the arithmetic behind it, blended by a normalized weighted mean.

  • Revenue Multiple, EBITDA Multiple, EBOC Multiple, Discounted Cash Flow, Client Value, AUM Percentage (1.5% base × quality), and Comparable Transactions (2.2× revenue × quality).
  • Six-factor quality multiplier — recurring revenue mix, organic growth, client retention, client demographics, concentration, and succession longevity — clamped to 0.5×–1.5×, with each factor shown at its point of effect.
  • User-adjustable method weights plus a "weight by data confidence" preset that loads each method's own confidence score into the weight vector (same normalized-mean math, different weights).
  • Per-method data-confidence scoring and a weighted coverage score so a thin dataset produces a visibly low-confidence valuation.
  • Sell-side headline: a defensible suggested asking price set above the fair-value blend, with the low/high range across contributing methods.
  • Client Value method can use a server-derived value per client when the user does not supply one.
  • Manual Workbench for exploring the same math by hand, available to signed-in accounts.

Benchmarks

Only sourced figures — no invented industry data.

  • SEC IAPD Form ADV panel derived from the official SEC compilation feed covering 23,512 registered investment adviser firms, with firm-size and client-mix percentiles.
  • Published industry operating medians (revenue per client, operating profit margin) used for tier-aware starting points.
  • Transaction multiples are explicitly left as user-editable inputs, because neither benchmark source publishes deal multiples.
  • Benchmark and industry panels surface the source and attribution next to every figure.

Accounts and workspace

Registration gates the MCP server and the valuation surfaces.

  • Email and Google sign-in, with a workspace portal that shows connection status and recorded valuations.
  • Connection guide mapping wealth-tech platforms — CRM, portfolio accounting, custodian, billing, accounting, payroll — to the exact fields they supply.
  • Supported MCP servers directory with a dedicated page per server covering hosting, authentication, and which valuation fields it can feed.
  • Recorded-valuation history with labels, notes, provenance summary, and delete.

Admin

Output-only oversight across accounts.

  • Valuation ledger showing each account that ran a valuation, the provenance of its data, and the calculated results — never the input data.
  • Cross-firm averages across every valuation calculated in the app.
  • Management of recorded valuations, and a contact-form inbox with reply and delete.
  • Client/Admin mode switch inside the logged-in workspace.

Brand, site and privacy

  • ValuationMCP identity on valuationmcp.ai: light and dark logo treatments, favicon and touch icon, blue-violet brand palette and gradients drawn from the mark.
  • Dark mode by default with a light/dark toggle that persists.
  • Landing page positioned as an MCP-native valuation app built for wealth management, with a standardized footer across every page.
  • Contact form that routes inquiries without exposing an email address.
  • Privacy policy documenting the core commitment: data pulled from other MCP servers is never synced into ValuationMCP. Only provenance and calculated outputs are stored, and rights are limited to aggregated, de-identified benchmarks.

Known limits in v1.0

  • Sell-side only. Buy-side framing and target discovery are intentionally out of scope for this release.
  • Transaction multiples are inputs, not benchmarks — set them from deal data you trust.
  • Long-running agent work is not exposed as a single MCP call; heavy steps run inside the app.

Browse the supported MCP servers or read the privacy policy.