IncredibleFi — Personal Loan Marketplace

Server Details

AI-powered loan marketplace. Match users with 100+ lenders — any credit score or employment status.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 100.0% over 42 days
Last Tested: 2026-09-28 13:44
Transport: Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.1/5.0

Scored 2026-09-13 04:25 across 3 tools

Disambiguation5/5

Each tool has a clearly distinct role: discovering the form schema, resubmitting additional info for a stalled application, and the primary application submission. The descriptions explicitly sequence them (call this first, requires token from that response, consent before calling), leaving little room for misselection.

Naming Consistency5/5

All three tools follow a consistent snake_case verb_noun pattern (get_loan_application_fields, submit_additional_information, submit_loan_application). The verb varies (get vs submit) but each matches its action, so the scheme is predictable.

Tool Count4/5

Three tools is on the thin side, but the server's scope is a narrow single-purpose loan application flow, and each tool maps to a distinct step with no filler. It is well-scoped rather than padded, just lacking any auxiliary operations.

Completeness4/5

The core lifecycle is covered: discover fields, submit, and handle the additional_information_needed follow-up, with a URL always returned so no dead end occurs. A status/result-retrieval operation for an in-flight application is the only noticeable gap.

Available Tools

3 tools

get_loan_application_fieldsAInspect

Get the loan application form fields, their types, allowed values, and validation rules. Call this first to understand what information is needed to submit a loan application.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses what the tool returns (fields, types, allowed values, validation rules) and implies a read-only, non-mutating operation via the verb 'Get' and the 'Call this first' guidance. It does not mention authentication or error behavior, but for a zero-parameter retrieval tool, the provided context is sufficient.

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?

The description is two sentences, front-loads the core purpose, and includes only essential details. Every word earns its place; there is no redundancy or unnecessary elaboration.

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?

For a simple zero-parameter, no-output-schema tool, the description fully covers what the agent needs: what it returns and when to call it. It references the relevant submission workflow, making the context complete without excess.

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?

The tool has zero parameters, so the description need not explain any. The baseline for zero-parameter tools is 4, and since no parameter information is required, this score is appropriate.

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 uses a specific verb ('Get') and explicitly names the resource ('loan application form fields'), along with the details returned (types, allowed values, validation rules). It clearly differentiates from the sibling submit tools by focusing on retrieval of form structure rather than submission.

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 instruction 'Call this first to understand what information is needed to submit a loan application' provides explicit when-to-use guidance, establishing this as a prerequisite before the submit tools. It implies the appropriate sequence relative to siblings, satisfying the usage guideline requirement.

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

submit_additional_informationAInspect

Submit additional information for a loan application that previously returned "additional_information_needed". Requires the application_reference token from that response.

ParametersJSON Schema

Name	Required	Description
`nextPayDate`	Yes	Your next pay date Format: YYYY-MM-DD. The date your next paycheck will be deposited. Must be today or within the next 31 days.
`ownsVehicle`	Yes	Whether you own a car, truck, or other vehicle — and whether it is paid off or financed. Natural language and synonyms are accepted. Options: Yes - paid off, Yes - making payments, No
`employerName`	Yes	Employer name Name of your current employer or business. For verification only — your employer will not be contacted.
`licenseState`	No	State that issued your driver's license Two-letter state abbreviation (e.g. CA, TX). Required if you have a driver's license.
`accountNumber`	Yes	Bank account number Your checking account number — found on a check or in your banking app. 4-25 digits. Used to deposit funds if matched.
`employerPhone`	Yes	Employer phone number 10-digit phone number for your employer. For verification only — your employer will not be contacted.
`licenseNumber`	No	Driver's license number 4-25 alphanumeric characters as printed on your license. Required if you have a driver's license.
`routingNumber`	Yes	Bank routing number 9-digit ABA routing number for your checking account — found at the bottom left of a check or in your banking app. Used to deposit funds if matched.
`hasDriverLicense`	Yes	Final identity check — one last step to see your offers. Natural language and synonyms are accepted. Options: Yes, No
`application_reference`	Yes	Reference token from the previous submit_loan_application response

TDQS

A3.7/5.0

Behavior2/5

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

There are no annotations, so the description carries the full burden of disclosing behavioral traits. It only mentions the token requirement and the context, but does not describe what happens after submission (e.g., expected response, side effects, whether it finalizes the application). This is a significant gap for a mutation tool.

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?

