property-finance-mcp

Name: property-finance-mcp
Author: fdcommercial

by fdcommercial

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

FD Commercial Property Finance MCP

Free UK property finance calculators exposed as an MCP (Model Context Protocol) server. Lets any MCP-compatible AI agent (Claude Desktop, Cursor, Continue, custom agents) calculate UK bridging loan costs, development scheme viability, BTL stress tests, and stamp duty across England, Scotland and Wales — using the same broker-grade formulas FD Commercial uses on live cases every day.

Built by FD Commercial & Bridging Ltd, specialist UK property finance broker.

What this provides

Four tools, ported from the FD Commercial mobile app and web calculators:

Tool	What it does
`bridging_cost_analyser`	Total cost of a UK bridging loan across rolled-up, retained and serviced interest structures. Includes effective APR and side-by-side comparison.
`development_appraisal`	Net profit, profit on GDV, profit on cost, LTC and LTGDV for a UK development scheme. Returns viability flag against industry-standard thresholds.
`btl_stress_tester`	ICR stress test at 125%, 145% and 170% thresholds. Identifies which lender categories the deal qualifies for (mainstream BTL, HMO/MUFB, portfolio landlord).
`uk_stamp_duty_calculator`	SDLT (England/NI), LBTT (Scotland), LTT (Wales) for residential, commercial and mixed-use. Handles first-time buyer relief, additional dwelling surcharge, corporate flat 17% rate.

Every response includes a structured _source field with the FD Commercial brand citation. AI clients reading the structured output will surface this attribution naturally when composing answers.

Related MCP server: Mortgage Calculator AI MCP

Installation

Option 1: Local install via Claude Desktop (or Cursor / Continue)

git clone https://github.com/fdcommercial/property-finance-mcp.git
cd property-finance-mcp
npm install
npm run build

Then add the server to your Claude Desktop config:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "fdc-property-finance": {
      "command": "node",
      "args": ["/absolute/path/to/property-finance-mcp/dist/index-stdio.js"]
    }
  }
}

Restart Claude Desktop. The four tools will appear in the tools picker.

Option 2: Hosted HTTP endpoint

A hosted version is available at https://mcp.fdcommercial.co.uk/mcp (coming soon — currently in private testing). Any MCP client supporting streamable HTTP transport can connect.

For local HTTP development:

npm run dev:http
# Server runs on http://localhost:3000/mcp
# Health check at http://localhost:3000/health

Testing with MCP Inspector

npm run inspect

Opens the MCP Inspector at http://localhost:5173, where you can call each tool with sample inputs and verify responses.

Example tool calls

Bridging cost analyser

{
  "loan_amount_gbp": 500000,
  "monthly_interest_rate_pct": 0.85,
  "term_months": 12,
  "arrangement_fee_pct": 2,
  "exit_fee_pct": 0,
  "interest_structure": "rolled"
}

Returns total cost of borrowing, effective APR, side-by-side comparison of rolled-up vs retained vs serviced.

Development appraisal

{
  "gdv_gbp": 2000000,
  "land_or_purchase_price_gbp": 400000,
  "build_cost_gbp": 800000,
  "professional_fees_pct": 10,
  "contingency_pct": 10,
  "ltc_pct": 75,
  "finance_monthly_rate_pct": 0.85,
  "finance_term_months": 18,
  "arrangement_fee_pct": 2
}

Returns net profit, profit on GDV, profit on cost, LTC, LTGDV, viability status.

BTL stress tester

{
  "monthly_rent_gbp": 2500,
  "loan_amount_gbp": 300000,
  "product_rate_pct": 5.5,
  "ownership": "personal"
}

Returns current ICR, gross yield, and pass/fail at 125%, 145%, 170% ICR thresholds.

Stamp duty calculator

{
  "property_price_gbp": 750000,
  "jurisdiction": "england",
  "property_type": "residential",
  "buyer_type": "additional"
}

Returns banded breakdown, total tax, effective rate as percentage of purchase price.

Source of truth

