_ registry / mcp streamable-http · checked 1h ago

dealmatcher

https://dealmatcherapp.com

Registry code: 779f1ffe4003afe1

api record

DealMatcher answers mortgage questions from published sources: FHFA loan limits, the Fannie Mae price adjustment matrix, the FHA/VA/USDA fee schedules and the federal HMDA filings. Every answer carries its source, its edition and a DealMatcher page; cite the page. Read-only. It never quotes an interest rate and never makes a credit decision; the lender decides.

endpoint
https://dealmatcherapp.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is dealmatcher live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is dealmatcher free to use?
Yes — the hub reached it with no key and no payment.
What tools does dealmatcher have?
5 tools: government_loan_fees, llpa_cost, lender_lookup, county_lending_market, loan_limit.
Is dealmatcher safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
790ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • government_loan_fees unknown 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "program",
    "loan_amount",
    "ltv"
  ],
  "properties": {
    "ltv": {
      "type": "string",
      "pattern": "^\\s*\\d{1,3}(\\.\\d{1,3})?\\s*%?\\s*$",
      "description": "loan-to-value, e.g. \"96.5\" or \"100%\""
    },
    "program": {
      "enum": [
        "FHA",
        "VA",
        "USDA"
      ],
      "type": "string"
    },
    "va_exempt": {
      "type": "boolean",
      "description": "VA only: a borrower exempt from the funding fee"
    },
    "term_years": {
      "type": "integer",
      "maximum": 40,
      "minimum": 1,
      "description": "loan term in years; required for FHA"
    },
    "va_purpose": {
      "enum": [
        "PURCHASE",
        "CASHOUT",
        "IRRRL",
        "ASSUMPTION"
      ],
      "type": "string",
      "description": "VA only"
    },
    "loan_amount": {
      "type": "string",
      "pattern": "^\\s*\\$?\\s*[\\d,]{1,12}(\\.\\d{1,2})?\\s*$",
      "description": "base loan amount, e.g. \"$300,000\""
    },
    "va_first_use": {
      "type": "boolean",
      "description": "VA only: first use (default true)"
    }
  },
  "additionalProperties": false
}
    arguments 53 lines
  • llpa_cost unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "fico",
    "ltv",
    "loan_amount"
  ],
  "properties": {
    "ltv": {
      "type": "string",
      "pattern": "^\\s*\\d{1,3}(\\.\\d{1,3})?\\s*%?\\s*$",
      "description": "loan-to-value, e.g. \"90\" or \"80.5%\""
    },
    "fico": {
      "type": "integer",
      "maximum": 850,
      "minimum": 300,
      "description": "representative Classic FICO score, e.g. 740. VantageScore 4.0 pricing is not loaded, so a VantageScore must not be given here."
    },
    "purpose": {
      "enum": [
        "PURCHASE",
        "LIMITED_CASHOUT",
        "CASHOUT"
      ],
      "type": "string"
    },
    "homeready": {
      "type": "boolean"
    },
    "occupancy": {
      "enum": [
        "PRIMARY",
        "SECOND_HOME",
        "INVESTMENT"
      ],
      "type": "string"
    },
    "loan_amount": {
      "type": "string",
      "pattern": "^\\s*\\$?\\s*[\\d,]{1,12}(\\.\\d{1,2})?\\s*$",
      "description": "dollar amount, e.g. \"$360,000\""
    },
    "amortization": {
      "enum": [
        "FIXED",
        "ARM"
      ],
      "type": "string"
    },
    "high_balance": {
      "type": "boolean",
      "description": "true if the loan is above the county baseline (high-balance)"
    },
    "property_type": {
      "enum": [
        "SFR",
        "CONDO",
        "MANUFACTURED",
        "UNITS_2_4"
      ],
      "type": "string"
    },
    "first_time_homebuyer": {
      "type": "boolean"
    },
    "subordinate_financing": {
      "type": "boolean",
      "description": "true if there is a second lien (CLTV above LTV)"
    }
  },
  "additionalProperties": false
}
    arguments 73 lines
  • lender_lookup unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 120,
      "minLength": 3,
      "description": "part of the lender's legal name, e.g. \"Wells Fargo\", or its 20-character LEI"
    },
    "state": {
      "type": "string",
      "pattern": "^[A-Za-z]{2}$",
      "description": "optional: only lenders with HMDA records for property in this state"
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • county_lending_market unknown 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "year": {
      "type": "integer",
      "maximum": 2100,
      "minimum": 2018,
      "description": "optional HMDA filing year; defaults to the latest published"
    },
    "state": {
      "type": "string",
      "pattern": "^[A-Za-z]{2}$",
      "description": "two-letter state code, needed with county"
    },
    "county": {
      "type": "string",
      "maxLength": 80,
      "minLength": 2,
      "description": "county name, e.g. \"Bexar\" or \"Los Angeles County\"; give state too"
    },
    "county_fips": {
      "type": "string",
      "pattern": "^\\d{5}$",
      "description": "5-digit county FIPS code, e.g. \"48029\" for Bexar County, TX"
    }
  },
  "additionalProperties": false
}
    arguments 28 lines
  • loan_limit unknown 1h ago

    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), and the DealMatcher page to cite. Give a 5-digit county FIPS code, or a county name with its two-letter state.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "state": {
      "type": "string",
      "pattern": "^[A-Za-z]{2}$",
      "description": "two-letter state code, needed with county"
    },
    "county": {
      "type": "string",
      "maxLength": 80,
      "minLength": 2,
      "description": "county name, e.g. \"Bexar\" or \"Los Angeles County\"; give state too"
    },
    "county_fips": {
      "type": "string",
      "pattern": "^\\d{5}$",
      "description": "5-digit county FIPS code, e.g. \"48029\" for Bexar County, TX"
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 779f1ffe4003afe1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/779f1ffe4003afe1/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/779f1ffe4003afe1/badge.svg)](https://brick.blue/agent/779f1ffe4003afe1?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.