AINumbers.co Mortgage Servicing API
The mortgage-servicing API from AINumbers.co — 2 operation(s) for mortgage-servicing.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/ainumbers-co:ainumbers-co-mortgage-servicing-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: AINumbers.co Fintech Intelligence Suite Mortgage Servicing…
version: 1.0.0
description: '**1255 fintech intelligence tools** covering ISO 20022, A2A payments, CFPB §1033, EU AI Act, DORA, MiCA, AML/KYC, BaaS, DLT/tokenization, ESG/climate finance, agentic payments (AP2, ACP, x402, Visa TAP, Mastercard Agent Pay), PQC migration, sanctions screening, and OpenChainGraph v0.4 computation chains.
## Transport
> **The live transport is MCP JSON-RPC 2.0 at `https://mcp.ainumbers.co/mcp` — not REST.**
>
> This OpenAPI file is a **descriptive data-room artifact** — a machine-readable index of all tools and their input/output schemas. The REST paths (`POST /v1/tools/{name}`) described here are a projection; they become functional only if the optional REST shim (Area 2 Path B) is deployed.
>
> To call tools today, connect via the official MCP client SDKs. TypeScript: `@modelcontextprotocol/sdk`. Python: `mcp`.
## Architecture
All tools run **entirely client-side** (browser JavaScript). Zero PII. Zero server calls after page load. Deterministic, reproducible outputs. Licensed CC BY 4.0.
OpenChainGraph v0.4 compute-binding nodes additionally run **server-side on the MCP Worker** and emit verifiable artifacts with `execution_hash` (WebCrypto SHA-256 over RFC 8785 canonical JSON).'
contact:
name: Post Oak Labs
url: https://postoaklabs.com
email: tim@postoaklabs.com
license:
name: CC BY 4.0
url: https://creativecommons.org/licenses/by/4.0/
servers:
- url: https://ainumbers.co
description: Static browser-based tool host (DreamHost). Tools run client-side — no REST gateway is active on this origin. See x-mcp for the live MCP endpoint.
tags:
- name: mortgage-servicing
paths:
/v1/tools/servicing_compliance_clock:
post:
operationId: servicing_compliance_clock
summary: Servicing Compliance Clock
description: 'Computes servicer-compliance due dates and clock states from event dates and loan values across the Regulation X/Z servicing rules: error-resolution, information-request, loss-mitigation, foreclosure-timeline, force-placed-insurance, reminder, cancel, refund, payment-crediting, payoff-statement and ARM notice clocks. Every obligation carries its paragraph citation, a named business-day calendar assumption and its due window; invalid dates and over-bound event sets are refused, never computed.
**Tool URL:** https://ainumbers.co/chaingraph/733-servicing-compliance-clock.html
**AP2/Policy Mandate export:** yes'
tags:
- mortgage-servicing
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- events
properties:
events:
type: array
maxItems: 32
items:
type: object
required:
- rule
- trigger_date
properties:
rule:
type: string
trigger_date:
type: string
action_date:
type: string
error_category:
type: integer
request_type:
type: string
foreclosure_sale_date:
type: string
extension_notice_given:
type: boolean
charge_date:
type: string
initial_notice_date:
type: string
first_adjusted_payment_date:
type: string
consummation_date:
type: string
adjustment_frequency_days:
type: integer
originated_before_2015_01_10:
type: boolean
index_figure_lt_45_days:
type: boolean
first_adjustment_within_60_days_of_consummation:
type: boolean
disclosed_rate_was_estimate:
type: boolean
prior_complete_application_date:
type: string
continuously_delinquent_since:
type: boolean
description: 'Event list, at most 32: rule id, strict ISO trigger date, rule-specific parameters.'
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
verdict:
type: string
obligations:
type: array
items:
type: object
properties:
rule:
type: string
cited_paragraph:
type: string
basis:
type: string
calendar:
type:
- string
- 'null'
trigger_date:
type: string
due_date:
type:
- string
- 'null'
action_date:
type:
- string
- 'null'
state:
type: string
state_reason:
type:
- string
- 'null'
obligation_owed:
type: boolean
window_start_date:
type:
- string
- 'null'
window_variant:
type: string
days_allowed:
type: integer
days_before_sale:
type:
- integer
- 'null'
earliest_lawful_first_notice_date:
type: string
evidence:
type: object
manual_review_required:
type: boolean
x-mcp-tool-name: servicing_compliance_clock
x-tool-url: https://ainumbers.co/chaingraph/733-servicing-compliance-clock.html
x-source: manifest
x-ap2-export: true
/v1/tools/check_force_placed_notice:
post:
operationId: check_force_placed_notice
summary: Force-Placed Insurance Notice Checker
description: 'Checks a lender-placed insurance event against the 12 CFR 1024.37 notice sequence: the 45-day advance first notice with its prescribed content set, the reminder notice at least 15 days before the charge and at least 30 days after the first notice, the no-evidence precondition, the 15-day cancel-and-refund clock with pro-rata overlapping-coverage refund, and a values-only premium benchmark against the borrower alternative quote. Never labels a premium reasonable; missing values are refused.
**Tool URL:** https://ainumbers.co/chaingraph/art-734-force-placed-insurance-checker.html
**AP2/Policy Mandate export:** yes'
tags:
- mortgage-servicing
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- first_notice_date
- reminder_notice_date
- charge_date
- charged_premium_amount
- charge_coverage_start
- charge_coverage_end
properties:
first_notice_date:
type: string
reminder_notice_date:
type: string
charge_date:
type: string
charged_premium_amount:
type: number
charge_coverage_start:
type: string
charge_coverage_end:
type: string
alternative_quote_amount:
type: number
evidence_of_continuous_coverage_date:
type: string
borrower_coverage_start:
type: string
borrower_coverage_end:
type: string
cancellation_date:
type: string
refund_date:
type: string
refund_amount:
type: number
notice_mail_class:
type: string
first_notice_content_items:
type: array
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
verdict:
type: string
elements:
type: array
items:
type: object
properties:
element_id:
type: string
cited_paragraph:
type: string
requirement:
type: string
state:
type: string
premium_benchmark:
type:
- object
- 'null'
refund_evaluation:
type:
- object
- 'null'
charge_summary:
type: object
evidence:
type: object
manual_review_required:
type: boolean
x-mcp-tool-name: check_force_placed_notice
x-tool-url: https://ainumbers.co/chaingraph/art-734-force-placed-insurance-checker.html
x-source: manifest
x-ap2-export: true
x-mcp:
transport: MCP JSON-RPC 2.0 (streamable HTTP)
endpoint: https://mcp.ainumbers.co/mcp
protocol_version: '2025-11-25'
authentication: none
registry: co.ainumbers/tools (official MCP registry)
note: Connect any MCP-compatible client (Claude, ChatGPT, custom agent) directly to this endpoint. The REST paths in this file are descriptive only — they do not exist on the live server unless the REST shim is deployed.