# DealMatcher (remote · dealmatcherapp.com)

Check a county's loan limit, a loan's price adjustment, FHA/VA/USDA fees or a lender.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `dealmatcherapp.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-bonissystems-dealmatcher/api-mcp.md), [page](https://verifymcp.io/servers/com-bonissystems-dealmatcher/api-mcp)

## Channel facts

- Endpoint: `https://dealmatcherapp.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1245 tokens (~249/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 81% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the DealMatcher MCP server?

DealMatcher is a hosted endpoint at https://dealmatcherapp.com/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.

### Claude

```bash
claude mcp add --transport http com-bonissystems-dealmatcher 'https://dealmatcherapp.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-bonissystems-dealmatcher": {
      "url": "https://dealmatcherapp.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-bonissystems-dealmatcher": {
      "type": "http",
      "url": "https://dealmatcherapp.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-bonissystems-dealmatcher]
url = "https://dealmatcherapp.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-bonissystems-dealmatcher": {
      "type": "remote",
      "url": "https://dealmatcherapp.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-bonissystems-dealmatcher --url 'https://dealmatcherapp.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-bonissystems-dealmatcher:
    url: "https://dealmatcherapp.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-bonissystems-dealmatcher": {
      "Transport": "http",
      "Url": "https://dealmatcherapp.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-bonissystems-dealmatcher -t streamable-http -u 'https://dealmatcherapp.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-bonissystems-dealmatcher": {
      "type": "http",
      "url": "https://dealmatcherapp.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 71, +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.

### 2026-11-19 (score 70, +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.

### 2026-11-16 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 68)

First indexed and scored.

## MCP tools (5)

### `loan_limit` (~175 tokens)

Conforming and FHA loan limits for a county

The 2026 conforming loan limit for a U.S. county (1 to 4 units) from the Federal Housing Finance Agency's county file, whether the county is above the national baseline (high-balance), the county's FHA loan limits (1 to 4 units) from HUD's county file with its year, and the DealMatcher page to cite. Give a 5-digit county FIPS code, or a county name with its two-letter state.

Input parameters:

- `county` (string): county name, e.g. "Bexar" or "Los Angeles County"; give state too
- `county_fips` (string): 5-digit county FIPS code, e.g. "48029" for Bexar County, TX
- `state` (string): two-letter state code, needed with county

### `llpa_cost` (~502 tokens)

Fannie Mae price adjustment (LLPA) for a scenario

Fannie Mae's published loan-level price adjustment (LLPA) for an anonymized conventional scenario (Classic FICO, LTV, loan amount, purpose, occupancy, property type), the dollar price it adds, and the structuring moves that lower it, with the matrix edition. An LLPA is a one-time price adjustment, never an interest rate and never a credit decision; the lender decides. Takes numbers only, never a borrower's name or details.

Input parameters:

- `amortization` (string)
- `duty_to_serve` (boolean): true if the loan may meet a Duty to Serve category (flagged as a possible waiver, never applied)
- `fico` (integer, required): representative Classic FICO score, e.g. 740. VantageScore 4.0 pricing is not loaded, so a VantageScore must not be given here: Fannie Mae's 09/30/2026 reissue of LL-2026-06 removed the separate Vanta…
- `first_time_homebuyer` (boolean)
- `high_balance` (boolean): true if the loan is above the county baseline (high-balance)
- `homeready` (boolean)
- `loan_amount` (string, required): dollar amount, e.g. "$360,000"
- `ltv` (string, required): loan-to-value, e.g. "90" or "80.5%". Read as Fannie Mae does (Selling Guide B2-1.2-01): truncated to two decimals, then rounded up to the whole percent.
- `mh_advantage` (boolean): manufactured home only: true if it meets MH Advantage (no manufactured-home charge)
- `minimum_mi` (boolean): true if the loan uses Fannie Mae's minimum mortgage insurance coverage option (adds the Minimum-MI charge)
- `occupancy` (string)
- `property_type` (string): DETACHED_CONDO and COOP do not pay the condo charge (matrix footnote 1)
- `purpose` (string)
- `subordinate_financing` (boolean): true if there is a second lien (CLTV above LTV)
- `term_years` (integer): loan term in years; defaults to 30 and the answer says so. Fannie Mae's purchase and limited cash-out score grids apply only to terms over 15 years.

### `government_loan_fees` (~193 tokens)

FHA, VA or USDA loan fees

The published government fee a program adds to an anonymized loan: FHA upfront and annual mortgage insurance premium (MIP) and how long it runs, the VA funding fee, or the USDA guarantee fee, from the agency schedules with their effective dates. A published fee, never an interest rate and never a credit decision.

Input parameters:

- `loan_amount` (string, required): base loan amount, e.g. "$300,000"
- `ltv` (string, required): loan-to-value, e.g. "96.5" or "100%", at most two decimals
- `program` (string, required)
- `term_years` (integer): loan term in years; required for FHA
- `va_exempt` (boolean): VA only: a borrower exempt from the funding fee
- `va_first_use` (boolean): VA only: first use (default true)
- `va_purpose` (string): VA only

### `county_lending_market` (~183 tokens)

Mortgage lending in a county (HMDA)

What lenders reported for a U.S. county in the latest HMDA filing year: purchase, refinance and cash-out loans and applications by loan type (conventional, FHA, VA, USDA) against the national mix, and the denial rate with its base named. Describes a market, never a person; small counts are withheld. Give a county FIPS code, or a county name with its state.

Input parameters:

- `county` (string): county name, e.g. "Bexar" or "Los Angeles County"; give state too
- `county_fips` (string): 5-digit county FIPS code, e.g. "48029" for Bexar County, TX
- `state` (string): two-letter state code, needed with county
- `year` (integer): optional HMDA filing year; defaults to the latest published

### `lender_lookup` (~113 tokens)

Mortgage lender profile (HMDA)

A mortgage lender's own 2025 HMDA filing, by name or LEI: records, loans originated and their dollar total, the loan-type and loan-purpose mix, and its largest states. Not a rating; no per-lender approval or denial rate is given.

Input parameters:

- `query` (string, required): part of the lender's legal name, e.g. "Wells Fargo", or its 20-character LEI
- `state` (string): optional: only lenders with HMDA records for property in this state

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-bonissystems-dealmatcher/api-mcp#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 70
- 2026-11-19: 70
- 2026-11-18: 69
- 2026-11-17: 69
- 2026-11-16: 69
- 2026-11-15: 68
- 2026-11-14: 68

## Common questions

### What is the DealMatcher MCP server?

DealMatcher is an MCP server listed in the public MCP registry as com.bonissystems/dealmatcher. Check a county's loan limit, a loan's price adjustment, FHA/VA/USDA fees or a lender. This page covers its hosted endpoint (https://dealmatcherapp.com/api/mcp).

### Is the DealMatcher MCP server safe to use?

DealMatcher scores 71 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 DealMatcher MCP server expose?

DealMatcher exposes 5 tools: loan_limit, llpa_cost, government_loan_fees, county_lending_market, lender_lookup. Their descriptions and schemas cost roughly 1,166 tokens of context every time the server is loaded.

### Does the DealMatcher MCP server require authentication?

No. We connected to DealMatcher without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the DealMatcher MCP server still maintained?

DealMatcher is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the DealMatcher MCP server?

VerifyMCP ran 13 checks on DealMatcher, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://dealmatcherapp.com/api/mcp
- Website: https://dealmatcherapp.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-bonissystems-dealmatcher/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-bonissystems-dealmatcher/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-bonissystems-dealmatcher/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-bonissystems-dealmatcher/api-mcp
