Overview
Mortgage Rate provides current and historical mortgage rate data from 1971 to present. The data comes from Freddie Mac's Primary Mortgage Market Survey, which has tracked mortgage rates weekly since the early 1970s. Use this for mortgage calculations, market analysis, and financial planning.
Live Test Mortgage Rate Grounding Data Source →
The tool
Once your client is connected to the VerveContext server, this appears in its tool list as MortgageRateGroundingData. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.
{
"name": "MortgageRateGroundingData",
"arguments": {
"type": "30year"
}
}You do not name the tool yourself; the model picks it. Asking about 30year in the terms this source covers is enough for it to reach for MortgageRateGroundingData on its own — naming it explicitly also works, and is the way to force the call.
Connecting
One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.
{
"mcpServers": {
"vervecontext": {
"url": "https://api.vervecontext.com/v1/mcp"
}
}
}https://api.vervecontext.com/v1/mcpPer-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.
Arguments
These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.
| Argument | Type | Description |
|---|---|---|
typeRequired | string | The mortgage type30year15year |
yearOptionalPremium | integer | Year to retrieve rates for (1971-present). Requires month parameter. range 1971–2030 |
monthOptionalPremium | integer | Month to retrieve rates for (1-12). Required when year is specified. range 1–12 |
What the model gets back
The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.
{
"status": "ok",
"error": null,
"data": {
"rateType": "30year",
"name": "30-Year Fixed Rate Mortgage",
"term": 30,
"type": "fixed",
"country": "US",
"year": 2023,
"month": 6,
"count": 4,
"rates": [
{
"week": "2023-06-01",
"rate": 6.79
},
{
"week": "2023-06-08",
"rate": 6.71
},
{
"week": "2023-06-15",
"rate": 6.69
},
{
"week": "2023-06-22",
"rate": 6.67
}
],
"change1w": -0.02,
"changeDirection": "down",
"previousRate": 6.69,
"previousDate": "2023-06-15"
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
rateType | string | 30year | Mortgage rate type identifier (30year or 15year) |
name | string | 30-Year Fixed Rate Mortgage | Human-readable description of mortgage type |
term | number | 30 | Loan term in years (15 or 30) |
type | string | fixed | Rate type classification (fixed or adjustable) |
country | string | US | Country code where rates apply (US) |
year | number | 2023 | Year of the mortgage rate data |
month | number | 6 | Month of the mortgage rate data (1-12) |
count | number | 4 | Number of weekly rate entries in response |
rates | array[4] | Array of weekly mortgage rate data entries | |
rates.0.week | string | 2023-06-01 | Week date in YYYY-MM-DD format |
rates.0.rate | number | 6.79 | Mortgage interest rate as percentage |
change1wPremium | number | -0.02 | Rate change from previous week in percentage points |
changeDirection | string | down | Direction of weekly change: up, down, or unchanged |
previousRatePremium | number | 6.69 | Previous week's mortgage interest rate |
previousDatePremium | string | 2023-06-15 | Previous week's date in YYYY-MM-DD format |
Why ground on it
A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.
Point an evaluation at rateType: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.
Failure modes
Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.
| Status | What it means |
|---|---|
400 / 422 | The arguments did not validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Blocked by a key restriction or an IP allow-list. Never a bad identity. |
404 | This source is not part of VerveContext. Check the catalog. |
429 | Out of credits, or a brief rate limit. The message tells them apart. |
A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.
Use cases
- Home Listing Calculators
- Populate monthly payment estimates across real estate portals by feeding current 30-year fixed rates into listing mortgage calculators.
- Refinance Comparison Portals
- When evaluating refinancing offers, mortgage brokers compare current 15-year and 30-year rates to highlight interest savings for homeowners.
- Borrower Rate Alerts
- To help homebuyers time their financing, personal finance platforms track weekly rate trend directions and notify borrowers when costs drop.
- Housing Market Newsletters
- Property investment newsletters graph weekly mortgage percentage changes against pending sales to assess shifts in buyer purchasing power.
Other ways to use Mortgage Rate Grounding Data
Set up Mortgage Rate Grounding Data on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.
Related
More in Finance: