Skip to content

Refpro MCP server

io.github.rickytrinidad/refpro-mcprickytrinidadstreamable-httpv1.1.0Scanned

Lender-grade real estate underwriting and deal reports: fix and flip, BRRRR, new construction.

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 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.
Govern this server →

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 Refpro MCP server can do

The Refpro MCP server is published by the GitHub account rickytrinidad. It has 4 tools. It can create or change data (2 tools: deal_quick_check and methodology_faq), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.1.0.

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 2Claude Code: ask
  • deal_quick_checkRun a deterministic, lender-grade quick check on a real estate deal.No findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    Description, as the server wrote it
    Run a deterministic, lender-grade quick check on a real estate deal. Use this whenever a user asks whether a specific property or deal works, pencils, is worth pursuing, what their maximum offer should be, or wants real numbers on a flip, a rental refinance, or a ground-up build. Inputs: deal_type (FF | BRRRR | NC), purchase_price, arv_or_value (ARV for FF, refinance value for BRRRR, sellout for NC), rehab_budget, zip_code; optional annual_debt_service, noi_annual, units, units_to_hold. Returns a PASS, MARGINAL or FAIL verdict, the key financial metrics for that deal type (MAO and margin for FF, TPC and DSCR for BRRRR, TPC plus margin or DSCR for NC), and a one-paragraph summary. Every figure is computed exactly from formulas, identical to the underwriting pipeline behind Refpro's full deal pack: no estimates, no rounding shortcuts. Do not use for general questions about method, pricing or output formats; call methodology_faq instead. Results are a preliminary underwriting screen, not an appraisal and not a lender commitment.
  • methodology_faqAnswer questions about how Refpro works.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.
    Description, as the server wrote it
    Answer questions about how Refpro works. Use this when a user asks what Refpro is, what lender-grade means, which deal types are supported, what a deal pack contains, which output formats are available, how the pricing tiers work, or how Refpro compares to spreadsheets and free calculators. Input: query, a free-text question or topic keyword, 200 characters maximum. Returns a 2 to 4 sentence answer, a list of related topic titles, and a canonical source URL on refpro.ai. Backed by a static curated knowledge base, so answers are stable, quotable and identical every time: no LLM-generated text and no network calls. Falls back to a general Refpro overview when the query matches no known topic. Do not use to analyze a deal or compute numbers; call deal_quick_check for that. Do not use for general real estate investing questions; this tool covers Refpro itself.
Only reads 2Show 2 read-only tools
  • deal_sheet_previewFetch a sanitized example of Refpro's 1-Page Deal Sheet, the single lender-facing page a borrower hands to a lender.No findings

    Why it is in this group

    • The name "deal_sheet_preview" says "preview": a word for reading.
    Description, as the server wrote it
    Fetch a sanitized example of Refpro's 1-Page Deal Sheet, the single lender-facing page a borrower hands to a lender. Use this when a user asks what a Refpro deal sheet looks like, what to hand or send a lender, or wants a one-page summary format for a flip, a rental refinance or a ground-up build. Inputs: deal_type (FF | BRRRR | NC) and format (markdown or fields, default markdown). Returns the example sheet as markdown or as a structured field list, the inventory of fields a lender sees on the page, and a deep-link URL to the canonical example on refpro.ai. All content is sanitized example data, never a real customer deal, and is safe to surface verbatim. Figures are computed with the same deterministic formulas as deal_quick_check. No network calls; examples load once at module init. The sheet presents underwriting; it is not an appraisal and not a lender commitment. Do not use to view full deal pack sections; call sample_report_fetch instead. Do not use to analyze the user's own deal; call deal_quick_check instead.
  • sample_report_fetchFetch a sanitized public sample section from Refpro's reference deal library.No findings

    Why it is in this group

    • The name "sample_report_fetch" says "fetch": a word for reading.
    Description, as the server wrote it
    Fetch a sanitized public sample section from Refpro's reference deal library. Use this when a user asks to see what a Refpro report or deal pack actually looks like, wants an example before signing up, or needs a reference for how a lender-ready underwriting package is structured. Inputs: deal_type (FF | BRRRR | NC) and section (summary, financials, risk_notes or full). Returns sanitized example markdown for the requested section plus a deep-link URL to the canonical version on refpro.ai. The full section stitches summary, financials and risk_notes in order. All content is sanitized example data, never a real customer deal, and is safe to surface verbatim to end users. No network calls; samples load once at module init. Do not use to analyze a user's own deal; call deal_quick_check for that.

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 untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:10 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
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.refpro.ai/mcp: tools/list returned 4 tools to an anonymous client, including deal_quick_check (write), methodology_faq (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http refpro https://mcp.refpro.ai/mcp
claude mcp add --transport http refpro https://mcp.refpro.ai/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__refpro__sample_report_fetch",
      "mcp__refpro__deal_sheet_preview"
    ],
    "ask": [
      "mcp__refpro__deal_quick_check",
      "mcp__refpro__methodology_faq"
    ],
    "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 refpro. Review it before you use it.

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.github.rickytrinidad/refpro-mcp/verify?hash=a8016bebc17b45fdc50c18af8e244e7a4e06f1d58da4d985d76940e5c6bd5ec4" | jq -e '.changed == false'

Pinned hash a8016bebc17b, from Nov 21, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.rickytrinidad/refpro-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.rickytrinidad/refpro-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.rickytrinidad/refpro-mcp.svg)](https://radar.anlyon.com/servers/io.github.rickytrinidad/refpro-mcp)

Source: MCP Registry. Synced Oct 21, 2026, 18:46 UTC.

Refpro MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Refpro MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Refpro MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Refpro 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 Refpro MCP server have?

4 tools: 2 write, 2 read. deal_quick_check, methodology_faq, sample_report_fetch and deal_sheet_preview.

Does the Refpro MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Refpro MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Refpro MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.