The description is two sentences that are direct, informative, and front-loaded with the purpose. No filler or redundancy, earning a top score.

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

Completeness3/5

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

The description covers when to use and what's required, but it does not mention the output or post-submission behavior, and there are no annotations or output schema to fill that gap. It also does not reference the sibling get_loan_application_fields, which could be a relevant prerequisite. Adequate but incomplete.

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?

The input schema has 100% coverage with detailed descriptions for every parameter, including formats, constraints, and examples. The description itself adds no additional parameter-level semantics beyond restating the token requirement, which is already in the schema. Baseline 3 is appropriate.

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 action (submit additional information), the resource (a loan application), and the specific condition that triggers this tool (previously returned 'additional_information_needed'). This distinguishes it from siblings like submit_loan_application (initial submission) and get_loan_application_fields (field fetching).

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?

The description provides a clear contextual trigger and a hard prerequisite: it requires the application_reference token from a previous response. However, it does not explicitly state when not to use the tool or mention alternatives, so it stops short of full usage guidance.

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

submit_loan_applicationAInspect

CONSENT REQUIRED BEFORE CALLING THIS TOOL. Before submitting a loan application, you MUST display the following disclosure to the user verbatim and obtain their explicit agreement (e.g. they say "I agree", "I consent", or "Yes"). Do NOT call this tool until the user has explicitly agreed.

DISCLOSURE: "By submitting this application, you: (1) consent to and agree with IncredibleFi's Terms of Service, Privacy Policy, Credit Authorization Agreement, E-Consent, Arbitration Notice, Advertiser Disclosure, and Personal Loan Notice; (2) certify that all information herein is true and complete; (3) provide written instructions under the Fair Credit Reporting Act for Acqscale, Inc. (IncredibleFi.com) and its Marketplace Partners with whom Acqscale, Inc. (IncredibleFi.com) connects you to obtain your consumer credit report from contracted Credit Bureau(s) associated with your pre-qualification for credit inquiry; (4) understand your information will be presented to a network of lenders and/or lending partners who will review and verify your information to determine if you may qualify for a loan, and that lenders and financial service providers may share your personal information including approval and funded status; and (5) provide express consent to recurring communication at the telephone number provided by Acqscale, Inc. (IncredibleFi.com) and its Marketplace Partners. Consent is not required to purchase any goods or services; and (6) understand that if you are not connected with a lender, your information may be shared with, and you may be contacted by, other financial service providers, debt relief providers, aggregators, and marketers offering products that are not loans, and that this consent to be contacted applies to them as well."

Once the user has explicitly agreed, set tcpaConsent to true and submit the application. This tool always returns a URL for the user: either a direct lender match or curated loan options. May return "additional_information_needed" with extra fields to improve matching.

ParametersJSON Schema

