accueil / serveurs / Dev & Code / io.github.rickytrinidad/refpro-mcp
io.github.rickytrinidad/refpro-mcp
serveur MCP (Model Context Protocol) · refpro-mcp 1.1.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.rickytrinidad/refpro-mcp est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.rickytrinidad/refpro-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 4 outils
- deal_quick_check≈ 483 tokens
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.
Paramètres, retour & exemple (9)
Paramètresunits· integer · optionnelzip_code· string · requisdeal_type· string · requis · FF | BRRRR | NCnoi_annual· number · optionnelarv_or_value· number · requisrehab_budget· number · requisunits_to_hold· integer · optionnelpurchase_price· number · requisannual_debt_service· number · optionnel
Exemple d'appel{"name": "deal_quick_check", "arguments": {"zip_code": "texte", "deal_type": "FF", "arv_or_value": 1, "rehab_budget": 1, "purchase_price": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - deal_sheet_preview≈ 341 tokens
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.
Paramètres, retour & exemple (2)
Paramètresformat· string · optionnel · markdown | fieldsdeal_type· string · requis · FF | BRRRR | NC
Exemple d'appel{"name": "deal_sheet_preview", "arguments": {"deal_type": "FF"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - methodology_faq≈ 276 tokens
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.
Paramètres, retour & exemple (1)
Paramètresquery· string · requis
Exemple d'appel{"name": "methodology_faq", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - sample_report_fetch≈ 287 tokens
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.
Paramètres, retour & exemple (2)
Paramètressection· string · requis · summary | financials | risk_notes | fulldeal_type· string · requis · FF | BRRRR | NC
Exemple d'appel{"name": "sample_report_fetch", "arguments": {"section": "summary", "deal_type": "FF"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».