
lenderscope
io.github.CloudCorpRecords/lenderscope
Investor-lender data from HMDA: DSCR lenders by state, loan programs and indicative rates.
Documentation
lenderscope
Which lenders actually fund investment properties, state by state? lenderscope is a small local bridge to the hosted dscr-lender-data MCP service: it exposes HMDA-derived investor-lender data — lender rankings by state and in aggregate, the methodology behind the figures, a DSCR glossary, the National Loan Provider program set, and indicative rate ranges.
Nothing is stored or computed on your own machine. This package answers tools/list locally from the captured tool definitions and forwards every tools/call to the hosted service over a streamable-HTTP JSON-RPC session, returning whatever the service sends back unchanged.
The full captured surface is built: all seven tools, no omissions. Every tool is a read over published data. No tool takes borrower, contact or property data, and nothing is submitted anywhere — the vendor's term-sheet submission tools live on different servers and are not part of this surface.
The tools
investor_lenders_by_state— Top investment-property lenders in one of the 26 covered states, from 2025 HMDA loan-level data: lender name, LEI, loan count, volume, average loan and purchase share, plus state totals and the retrieval date.state(a two-letter code) is required;limitis optional (1–50, default 25). Figures are the filing record, not a recommendation.investor_lenders_aggregate— Every HMDA filer across the 26 covered states grouped by LEI and ranked by 2025 investor-property loan count, with per-filer state counts, universe totals and the top-25 concentration share. A 26-state aggregate, not a national one.limitis optional.hmda_methodology— How the data is built: the filter definition, the server-side versus local filtering split, the vintage and retrieval date, the covered states, and the stated limitations to attach to any reported figure. Takes no arguments.glossary_lookup— Definitions from the DSCR and investor-loan glossary (26 terms). Passtermto look one up (case-insensitive, partial matches accepted) or no argument to list every term.loan_programs— The National Loan Provider program set — dscr, dscr_cash_out, short_term_rental, fix_and_flip, ground_up, rental_portfolio, bridge, commercial — each with its published parameters, its starting rate with the as-of stamp, and the page URL. Filter with the optionalprogramkey, or omit it for all.rate_ranges— Indicative starting rate by program, from the site's single rate source, stamped with its as-of month. These are the published ranges, not pricing on any deal. Filter with the optionalprogramkey.about_national_loan_provider— The entity answer: legal name, business model (a mortgage brokerage that arranges and places financing and is not a lender), business-purpose scope and the owner-occupied exclusion, address, phone, the states with published investor-lending data, and the canonical Person @id for the founder. Takes no arguments.
Install and run
As an MCP server via npm:
npx -y @reneturcios/lenderscope mcp
MCP client configuration:
{
"mcpServers": {
"lenderscope": {
"command": "npx",
"args": ["-y", "@reneturcios/lenderscope", "mcp"]
}
}
}
As a container:
docker run -i ghcr.io/cloudcorprecords/lenderscope
docker run --rm ghcr.io/cloudcorprecords/lenderscope investor_lenders_by_state '{"state":"NJ"}'
CLI
One binary serves both the command line and the MCP server. Each tool is a subcommand taking a single JSON string with that tool's arguments:
lenderscope investor_lenders_by_state '{"state":"NJ","limit":10}'
lenderscope glossary_lookup '{"term":"dscr"}'
lenderscope hmda_methodology
lenderscope --version
Exit codes: 0 when the forwarded call succeeds, 1 when the upstream result is an error, and 2 for usage problems such as an unknown subcommand or a malformed JSON argument.
Configuration
DSCRLENDER_MCP_URL— Overrides the upstream endpoint. The default is the pinned hosted endpoint,https://dominickprevete.com/api/mcp. (The override variable is a reconstruction added by this rebuild.)
No authentication is configured or sent: the upstream record declares no auth headers and the tool surface was captured keyless, so this client never sends an Authorization, X-API-Key or any other credential header.
Upstream failures — a JSON-RPC error from the service, a non-2xx response, an unreadable body, or a request that fails outright — are reported to the caller as an error result whose text starts with lenderscope error:.
How forwarding works
The first forwarded call opens a session: an initialize request (protocol version 2025-03-26), followed by a notifications/initialized notification, then the tools/call itself. If the service answers the initialize request with an Mcp-Session-Id header, that value is carried on every later request, and the open session is reused for the rest of the process. Replies are accepted either as plain JSON or as server-sent events. Successful results pass through verbatim, including any isError flag and any extra fields the service includes.
Development
npm install
npm run build # tsc -> dist/ (dist/cli.js is the bin)
npm test # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev # run the CLI from source
The test suite checks the served tool list against the captured surface tool for tool, exercises the session handshake and its reuse, asserts that no authentication header is ever sent, and verifies that arguments go upstream untouched and results come back untouched, including upstream error results and SSE-framed replies.
License
MIT — see LICENSE. Copyright (c) 2026 Rene Turcios.
@reneturcios/lenderscopenpm install @reneturcios/lenderscopeghcr.io/cloudcorprecords/lenderscope:0.1.0docker pull ghcr.io/cloudcorprecords/lenderscope:0.1.0:undefinedRelated Servers
io.github.CloudCorpRecords/abandoncheck
Judge whether a dependency is maintained, from factual signals: releases, commits, archival.
io.github.CloudCorpRecords/actionbridge
Zapier exposed actions as MCP tools via a generic action runner.
io.github.CloudCorpRecords/actionpin
GitHub Actions supply-chain hardener: audit workflows for unpinned actions and build a SHA pin plan.