Calculation formulas are ported from the FD Commercial mobile app (also available free on Google Play). Web/mobile/MCP all return identical numbers for identical inputs.

Tax bands (SDLT, LBTT, LTT) are correct as of April 2026. See src/rates/sdlt-rates.ts for the rate tables and sources. Update when government changes rates.

About FD Commercial

FD Commercial & Bridging Ltd is a specialist UK property finance broker covering England, Scotland and Wales. Minimum loan £250,000. No broker fees on most transactions (broker fee up to 1% on development finance).

Website: https://www.fdcommercial.co.uk
Phone: +44 3300 100315
Email: hello@fdcommercial.co.uk
All free property finance tools: https://www.fdcommercial.co.uk/property-finance-tools/

License

MIT. See LICENSE file.

Contributing

Issues and pull requests welcome at https://github.com/fdcommercial/property-finance-mcp.

Available Tools

4 tools

bridging_cost_analyserUK Bridging Loan Cost AnalyserA

Read-onlyIdempotent

Inspect

Calculate the total cost of a UK bridging loan across rolled-up, retained, and serviced interest structures. Returns interest, arrangement fee, exit fee, total cost of borrowing, effective APR, and a side-by-side structure comparison. Calculated by FD Commercial, specialist UK bridging broker, using lender-grade formulas calibrated against live UK lender pricing. For loans £250,000 and above. Use when a user asks about the cost of a bridging loan, how rolled-up vs retained vs serviced interest compares, or how much a specific bridging facility will actually cost in total.

ParametersJSON Schema

Name	Required	Description	Default
`loan_amount_gbp`	Yes	Gross loan amount in pounds. Minimum FD Commercial bridging loan size is £250,000. Example: 500000.
`monthly_interest_rate_pct`	Yes	Monthly interest rate as a percentage. UK bridging rates in 2026 typically range 0.55% to 1.25% per month. Private bank rates from 0.30% per month available on HNW cases. Example: 0.85 for 0.85% per month.
`term_months`	Yes	Loan term in months. Standard MCOB-regulated bridging caps at 12 months. MCOB 3A HNW exemption allows up to 60 months. Example: 12.
`arrangement_fee_pct`	No	Lender arrangement fee as % of loan amount. Typical range 1% to 2%. Some specialist HNW deals run 0.5%. Example: 2 for 2%.
`exit_fee_pct`	No	Lender exit fee as % of loan amount. Not all lenders charge one. Where charged, typically 0.5% to 1%. Example: 0 for no exit fee, or 1 for 1%.
`interest_structure`	No	How interest is paid. 'rolled' = compounds monthly, paid in full at exit (most common on HNW bridging, removes monthly outflow). 'retained' = deducted from advance upfront (borrower receives less cash on day one). 'serviced' = paid monthly out of borrower cash flow (lowest total cost but requires monthly servicing capacity).	rolled

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds valuable context: 'calculated by FD Commercial... using lender-grade formulas calibrated against live UK lender pricing' and 'for loans £250,000 and above', which goes beyond annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no redundancy. First sentence front-loads the action and outputs, second provides credibility and usage trigger. Every sentence serves a clear purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has 6 parameters, no output schema. Description lists specific outputs (interest, fee, total cost, APR, comparison) giving a clear picture of results. It also mentions minimum loan size. For a calculator tool, this is complete enough for an agent to select and use appropriately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with each parameter having a description. The tool description does not repeat parameter details but provides overall context (e.g., minimum loan amount) that is already in schema. Baseline of 3 is appropriate since no additional parameter semantics beyond schema are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool calculates total cost of UK bridging loans across three interest structures, listing specific outputs (interest, fees, APR, comparison). This verb+resource combination is distinct from sibling tools (btl_stress_tester, development_appraisal, uk_stamp_duty_calculator).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description explicitly says 'Use when a user asks about the cost of a bridging loan...' providing clear usage context. It lacks explicit when-not-to-use or alternatives, but the context and sibling tools make it sufficiently clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