Name	Required	Description
`city`	Yes	City City of your current mailing address.
`email`	Yes	Email address Your email address. Kept private and secure — used to send your loan match results.
`phone`	Yes	Phone number 10-digit US mobile or home phone number. Cannot start with 0 or 1.
`state`	Yes	State Two-letter US state abbreviation (e.g. CA, TX, NY, FL).
`zipCode`	Yes	ZIP code 5-digit US ZIP code for your mailing address.
`lastName`	Yes	Last name Legal last name — required to verify your identity. 2-30 letters only.
`firstName`	Yes	First name Legal first name — required to verify your identity. 2-30 letters only.
`totalDebt`	Yes	Total outstanding unsecured debt (credit cards, personal loans, medical bills, etc.) — not including mortgage or auto loans. An estimate is fine. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: $20,000 or More, $15,000 - $20,000, $10,000 - $15,000, $5,000 - $10,000, $3,000 - $5,000, $2,000 - $3,000, $1,000 - $2,000, None
`loanAmount`	Yes	Amount in US dollars between $100 and $40,000. We'll find the best options for you based on this amount. Minimum: $100 Maximum: $40000
`creditScore`	Yes	All credit scores are welcome — including no credit history. This helps us match you with the right lenders. Checking does not impact your score. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: Excellent (720+), Good (660-719), Fair (600-659), Poor (Under 600), No credit or not sure
`dateOfBirth`	Yes	Date of birth Format: YYYY-MM-DD. Must be 18 or older. Required to verify your identity.
`loanPurpose`	Yes	Choose the option that best describes the primary reason for the loan. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: Bills, Purchases, Loan Repayment, Rent or Mortgage, Emergency Expenses, Debt Consolidation, Other, Home Improvement, Education, Travel, Medical Expense, Car Purchase, Business
`tcpaConsent`	Yes	Set to true ONLY after you have displayed the full TCPA/consent disclosure to the user verbatim and the user has explicitly agreed (e.g. said "I agree" or "I consent"). Never set this to true without explicit user agreement.
`directDeposit`	Yes	Whether your income is automatically deposited into your bank account by your employer or benefits provider. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: Yes, No
`homeOwnership`	Yes	Your current housing situation. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: Own, Rent
`monthlyIncome`	Yes	Your take-home pay after taxes, per month. An estimate is fine — this helps match you with lenders who fit your income level. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: $10,000 or More, $9,000 - $10,000, $8,000 - $9,000, $7,000 - $8,000, $6,000 - $7,000, $5,000 - $6,000, $4,000 - $5,000, $3,000 - $4,000, $2,500 - $3,000, $2,000 - $2,500, $1,500 - $2,000, Below $1,500
`streetAddress`	Yes	Street address Your current US mailing address — for verification only. Example: 123 Main St
`employmentStatus`	Yes	Choose what best applies. All employment types are accepted including benefits recipients and military. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: Employed, Self-employed, Unemployed, Active-duty military
`paymentFrequency`	Yes	Your pay schedule — how often income is deposited into your account. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: Monthly, Twice a month, Bi-weekly, Weekly
`hasCheckingAccount`	Yes	A checking account is typically required for loan deposit. Savings accounts do not qualify. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: Yes, No
`socialSecurityNumber`	Yes	Social Security Number 9-digit SSN with no dashes (e.g. 123456789). For identity verification only — does not impact your credit score. Transmitted with bank-level encryption.

TDQS

A3.9/5.0

Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose the return contract (always a URL; either direct lender match or curated options) plus the may-return additional_information_needed branch. It doesn't characterize irreversibility, rate limits, or re-submission behavior, though the embedded disclosure text does flag the credit-inquiry consequence.

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 critical action requirement is front-loaded and set in caps before any boilerplate. The verbatim disclosure is long, but it is a functional/legal requirement that must be reproduced exactly, and the closing behavioral sentence is tight and informative.

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?

For a 21-required-parameter, no-annotation, no-output-schema mutation tool, the definition covers the gating flow and the return shape adequately. It stops short of explaining the follow-up flow once additional_information_needed is returned, leaving that to the sibling tool.

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% and every parameter carries its own description, so the schema does the heavy lifting (baseline 3). The description only reiterates the tcpaConsent semantics already stated in the schema and adds no syntax or format detail beyond it.

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

Purpose4/5

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

The operative sentence — 'set tcpaConsent to true and submit the application' — states a clear verb and resource, and the mention of returning a lender match or 'additional_information_needed' implicitly distinguishes it from the submit_additional_information sibling. However, purpose is buried under the consent preamble rather than stated up front, and siblings are never named explicitly.

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?

Gives a hard precondition (display verbatim disclosure, obtain explicit agreement) and even supplies acceptable agreement phrasings ('I agree', 'I consent'). The additional_information_needed return value hints at when the sibling tool takes over, but routing to get_loan_application_fields or submit_additional_information is left to inference.

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.

1 tool updateMay 4, 2026

Changedsubmit_loan_application1 field changed

changedInput schema / properties / loanPurpose / description

Previous value: -"Choose the option that best describes the primary reason for the loan. Natural language and synonyms are accepted (e.g. \"fair\", \"consolidate debt\", \"biweekly\", \"4500\"). Options: Bills, Purchases, Debt Repayment, Rent or Mortgage, Emergency Expenses, Debt Consolidation, Other, Home Improvement, Education, Travel, Medical Expense, Car Purchase, Business"New value: +"Choose the option that best describes the primary reason for the loan. Natural language and synonyms are accepted (e.g. \"fair\", \"consolidate debt\", \"biweekly\", \"4500\"). Options: Bills, Purchases, Loan Repayment, Rent or Mortgage, Emergency Expenses, Debt Consolidation, Other, Home Improvement, Education, Travel, Medical Expense, Car Purchase, Business"

1 tool updateMay 3, 2026

Changedsubmit_loan_application1 field changed

changedInput schema / properties / loanPurpose / description

