German Real Estate Depreciation & Restnutzungsdauer MCP server
online · 100% uptimeimmo.rundum/real-estate-appraisal·v0.2.1German property depreciation (AfA), Restnutzungsdauer, Kaufpreisaufteilung & appraisals via AfAMax
not scanned yet
0 stars40 downloads/wk
Reviews
Write oneNobody has reviewed German Real Estate Depreciation & Restnutzungsdauer yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
German Real Estate Depreciation & Restnutzungsdauer tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How German Real Estate Depreciation & Restnutzungsdauer compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 86/100
- higher than 72% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 604 ms
- faster than 24% of 30,031 servers
- Downloads a week
- 40
- more than 31% of 12,191 servers with a package
Release history: 4 versions in the registry since 2026-09-16, latest 2026-10-06, typically one every 5 days.
Install German Real Estate Depreciation & Restnutzungsdauer in Claude Code, Cursor or VS Code
claude mcp add --transport http real-estate-appraisal https://mcp.rundum.immo/mcp
What the publisher says
From the German Real Estate Depreciation & Restnutzungsdauer repository's README, as published. We do not edit it. Read it on GitHub
Rundum Immo Real Estate Appraisal MCP
An open-source Model Context Protocol server for indicative German real-estate depreciation and purchase-price allocation. It exposes calculatepropertydepreciation and calculatepurchaseprice_allocation, delegating both calculations to the public AfAMax APIs. Proprietary appraisal formulas remain in AfAMax.
<!-- mcp-name: immo.rundum/real-estate-appraisal -->
Hosted server
The public Streamable HTTP endpoint is:
https://mcp.rundum.immo/mcpNo end-user API key is required. Calls are subject to AfAMax per-client and service-wide rate limits and abuse protections.
Run from source over stdio
Node.js 22.12 or newer is required.
git clone https://github.com/Rundum-Immo/real-estate-appraisal-mcp.git
cd real-estate-appraisal-mcp
pnpm install --frozen-lockfile
pnpm buildConfigure your MCP client to run the built server, replacing the path with the absolute path to your checkout:
{
"mcpServers": {
"rundum-real-estate-appraisal": {
"command": "node",
"args": ["/absolute/path/to/real-estate-appraisal-mcp/dist/transports/stdio.js"]
}
}
}The stdio server calls the anonymous AfAMax API directly. Its public limits are 30 requests per minute and 500 requests per rolling day per IP; a tenant-wide ceiling may also apply. It writes protocol messages only to stdout and operational logs only to stderr.
Install from npm over stdio
Node.js 22.12 or newer is required. Configure your MCP client to launch the published package with npx:
{
"mcpServers": {
"rundum-real-estate-appraisal": {
"command": "npx",
"args": ["-y", "@rundum-immo/real-estate-appraisal-mcp"]
}
}
}Tools
Property depreciation
calculatepropertydepreciation accepts the complete public AfAMax request contract:
- Required: property type, construction year, and floor area.
- Optional: purchase price, land area, standard land value, inventory, purchase costs, core-renovation year, marginal tax rate, locale, coarse modernization level, and eight detailed modernization component states.
- Results: annual and monthly AfA, comparison with statutory AfA, estimated tax savings, building-value assumptions, modernization points, and remaining useful life.
Omitting modernization data means AfAMax assumes no modernization, producing an upper-bound estimate. For multi-unit buildings, provide whole-building figures or calculate individual units separately. Results are indicative and do not replace tax, legal, or appraisal advice.
Example input:
{
"propertyType": "CONDOMINIUM",
"constructionYear": 1970,
"floorArea": 85,
"purchasePrice": 350000,
"taxRate": 0.42,
"locale": "en"
}Purchase-price allocation
calculatepurchaseprice_allocation divides acquisition costs between non-depreciable land and the depreciable building using the German Federal Ministry of Finance (BMF) method.
- Required: property type, total purchase price, purchase date, construction year, floor area, land area, and standard land value.
- Condominiums also require the numerator and denominator of the co-ownership share.
- Mixed-use residential/commercial buildings also require whether the commercial share is under or over 50%.
- Optional: purchase costs, included inventory, garage and underground-parking counts, monthly net cold rent, and locale.
- Results: the applied method, meaningful alternatives, land/building shares and values, depreciation base, unavailable or unusable method reasons, and disclosed asset-method defaults.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-10-02restoreB → Ascore 86: Write-action tools reachable without authentication
German Real Estate Depreciation & Restnutzungsdauer: common questions
- Is German Real Estate Depreciation & Restnutzungsdauer MCP server safe?
- Yes, by our scan: it is graded A (86/100). Read the German Real Estate Depreciation & Restnutzungsdauer safety report
- How do I install German Real Estate Depreciation & Restnutzungsdauer?
- It runs remotely at mcp.rundum.immo. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does German Real Estate Depreciation & Restnutzungsdauer need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is German Real Estate Depreciation & Restnutzungsdauer maintained?
- The last commit was 34 days ago (2026-10-01). The latest release is v0.2.1.
- Is German Real Estate Depreciation & Restnutzungsdauer up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does German Real Estate Depreciation & Restnutzungsdauer compare with other MCP servers?
- safety score 86/100 (higher than 72% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 604 ms (faster than 24% of 30,031 servers). Full comparison.