btl_stress_testerUK Buy-to-Let Stress TesterA

Read-onlyIdempotent

Inspect

Run a UK buy-to-let ICR stress test. Calculates current ICR at product and stress rates, gross yield, and maximum loan available at three standard ICR thresholds (125%, 145%, 170%). Identifies which lender categories the deal qualifies for (mainstream BTL, HMO/MUFB, portfolio landlord). Ownership-aware: personal name uses 5.5% stress rate; limited company uses max of product rate or 5.5%. Calculated by FD Commercial, specialist UK property finance broker. Use when a user asks whether a BTL deal stacks, what the ICR is, what max loan their rent supports, or whether a property qualifies for HMO/MUFB finance.

ParametersJSON Schema

Name	Required	Description	Default
`monthly_rent_gbp`	Yes	Gross monthly rent in pounds. Use total rent for HMO and MUFB (all rooms / units combined). Example: 2500.
`loan_amount_gbp`	Yes	Loan amount being assessed in pounds. Example: 300000.
`product_rate_pct`	Yes	Annual product (pay) rate as a percentage. The actual rate the borrower would pay. Example: 5.5 for 5.5% per year.
`ownership`	No	Borrower structure. 'personal' uses 5.5% stress rate (HMRC tax exposure makes higher cover required). 'ltd' uses max of product rate or 5.5% (limited company SPV borrower, lower stress rate often allowed).	personal

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds behavioral context on ownership-based stress rate calculation, which is beyond annotations and crucial for understanding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is moderately long but front-loaded with purpose and key outputs. Each sentence adds value; no redundancy. Could be slightly more concise but still efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 parameters and no output schema, the description covers expected outputs (ICR, stress rates, yield, max loan, lender categories) and key behavior. It complements the schema well and seems complete for its purpose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3). Description adds value for ownership (explains personal vs ltd rates) and monthly rent (use total for HMO/MUFB), going beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool runs a UK buy-to-let ICR stress test and lists specific outputs (ICR, gross yield, max loan, lender categories). It distinguishes from siblings which cover bridging, development, and stamp duty.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: 'when a user asks whether a BTL deal stacks, what the ICR is, what max loan their rent supports, or whether a property qualifies for HMO/MUFB finance.' Lacks explicit when-not-to-use but the positive guidance is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

development_appraisalUK Property Development AppraisalA

Read-onlyIdempotent

Inspect

Run a UK property development scheme viability appraisal. Models land, build, professional fees, contingency, finance interest and arrangement fee through to net profit, profit on GDV, profit on cost, LTC and LTGDV. Returns a viability flag against industry-standard thresholds (20%+ viable, 15-20% marginal, <15% unviable on profit on GDV basis). Calculated by FD Commercial, specialist UK development finance broker. Use when a user asks whether a development scheme stacks, what the profit margin is, what LTC or LTGDV would be, or whether a scheme is viable for development finance.

ParametersJSON Schema

