Real estate deal memo
REMOTE · AGENTWARES-DEAL-MEMO.VERCEL.APP · SCANNED SEP 25
Real estate deal memo from a US address: AVM, rent, comps, cap rate, cash-on-cash, DSCR, red flags.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 763 tokens (~381/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Real estate deal memo MCP server?
Real estate deal memo is a hosted endpoint at https://agentwares-deal-memo.vercel.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agentwares-deal-memo.vercel.app
claude mcp add --transport http agentwares-deal-memo 'https://agentwares-deal-memo.vercel.app/api/mcp'
{
"mcpServers": {
"agentwares-deal-memo": {
"url": "https://agentwares-deal-memo.vercel.app/api/mcp"
}
}
} {
"servers": {
"agentwares-deal-memo": {
"type": "http",
"url": "https://agentwares-deal-memo.vercel.app/api/mcp"
}
}
} [mcp_servers.agentwares-deal-memo] url = "https://agentwares-deal-memo.vercel.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"agentwares-deal-memo": {
"type": "remote",
"url": "https://agentwares-deal-memo.vercel.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add agentwares-deal-memo --url 'https://agentwares-deal-memo.vercel.app/api/mcp' --transport streamable-http
mcp_servers:
agentwares-deal-memo:
url: "https://agentwares-deal-memo.vercel.app/api/mcp" {
"McpServers": {
"agentwares-deal-memo": {
"Transport": "http",
"Url": "https://agentwares-deal-memo.vercel.app/api/mcp"
}
}
} assistant mcp add agentwares-deal-memo -t streamable-http -u 'https://agentwares-deal-memo.vercel.app/api/mcp'
{
"mcpServers": {
"agentwares-deal-memo": {
"type": "http",
"url": "https://agentwares-deal-memo.vercel.app/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://agentwares-deal-memo.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentwares-deal-memo.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentwares-deal-memo.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://agentwares-deal-memo.vercel.app/api/mcp | HTTPS enforced | 308 | https://agentwares-deal-memo.vercel.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
realestate_deal_memo Deal memo ~359
Underwrite a US residential property from its street address for a rental, flip or hold strategy. Pulls the property record (owner, last sale, taxes, HOA), the automated value estimate with sale comps and the long-term rent estimate with rental comps from RentCast, then computes NOI, cap rate, cash-on-cash, DSCR, GRM and break-even occupancy from stated assumptions with deterministic math (plus 70%-rule, profit and ROI for a flip; a multi-year exit projection for a hold), lists red flags with a pass/review/fail screen, and adds a one-paragraph analyst memo. Returns {data, sources, as_of, confidence, notice}. Not financial advice: verify before acting. Paid: $0.75 per call; without credit you get a PAYMENT_REQUIRED result. Set sample=true for a free example response.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Full US street address: number, street, city, state, zip (e.g. 1547 Example Ave, Cleveland, OH 44109). Required unless sample=true. |
| assumptions | object | – | Underwriting assumptions. Every field is optional; omitted fields use the documented defaults. |
| memo | boolean | – | Include the one-paragraph memo (cheap model, cached). Default true. |
| sample | boolean | – | Set true to return an example response at no charge (sample mode). Default false. |
| strategy | string | – | rental: buy and rent out (NOI, cap rate, cash-on-cash, DSCR). flip: buy, rehab, resell (70% rule, profit, ROI). hold: rental metrics plus a multi-year exit projection (appreciation, principal paydown… |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | ISO time of the oldest upstream data point in this response |
| confidence | object | yes | – |
| data | object | yes | – |
| notice | string | yes | liability disclaimer; always present |
| sample | boolean | yes | true when this is the free example, not a live lookup |
| sources | array | yes | – |
No examples provided.
realestate_lookup Property lookup ~243
Fetch one RentCast record for a US street address. kind=property: characteristics, owner, last sale, tax bill, assessment, HOA and sale history. kind=value: automated value estimate with a low/high range and the sale comps behind it. kind=rent: long-term rent estimate with a range and rental comps. One upstream call per lookup; use realestate_deal_memo when you need all three plus the underwriting. Returns {data, sources, as_of, confidence, notice}. Paid: $0.10 per call; without credit you get a PAYMENT_REQUIRED result. Set sample=true for a free example response.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Full US street address: number, street, city, state, zip (e.g. 1547 Example Ave, Cleveland, OH 44109). Required unless sample=true. |
| kind | string | – | property: characteristics, owner, last sale, taxes, HOA. value: automated value estimate with range and sale comps. rent: long-term rent estimate with range and rental comps. |
| sample | boolean | – | Set true to return an example response at no charge (sample mode). Default false. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | ISO time of the oldest upstream data point in this response |
| confidence | object | yes | – |
| data | object | yes | – |
| notice | string | yes | liability disclaimer; always present |
| sample | boolean | yes | true when this is the free example, not a live lookup |
| sources | array | yes | – |
No examples provided.
What is the Real estate deal memo MCP server?
Real estate deal memo is an MCP server listed in the public MCP registry as io.github.agentwares/deal-memo. Real estate deal memo from a US address: AVM, rent, comps, cap rate, cash-on-cash, DSCR, red flags. This page covers its hosted endpoint (https://agentwares-deal-memo.vercel.app/api/mcp).
Is the Real estate deal memo MCP server safe to use?
Real estate deal memo scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Real estate deal memo MCP server expose?
Real estate deal memo exposes 2 tools: realestate_deal_memo, realestate_lookup. Their descriptions and schemas cost roughly 602 tokens of context every time the server is loaded.
Does the Real estate deal memo MCP server require authentication?
No. We connected to Real estate deal memo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Real estate deal memo MCP server still maintained?
Real estate deal memo is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.