agentladle-mcp-reoi
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@agentladle-mcp-reoiRun REOI valuation for AAPL: sales 1000, WACC 10%, terminal growth 3%"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
AgentLadle MCP REOI
δΈζ | English
A Model Context Protocol (MCP) server for Residual Operating Income (REOI) Valuation, built with Python and FastMCP.
π Financial Data & Valuation Engine β A professional quantitative analysis tool for Residual Operating Income modeling.
It enables AI assistants (like Claude, Cursor, etc.) to perform multi-stage residual income projections, discounting, and enterprise value bridging analysis via standardized data input interfaces.
Features
1 Professional MCP Tool providing comprehensive financial valuation capabilities.
Standardized REOI Framework, incorporating base period analysis, forecast period discounting, and terminal value estimation.
Multi-stage Profit Forecasting, allowing independent revenue growth rates and operating margins configuration for each year.
Smart Markdown Formatting, returning not only precise valuation figures but also built-in markdown tables for elegant rendering inside LLM clients.
Zero Configuration Installation β Add one line to your MCP client without cloning or manual setup.
Pure Python, cross-platform (Windows / macOS / Linux).
Related MCP server: SSCMFI Bond Analytics MCP Server
Prerequisites
Python 3.10+ β Download Python
uv β Install uv
Tip: After installing uv, restart your terminal and MCP client (e.g., Claude Desktop) to ensure the
uvcommand is recognized.
Quick Start
Add the following to your MCP client configuration (Claude Desktop, Cursor, etc.):
{
"mcpServers": {
"agentladle-mcp-reoi": {
"command": "uvx",
"args": ["agentladle-mcp-reoi"]
}
}
}That's it. uvx automatically downloads the package and its dependencies from PyPI β no cloning, manual installation, or path configuration required.
Alternative: pip install
If you prefer managing the environment yourself:
pip install agentladle-mcp-reoiThen configure:
{
"mcpServers": {
"agentladle-mcp-reoi": {
"command": "agentladle-mcp-reoi"
}
}
}Alternative: Run from Source (Local Dev)
Clone the repository and run directly:
git clone https://github.com/agentladle/mcp-reoi.gitConfigure your MCP client:
{
"mcpServers": {
"agentladle-mcp-reoi": {
"command": "uv",
"args": ["run", "--directory", "/path/to/mcp-reoi", "agentladle-mcp-reoi"]
}
}
}Replace /path/to/mcp-reoi with the actual path to the cloned repository.
Tool List
# | Tool | Description |
1 |
| Residual Operating Income valuation model. Outputs value per share and detailed breakdown based on financial statements and assumptions. |
Tool 1: reoi_valuation_model
Calculates enterprise equity value and suggested value per share by taking base period financial data and future forecast assumptions.
Parameter List (request object)
Parameter | Type | Required | Description |
| string | Version, default "1.0" | |
| string | Stock ticker | |
| string | Company Name | |
| string | Currency, default "CNY" | |
| object | β | Base period financial data |
| object | β | Valuation parameters |
| object | Optional market consensus data | |
| object | Optional forecast assumptions |
baseData object
Parameter | Type | Required | Description |
| float | β | Total Assets (millions) |
| float | β | Financial Assets (millions) |
| float | β | Total Liabilities (millions) |
| float | β | Financial Liabilities (millions) |
| float | β | Preferred Stock Value (millions) |
| float | β | Minority Equity (millions) |
| float | β | Base Period Sales (millions), must be > 0 |
| float | Base Period Operating Profit (millions) | |
| float | Base Period Core Profit (millions) | |
| float | Base Period Sales Growth Rate | |
| float | Base Period Operating Margin | |
| float | β | Total Shares Outstanding (millions), must be > 0 |
parameters object
Parameter | Type | Required | Description |
| int | Number of Forecast Years (default: 5) | |
| float | β | Discount Rate/WACC, e.g., 0.10 for 10% |
| float | β | Terminal Growth Rate, e.g., 0.03 for 3% |
marketConsensus object (Optional)
Parameter | Type | Required | Description |
| float[] | Array of annual revenue consensus | |
| float[] | Array of annual EPS consensus |
assumptions object (Optional)
Parameter | Type | Required | Description |
| float[] | Array of annual revenue growth rates | |
| float[] | Array of annual operating margins |
Data Flow
Model Input (Financials & Assumptions)
β
βΌ
Input Validation
β
βββ 1. Derive Base Net Operating Assets (NOA) and Asset Turnover
β
βββ 2. Forecast Period Projection (Compute sales, OI, ending NOA, residual income)
β
βββ 3. Terminal Value Calculation (Compute terminal value and discount to present)
β
βββ 4. Value Bridging (Core operating value + Financial Assets - Liabilities - Minority Equity)
β
βΌ
Markdown Detailed Output (Value per share, Data Tables)Tech Stack
Component | Choice | Purpose |
MCP Framework |
| MCP server with stdio transport |
Data Validation |
| Strong typing and JSON Schema generation |
Build Tool |
| Project configuration and dependency management |
Testing |
| Unit testing for the core valuation engine |
License
MIT
Available Tools
1 toolreoi_valuation_modelB
Residual Operating Income Valuation Model (Strict Replica based on Ladleagent frontend). Accepts a full JSON state object for valuation calculation.
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It mentions 'Strict Replica' but does not disclose whether the tool is read-only, modifies data, requires permissions, or any other behavioral traits. The agent is left to infer that it computes a valuation without mutation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise at two sentences and front-loaded with the model name. It conveys the core function without fluff, but could benefit from added structure or examples without sacrificing brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of the input schema (multiple nested objects, many required fields) and the existence of an output schema, the description is too minimal. It does not summarize inputs, outputs, or calculation logic, leaving significant gaps for agent understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With schema description coverage reportedly at 0%, the description must compensate. However, it only vaguely refers to a 'full JSON state object' without explaining the one parameter 'request' or its nested structure. The agent lacks guidance on what fields matter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as a Residual Operating Income Valuation Model and states it accepts a full JSON state object for valuation calculation. The name and description align perfectly, leaving no ambiguity about the tool's function.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage by stating it accepts a full JSON state object, but provides no guidance on when to use it, prerequisites, or when not to use it. Since there are no sibling tools, the lack of alternatives is less critical, but basic usage context is missing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v0.1.0- First observed
reoi_valuation_model
TDQS
With only one tool, there is no risk of confusion. The tool's purpose is clear and distinct.
Only one tool exists, so consistency is trivially maintained. The name is clear and descriptive.
A single tool for a valuation model feels thin. Typically, a valuation server would benefit from multiple tools for different operations (e.g., parameter input, analysis, comparison).
The tool provides only a single calculation endpoint. Missing are tools for data management, scenario comparison, or model configuration, leading to significant gaps for a full valuation workflow.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Deterministic company valuation and corporate finance tools for AI agents β IRR, NPV, MOIC, DCF, WACC, enterprise value, EV multiples, CAPM, beta and sensitivity analysis via Model Context Protocol. Useful for financial analysis, equity analysis, quantitative analysis, financial projections, financial formulas and financial modeling.
13-model stock valuation engine for AI agents - fair values for 5,900+ US stocks, updated daily.
Structured financial modeling for AI agents: build, version, audit models, export to Excel.
Deterministic profitability and market-value analysis tools for AI agents β margins, ROA, ROE, ROCE, ROIC, EPS, P/E, P/B, dividend yield and payout ratio via Model Context Protocol. Useful for corporate finance, equity analysis, financial analysis, quantitative analysis, financial formulas and financial modeling.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to analyze single-company concentration risk for tech workers with RSU compensation, providing risk scores, wealth-at-risk, and action items.74Apache 2.0

SSCMFI Bond Analytics MCPofficial
FlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform high-precision Price and Yield calculations for fixed income securities, including institutional risk metrics, using the industry-standard SSCMFI Bond Math Engine.-- FlicenseAqualityDmaintenanceProvides AI assistants with real-time stock prices, financial statements, SEC filings, and analytical tools like DCF valuation and ratio analysis.14-
- AlicenseAqualityCmaintenanceEnables AI assistants to fetch intrinsic valuations and screen US equities using CirclFi's institutional-grade valuation models.245ISC
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/agentladle/mcp-reoi'
If you have feedback or need assistance with the MCP directory API, please join our Discord server