Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Valuation MCP: DCF/NAV/CCA, WACC, derivatives, credit risk, fixed income, structured products.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://fair-value.ascent-partners.com/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"fair-value": {
"command": "uvx",
"args": [
"fair-value",
"fair-value-mcp"
]
}
}
}Run this in your terminal
claude mcp add --transport http fair-value https://fair-value.ascent-partners.com/mcpclaude mcp add fair-value -- uvx fair-value fair-value-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"fair-value": {
"url": "https://fair-value.ascent-partners.com/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"fair-value": {
"command": "uvx",
"args": [
"fair-value",
"fair-value-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"fair-value": {
"type": "http",
"url": "https://fair-value.ascent-partners.com/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"fair-value": {
"type": "stdio",
"command": "uvx",
"args": [
"fair-value",
"fair-value-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://fair-value.ascent-partners.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The publisher (ascent-partners.com) is not the repo owner (simonmak-ascent); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (0.2.7) reached the registry 23 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, MCP Server Autocad Lisp Helper
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
High-precision static analysis and debug server for AutoCAD AutoLISP (.lsp) files.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Professional financial valuation system for OpenCode with IFRS/IVS compliance.
mcp-name: com.ascent-partners/fair-value
A single valuation core — exposed as an MCP server, a REST API, and a Python library — whose **14 native calculate_* tools / 135 methods cover corporate, startup, and intangible valuation aligned to IVS 2025 and IFRS/IAS**:
Every result is a deterministic-first envelope carrying the centre value, solution_type, statistics (σ / percentiles, and seeded samples for the few stochastic methods), and citations resolving to verbatim IVS/IFRS clauses. 120 / 135 methods carry standards citations and the taxonomy has 0 orphan clauses, enforced by a conformance gate in CI.
Fastest path — no install:
https://fair-value.ascent-partners.com/mcphttps://fair-value.ascent-partners.com/v1/healthhttps://fair-value.ascent-partners.com/uvx --from "fair-value[mcp]" fair-value-mcpThen call any of the 14 calculate_* tools (add -help / help=true for the generated transparency record). Client config: MCP Server.
flowchart LR
CLIENT["AI agent / OpenCode"] -->|"stdio (uvx) or Streamable HTTP"| MCP["fair-value-mcp 14 calculate_* tools · 135 methods"] HOST["Hosted · fair-value.ascent-partners.com docs/landing at / · MCP at /mcp · REST at /v1"] --> CLIENT MCP --> REG["method-spec registry (valuation://methods)"] REG --> STD["standards taxonomy + corpus IVS 2025 · IFRS/IAS · (valuation://standards)"] REG --> CORE["valuation engine DCF · NAV · CCA · WACC (FF5) · derivatives credit risk · actuarial"] CORE --> DATA["inputs from apdb-etl (cited)"] CORE --> ENV["result envelope value + statistics + citations"]
pip install -r requirements.txt # dev workflow
pip install . # base library pip install ".[mcp]" # + MCP server dependencies (fastmcp)
The console command fair-value-mcp runs the MCP server (stdio; add --http for Streamable HTTP).
# run locally without installing (stdio)
uvx --from "fair-value[mcp]" fair-value-mcp
pip install "fair-value[mcp]" fair-value-mcp # stdio fair-value-mcp --http # Streamable HTTP
The server exposes 14 native calculate_* tools spanning DCF, cost of capital, market multiples, residual/asset valuation, options, expected value, credit risk, actuarial PV, sector metrics, fair-value adjustments, convertible bonds, structured products, loss-making companies, and fixed income — all derived from one method-spec registry. Add -help to any tool (or help=true) for its generated documentation with formula reference, inputs, and governing clauses.
Adoption target: ≥ 100 PyPI downloads and ≥ 1 directory listing within 90 days of the first release (tracked via the PyPI stats API and the directory listing).
The same core is exposed at /v1 (served next to MCP by mcp_server.asgi:app):
curl -s localhost:8000/v1/health
curl -s -X POST localhost:8000/v1/calculate/calculate_dcf \ -H 'content-type: application/json' \ -d '{"method":"dcf","cash_flows":[100,110],"discount_rate":0.1}'
Endpoints: /v1/health, /v1/tools, /v1/methods, /v1/standards, /v1/openapi.json, /v1/docs (Swagger UI), /v1/help/{tool}, POST /v1/calculate/{tool}. See REST API.
The hosted domain serves a Next.js frontage — landing, complete docs, methods catalogue (one page per method), standards browser, and an API playground — alongside the MCP/REST function in one Vercel project. It is data-driven: the catalogue is generated from the registry at build time (scripts/gen_web_data.py → data/catalog.json).
pnpm install
pnpm dev # http://localhost:3000 (expects /v1 from the API for the playground) pnpm build # prebuild regenerates data/catalog.json pnpm typecheck && pnpm lint
Routing: / and /docs/* are Next.js; /mcp and /v1/* are rewritten to the Python function (api/index.py). The frontage is localized — en at /, zh at /zh, hk at /hk — via per-locale root layouts with hreflang.
from valuation_engine import run_valuation
result = run_valuation('9988.HK', 'dcf') # DCF valuation (shared envelope)
The standards alignment is data, not code: standards/taxonomy.json maps each method to its IVS and IFRS/IAS clauses, standards/source/*.md holds the verbatim clause text (with standards/provenance.json recording edition and source), and standards/coverage-baseline.json is the coverage ratchet. The engine attaches solution_type and citations to every envelope, and scripts/check_conformance.py fails CI if a published method loses its citation or the taxonomy/corpus drifts. See Standards reference.
flowchart LR
SEED["method_spec_seed.py method tables · 135 methods"] --> SPEC["method_spec.py parameter vocabulary"] SPEC --> SURF["tool_surface.py 15 calculate_* tools"] SPEC --> STD["standards.py taxonomy · citations"] SURF --> SRV["server.py (FastMCP)"] SRV --> STDIO["stdio · uvx fair-value-mcp"] SRV --> HTTP["Streamable HTTP · fair-value-mcp --http"] ASGI["asgi.py (+ rest.py, openapi.py)"] --> HOST["Hosted · / + /v1"] SRV --> DOCS["docs.py -help transparency records"] STD -.->|resources| RES["valuation://methods · valuation://standards"] SRV -.-> DOCS
src/ ├── constants.py # standards references ├── valuation/ # DCF, NAV, CCA, asset standards (relief-from-royalty, MPEEM, residual) ├── cost_of_capital/ # WACC, FF5, KMV ├── credit_risk/ # ECL, PD/LGD, CVA/DVA ├── derivatives/ # options, swaps, convertible bonds, structured products, fixed income └── output/ # shared result envelope (value + statistics + citations) mcp_server/ ├── method_spec.py + method_spec_seed.py # single source of truth for tools/methods ├── standards.py # taxonomy loader, citations, coverage ├── tool_surface.py · engine.py · handlers.py · server.py ├── docs.py · rest.py · openapi.py · asgi.py └── catalog.py · prompts.py # valuation:// resources + guided prompts standards/ # taxonomy.json · source/*.md · provenance · baseline scripts/ # check_conformance.py · gen_docs.py
sequenceDiagram
autonumber participant C as MCP / REST / Python caller participant E as validation + dispatch participant R as method-spec registry participant S as standards taxonomy participant M as computation modules (src/) participant O as output envelope C->>E: calculate_*(...) / POST /v1/calculate/* E->>R: resolve method + validate parameters (no defaults) R-->>E: method spec E->>M: dispatch to valuation / cost_of_capital / credit_risk / derivatives E->>S: attach solution_type + citations M-->>E: value + steps + assumptions E->>O: ok() / error() envelope (value · statistics · citations) O-->>C: status · method · value · statistics · assumptions · citations · disclaimer
CI and deployment run through the APG workbench pipeline.
mkdocs build (see mkdocs.yml); method reference auto-generated by scripts/gen_docs.pySKILL.md — capability spec; valuation://methods / valuation://standards — machine-readable cataloguesReleased under the MIT License.