Previous value: -"Choose the option that best describes the primary reason for the loan. Natural language and synonyms are accepted (e.g. \"fair\", \"consolidate debt\", \"biweekly\", \"4500\"). Options: Debt Consolidation, Credit Card Payoff, Emergency Expenses, Major Purchases, Home Improvement, Education, Travel, Medical Expense, Car Purchase, Business, Other"New value: +"Choose the option that best describes the primary reason for the loan. Natural language and synonyms are accepted (e.g. \"fair\", \"consolidate debt\", \"biweekly\", \"4500\"). Options: Bills, Purchases, Debt Repayment, Rent or Mortgage, Emergency Expenses, Debt Consolidation, Other, Home Improvement, Education, Travel, Medical Expense, Car Purchase, Business"

1 tool updateMar 19, 2026

Changedsubmit_loan_application2 fields changed

addedInput schema / properties / tcpaConsent

Added value: +{
+  "description": "Set to true ONLY after you have displayed the full TCPA/consent disclosure to the user verbatim and the user has explicitly agreed (e.g. said \"I agree\" or \"I consent\"). Never set this to true without explicit user agreement.",
+  "type": "boolean"
+}

changedInput schema / required

Previous value: -[
-  "loanAmount",
-  "loanPurpose",
-  "monthlyIncome",
-  "totalDebt",
-  "creditScore",
-  "employmentStatus",
-  "paymentFrequency",
-  "streetAddress",
-  "city",
-  "state",
-  "zipCode",
-  "homeOwnership",
-  "hasCheckingAccount",
-  "directDeposit",
-  "firstName",
-  "lastName",
-  "dateOfBirth",
-  "email",
-  "phone",
-  "socialSecurityNumber"
-]New value: +[
+  "loanAmount",
+  "loanPurpose",
+  "monthlyIncome",
+  "totalDebt",
+  "creditScore",
+  "employmentStatus",
+  "paymentFrequency",
+  "streetAddress",
+  "city",
+  "state",
+  "zipCode",
+  "homeOwnership",
+  "hasCheckingAccount",
+  "directDeposit",
+  "firstName",
+  "lastName",
+  "dateOfBirth",
+  "email",
+  "phone",
+  "socialSecurityNumber",
+  "tcpaConsent"
+]

3 tool updatesMar 19, 2026
- First observedget_loan_application_fields
- First observedsubmit_additional_information
- First observedsubmit_loan_application

Related MCP Connectors

Hive Credit Broker
io.github.srotzin
Broker-only credit/lending discovery shim for AI agents
Finance AI & Machine Learning
2
MIDAS Protocol C
io.github.BbrainFrance
Complete financial infrastructure for AI agents — payments, lending, escrow & more.
Finance Payments & Billing
2
Cotribute MCPOAuth
com.cotribute
Connect AI agents to financial institution origination, analytics, and compliance workflows.
Finance CRM
2
VerifyRef
com.verifyref
AI agent recruiting: talent pool match, reference checks, credit packs via Stripe MPP
AI & Machine Learning Autonomous Agents Payments & Billing
2

Related MCP Servers

lenderwiki
Finance Search Research & Data
lenderwiki
A
license
Not graded
quality
D
maintenance
Query 13,000+ US consumer lenders with eligibility criteria, rates, CFPB complaints, and ratings. Find matching lenders by borrower profile, get full profiles, compare lenders, and check eligibility.
Updated 6 months ago (2026-04-10 06:09 UTC)
MIT
hive-mcp-credit-broker
Finance Cryptocurrency Blockchain
srotzin
A
license
Not graded
quality
C
maintenance
Broker-only credit/lending discovery shim for AI agents, surfacing real lending markets from licensed/established third-party protocols and routing applications.
Updated 5 months ago (2026-05-04 01:32 UTC)
MIT
BankSync MCP Server
banksynchq
A
license
Not graded
quality
C
maintenance
Connect AI agents to real bank accounts across 15,000+ financial institutions for transactions, balances, investments, and loans.
Updated 5 months ago (2026-04-30 21:39 UTC)
2
MIT
SolvScore MCP
Finance Blockchain Autonomous Agents
shawnhvac
A
license
Not graded
quality
B
maintenance
Lets AI agents check credit scores, request underwriting decisions, and review credit market stats, all via free unauthenticated tools on Base L2.
Updated a month ago (2026-08-25 19:24 UTC)
MIT

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?