Real Estate Analyzer MCP server
io.reizer/deal-analysisreizer.iostreamable-httpv1.0.2Scanned
Free real-estate underwriting, no key or account. 6 strategies, stress tests, max offer.
4 tools: 3 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Real Estate Analyzer MCP server can do
The Real Estate Analyzer MCP server is published by reizer.io, a domain the MCP Registry verified. It has 4 tools. It can create or change data (3 tools: analyze_deal, best_use and solve_max_offer), but cannot delete data. 1 tool only reads.
1 tool brings in text other people can write (analyze_deal).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 1.0.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 3Claude Code: ask
analyze_dealAnalyze a real-estate investment deal and get a 0-100 score, verdict, cash flow, cap rate, DSCR, stress tests, break-even thresholds, and a shareable report link.Reads text others write1 finding
Why it is in this group
- The name "analyze_deal" says "analyze": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "analyze_deal" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "analyze_deal" says "analyze": a word for reading.
Description, as the server wrote it Analyze a real-estate investment deal and get a 0-100 score, verdict, cash flow, cap rate, DSCR, stress tests, break-even thresholds, and a shareable report link. Strategies: ltr (long-term rental), str (short-term rental), brrr, multifamily, flip (fix-n-flip), newc (new construction). All rates/percents are FRACTIONS (0.0675 = 6.75%). Omitted operating inputs are filled with documented defaults and listed in assumptions.estimated_fields. Output is a software estimate, not financial, investment, tax or legal advice — figures are projections to verify, not recommendations. Free, no key; the response includes a shareable report_url.
Annotations the server declares
- title: Analyze a real-estate deal
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
best_useScreen ONE property across every strategy the provided inputs qualify for and rank them by deal score — answers "what is the best use of this property?".No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Screen ONE property across every strategy the provided inputs qualify for and rank them by deal score — answers "what is the best use of this property?". Provide a superset of inputs (price, marketRent, adr, occupancy, rehabBudget, arv, units, …); strategies missing inputs are skipped with reasons. All rates/percents are FRACTIONS (0.0675 = 6.75%). Omitted operating inputs are filled with documented defaults and listed in assumptions.estimated_fields. Free, no key.
Annotations the server declares
- title: Rank the best use of a property
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
solve_max_offerReverse-solve the Maximum Allowable Offer: the highest purchase price that still meets every return target (defaults: CoC 8%, DSCR 1.20, cash flow ≥ 0; flip: 10% after-tax margin +…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Reverse-solve the Maximum Allowable Offer: the highest purchase price that still meets every return target (defaults: CoC 8%, DSCR 1.20, cash flow ≥ 0; flip: 10% after-tax margin + 15% annualized ROI). Returns the MAO, the binding constraint, and per-target price ceilings. Strategies: ltr, str, brrr, multifamily, flip. Provide the deal inputs WITHOUT committing to a price; an asking price or arv, if known, anchors the price-based defaults, and with neither those defaults (taxes, insurance, closing) follow each price tested. Override targets via the targets object. All rates/percents are FRACTIONS (0.0675 = 6.75%). Omitted operating inputs are filled with documented defaults and listed in assumptions.estimated_fields. Free, no key.
Annotations the server declares
- title: Solve the maximum offer
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
list_strategiesList every supported strategy with its required and optional input fields.No findings
Why it is in this group
- The name "list_strategies" says "list": a word for reading.
Description, as the server wrote it List every supported strategy with its required and optional input fields. Call this first when unsure which inputs a strategy needs. Free, no key.
Annotations the server declares
- title: List strategies and their inputs
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:14 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://reizer.io/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://urqjaxmcxwblmnotkwmi.supabase.co/auth/v1
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://reizer.io/mcp: tools/list returned 4 tools to an anonymous client, including analyze_deal (write), best_use (write), solve_max_offer (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnanalyze_deal
The server marks "analyze_deal" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "analyze_deal" says "analyze": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:analyze_dealChanges thingsdescriptionannotations
Install
Pinned to version 1.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http deal-analysis https://reizer.io/mcpclaude mcp add --transport http deal-analysis https://reizer.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__deal-analysis__list_strategies"
],
"ask": [
"mcp__deal-analysis__analyze_deal",
"mcp__deal-analysis__best_use",
"mcp__deal-analysis__solve_max_offer"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as deal-analysis. Review it before you use it.
Capability tags behind 1 rule
- mcp__deal-analysis__analyze_deal untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.reizer/deal-analysis/verify?hash=31bb6d033e8da2cdbe5a584c23f0943eaa51b687f891d1ba36557f23fc4005e6" | jq -e '.changed == false'Pinned hash 31bb6d033e8d, from Nov 18, 2026, 14:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.reizer/deal-analysis/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.reizer/deal-analysis)Source: MCP Registry. Synced Oct 21, 2026, 18:52 UTC.
Real Estate Analyzer MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Real Estate Analyzer MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Real Estate Analyzer MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Real Estate Analyzer MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Real Estate Analyzer MCP server have?
- 4 tools: 3 write, 1 read. analyze_deal, best_use, solve_max_offer and list_strategies.
Does the Real Estate Analyzer MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Real Estate Analyzer MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Real Estate Analyzer MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 4, 2026. Every change is on this page and in its Atom feed.