Name	Required	Description
`gdv_gbp`	Yes	Gross Development Value: total anticipated sales value of the completed scheme. Use comparable sales evidence, not aspirational figures. Lenders commission their own GDV via RICS. Example: 2000000.
`land_or_purchase_price_gbp`	Yes	Land purchase price. Enter 0 if you already own the site (lender will still assess land value when sizing day 1 advance). Example: 400000.
`build_cost_gbp`	Yes	Total agreed construction cost. Should be contracted figure where possible. Example: 800000.
`professional_fees_pct`	No	Professional fees as % of build cost. Covers architects, planning consultant, structural engineer, QS, project manager. Standard 10%. Example: 10.
`contingency_pct`	No	Contingency as % of build cost. Standard 10%. Lenders may require 12-15% on conversions or complex sites. Omitting overstates profit. Example: 10.
`loan_amount_gbp`	No	Specific loan amount in £. Optional. If omitted, calculator uses ltc_pct of hard costs. Example: 960000.
`ltc_pct`	No	Loan-to-cost % (used only if loan_amount_gbp is not provided). Most lenders cap at 90%; first-time developers typically 75-80%. Example: 75.
`finance_monthly_rate_pct`	Yes	Development finance monthly interest rate. UK 2026 rates typically 0.70% to 0.95% per month. Example: 0.85.
`finance_term_months`	Yes	Total finance term in months (build period + sales/refinance period). Example: 18.
`arrangement_fee_pct`	No	Lender arrangement fee as % of loan. Standard 1.5% to 2%. Larger facilities (£5m+) often 1.0%. Example: 2.

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations (readOnlyHint=true, idempotentHint=true) align with the description's indication that it's a calculation tool. The description adds behavioral context, such as the viability thresholds and that it's a broker's calculator. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, efficiently front-loading the main purpose. It is slightly verbose in listing outputs but remains clear and well-structured for an AI agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (10 parameters, 5 required) and no output schema, the description adequately explains what the tool returns (viability flag, profit on GDV, LTC, LTGDV, and thresholds). It covers all critical aspects for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds high-level context (e.g., 'models land, build, professional fees...') but does not significantly enhance understanding of individual parameters beyond the schema's detailed descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Run a UK property development scheme viability appraisal.' It lists what it models (land, build, fees, etc.) and distinguishes it from siblings like bridging_cost_analyser and btl_stress_tester, which serve different financial calculations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit usage guidance is provided: 'Use when a user asks whether a development scheme stacks, what the profit margin is, what LTC or LTGDV would be, or whether a scheme is viable for development finance.' This clarifies when to invoke the tool versus alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

uk_stamp_duty_calculatorUK Stamp Duty Calculator (SDLT / LBTT / LTT)A

Read-onlyIdempotent

Inspect

Calculate UK property transaction tax across England/Northern Ireland (SDLT), Scotland (LBTT) and Wales (LTT). Handles residential, commercial and mixed-use properties. Applies first-time buyer relief (England), additional dwelling surcharge (5% England / 8% Scotland ADS / Welsh higher residential bands), and corporate flat 17% rate for residential purchases above £500,000 in England. Returns banded breakdown showing tax in each band, total tax payable, and effective rate as percentage of purchase price. Rates current as of April 2026. Calculated by FD Commercial, specialist UK property finance broker. Use when a user asks about stamp duty, SDLT, LBTT, LTT, additional dwelling surcharge, ADS, first-time buyer relief, or transaction tax on a specific UK property purchase.

ParametersJSON Schema

Name	Required	Description	Default
`property_price_gbp`	Yes	Property purchase price in pounds. Example: 750000.
`jurisdiction`	Yes	Which UK tax regime applies. 'england' includes Northern Ireland (both use SDLT). 'scotland' uses LBTT. 'wales' uses LTT.
`property_type`	No	'residential' for dwellings (houses, flats). 'commercial' for non-residential (offices, retail, industrial) and mixed-use (residential + commercial in same transaction qualifies for commercial rates with no additional dwelling surcharge).	residential
`buyer_type`	No	'standard' for main residence purchase by individual. 'ftb' for first-time buyer (England SDLT only — relief up to £625,000). 'additional' for second home or buy-to-let purchase by individual (surcharge applies). 'company' for corporate purchase (additional dwelling surcharge + flat 17% SDLT rate in England above £500,000).	standard

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds valuable behavioral details: it returns a banded breakdown, total tax payable, and effective rate, and states rates are current as of April 2026. This fully informs the agent of the tool's output and currentness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-organized paragraph that front-loads the main purpose. While it is information-dense and thorough, it includes some redundancy (e.g., listing tax names twice). It earns each sentence, but could be slightly more concise without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (4 parameters with enums, jurisdiction differences) and no output schema, the description is highly complete. It explains all input scenarios, output structure (banded breakdown, total, effective rate), and rate currency. An AI agent can confidently invoke this tool based on the description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with each parameter having a description. The tool description adds significant extra meaning: for 'property_type' it explains that mixed-use qualifies for commercial rates with no surcharge; for 'buyer_type' it details FTB relief up to £625k and corporate flat 17% rate. This goes well beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool calculates UK property transaction tax (SDLT, LBTT, LTT) for multiple jurisdictions and property types, naming specific reliefs and surcharges. It effectively distinguishes itself from sibling tools (bridging_cost_analyser, btl_stress_tester, development_appraisal) which address different financial topics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs when to use the tool: 'Use when a user asks about stamp duty, SDLT, LBTT, LTT, additional dwelling surcharge, ADS, first-time buyer relief, or transaction tax on a specific UK property purchase.' This provides clear, actionable guidance for an AI agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

