Is the npm:dealflowpro-mcp MCP server safe to use?
Independent trust grade C- (72/100). References sensitive file paths / environment secrets. wmcp.sh continuously watches npm:dealflowpro-mcp for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.
What it offers — 4 tools · Maps & Geo
analyze_deal
Analyze a multifamily real estate deal. Returns cap rate, cash-on-cash, DSCR, IRR, DFP Score (0-100), max offer price, and full financial projections.
score_deal
Quick-score a multifamily deal on the DFP 0-100 scale. Returns the DFP Score and key metrics. Faster than full analysis — use this for quick screening
reverse_calc
Calculate the maximum offer price for a multifamily deal based on target return metrics. Back-solves from your desired cap rate, cash-on-cash, DSCR, a
market_data
Look up market intelligence for a property address. Returns flood zone, neighborhood income relative to state median, and job growth rate. Use this wh
INFO Static analysis of npm package dealflowpro-mcp@1.2.3 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
We re-grade npm:dealflowpro-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.
Share this report card
A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.
A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.
Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:
https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.