Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DealMatcher

REMOTE · DEALMATCHERAPP.COM

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

+3 this week 71 Trust /100

Last scanned (19 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 81% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 16 Nov 26 +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.

  • 15 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 68

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://dealmatcherapp.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dealmatcherapp.com CN=YE2,O=Let's Encrypt,C=US 15 Nov 2026 13 Feb 2027 ECDSA 256 ECDSA-SHA384 69fa06c20818a87b4a88fe8391a6fe75220
SANs: *.dealmatcherapp.com, dealmatcherapp.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of dealmatcherapp.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
dealmatcherapp.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.gstatic.com https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: blob: https:; connect-src 'self' https://cloudflareinsights.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://dealmatcherapp.com/api/mcp Verified 200
http (plaintext) http://dealmatcherapp.com/api/mcp HTTPS enforced 302 https://dealmatcherapp.com/api/mcp
MCP tools · 5 exposed · ~1,166 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
county_lending_market ~183

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.

NameTypeReqDescription
countystring–county name, e.g. "Bexar" or "Los Angeles County"; give state too
county_fipsstring–5-digit county FIPS code, e.g. "48029" for Bexar County, TX
statestring–two-letter state code, needed with county
yearinteger–optional HMDA filing year; defaults to the latest published

No output schema declared.

No examples provided.

government_loan_fees ~193

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.

NameTypeReqDescription
loan_amountstringyesbase loan amount, e.g. "$300,000"
ltvstringyesloan-to-value, e.g. "96.5" or "100%", at most two decimals
programstringyes–
term_yearsinteger–loan term in years; required for FHA
va_exemptboolean–VA only: a borrower exempt from the funding fee
va_first_useboolean–VA only: first use (default true)
va_purposestring–VA only

No output schema declared.

No examples provided.

lender_lookup ~113

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.

NameTypeReqDescription
querystringyespart of the lender's legal name, e.g. "Wells Fargo", or its 20-character LEI
statestring–optional: only lenders with HMDA records for property in this state

No output schema declared.

No examples provided.

llpa_cost ~502

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.

NameTypeReqDescription
amortizationstring––
duty_to_serveboolean–true if the loan may meet a Duty to Serve category (flagged as a possible waiver, never applied)
ficointegeryesrepresentative 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_homebuyerboolean––
high_balanceboolean–true if the loan is above the county baseline (high-balance)
homereadyboolean––
loan_amountstringyesdollar amount, e.g. "$360,000"
ltvstringyesloan-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_advantageboolean–manufactured home only: true if it meets MH Advantage (no manufactured-home charge)
minimum_miboolean–true if the loan uses Fannie Mae's minimum mortgage insurance coverage option (adds the Minimum-MI charge)
occupancystring––
property_typestring–DETACHED_CONDO and COOP do not pay the condo charge (matrix footnote 1)
purposestring––
subordinate_financingboolean–true if there is a second lien (CLTV above LTV)
term_yearsinteger–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.

No output schema declared.

No examples provided.

loan_limit ~175

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.

NameTypeReqDescription
countystring–county name, e.g. "Bexar" or "Los Angeles County"; give state too
county_fipsstring–5-digit county FIPS code, e.g. "48029" for Bexar County, TX
statestring–two-letter state code, needed with county

No output schema declared.

No examples provided.

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.

remote · dealmatcherapp.com

# add to Claude Code
claude mcp add --transport http com-bonissystems-dealmatcher 'https://dealmatcherapp.com/api/mcp'
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.