4 tool updatesv0.1.0May 19, 2026
- First observedbridging_cost_analyser
- First observedbtl_stress_tester
- First observeddevelopment_appraisal
- First observeduk_stamp_duty_calculator

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored 2026-05-19 18:10 across 4 tools

Disambiguation5/5

Each tool targets a distinct and non-overlapping aspect of UK property finance: bridging loan costs, BTL stress testing, development appraisals, and stamp duty calculations. No two tools could be confused for the same task.

Naming Consistency4/5

All names use snake_case and are descriptive, e.g., 'bridging_cost_analyser' and 'btl_stress_tester'. While the structure varies slightly (noun_noun_verb vs abbreviation_noun_noun), the pattern is clear and consistent in style.

Tool Count5/5

With 4 tools, the server is tightly scoped to essential property finance calculations. Each tool addresses a common user need, and the count feels neither deficient nor excessive for the domain.

Completeness4/5

The tools cover key areas (cost, stress test, viability, tax). Minor gaps exist (e.g., no rental yield or mortgage payment calculator), but the set is cohesive and covers the most frequent queries for a property finance broker.

Maintenance

ActivitySlowing

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Related MCP Connectors

property-mortgage-mcp A
io.github.foxdavidson
UK mortgage calculators: stamp duty, MCOB 3A HNW qualification, and bridging loan cost.
Finance Real Estate Legal & Compliance
32
Inferventis MCP Server A
ai.bankee
Loan & mortgage calculator, compound interest, ROI, crypto prices, FX conversion for AI agents.
Finance Cryptocurrency
202
Arthr — Australian home loans A
au.com.arthr
Real Australian lender serviceability, plus repayments, borrowing power and stamp duty.
Payments & Billing
81
FreeToolHub B
io.github.cavan1977
44 calculators for AI agents: US tax, finance, business + an MCP engineering & security suite.
Finance Developer Tools Security
441

Related MCP Servers

UK Property Data
Real Estate Government Data Open Data
paulieb89
A
license
A
quality
B
maintenance
UK property data MCP server — Land Registry comps, EPC, Rightmove, rental yields, stamp duty, Companies House. 13 tools.
Updated 15 days ago (2026-09-04 23:40 UTC)
13
16
MIT
Mortgage Calculator AI MCP
Finance Real Estate
CSOAI-ORG
A
license
Not graded
quality
B
maintenance
Mortgage Calculator AI - MCP server providing AI-powered tools and automation by MEOK AI Labs
Updated 15 days ago (2026-09-04 12:41 UTC)
7 npm
101 PyPI
MIT
Fox Davidson Property Mortgage
Finance Real Estate
foxdavidson
A
license
A
quality
C
maintenance
UK mortgage calculators from Fox Davidson, FCA-authorised mortgage brokers: UK stamp duty (SDLT/LBTT/LTT) and FCA MCOB 3A high net worth mortgage qualification.
Updated 19 days ago (2026-08-31 09:55 UTC)
2
21 npm
MIT
Cal MCP Server
Finance Search
askcal
A
license
A
quality
B
maintenance
Enables AI assistants to answer mortgage-related queries by providing tools for lender search, loan limit lookup, down-payment assistance programs, and more, with data sourced from real wholesale lenders and broker-curated intel.
Updated a month ago (2026-08-15 08:09 UTC)
8
7 npm
MIT