A
license-
qualityC
maintenanceBroker-only credit/lending discovery shim for AI agents, surfacing real lending markets from licensed/established third-party protocols and routing applications.
MIT
IncredibleFi — Personal Loan Marketplace
Server Details
AI-powered loan marketplace. Match users with 100+ lenders — any credit score or employment status.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.1/5.0
Tool DescriptionsA
Average 4.2/5 across 3 of 3 tools scored.
Server CoherenceA
Disambiguation5/5
Each tool serves a distinct role: fetching form fields, submitting additional information, and submitting the loan application. No overlap or ambiguity exists between them.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern (get_, submit_, submit_). The names clearly indicate the action and target, with no mixed conventions.
Tool Count4/5
With only 3 tools, the set is minimal but still within the ideal 3-15 range. The tools cover the core flow without unnecessary bloat, though it feels slightly thin for a marketplace.
Completeness4/5
The tools cover the full loan application lifecycle: fetching required fields, submitting the application, and handling additional information requests. Minor gaps like status checking are not essential to the described purpose.
Available Tools
3 toolsget_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 | |||
Tool Definition Quality
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 | Default |
|---|---|---|---|
| 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 |
Tool Definition Quality
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 Marketing Partners. Consent is not required to purchase any goods or services."
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 | Default |
|---|---|---|---|
| city | Yes | City City of your current mailing address. | |
| 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. |
Tool Definition Quality
A4.3/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 the mandatory consent step, the return of a URL, the possibility of 'additional_information_needed', and includes the full legal disclosure text, making the side effects clear. It does not cover error cases or rate limits, but the key behaviors are well covered.
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 long due to the legally required disclosure text, but the text is essential for compliance and must be displayed verbatim. It front-loads the consent warning and provides actionable steps concisely after the disclosure. The structure is clear despite the length.
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 21 required parameters and no output schema, the description explains the tool's return behavior (URL or 'additional_information_needed') and consent requirements. It does not detail error scenarios or what to do next, but the core workflow is adequately described for an AI agent.
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% with detailed parameter descriptions. The description adds critical semantics for tcpaConsent, explicitly requiring explicit user agreement and explaining the consent workflow. This goes beyond the schema's basic description, adding meaningful context for the most sensitive parameter.
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 function: submitting a loan application after consent. It specifies the return value (URL) and the possible 'additional_information_needed' response, which distinguishes it from sibling tools like get_loan_application_fields and submit_additional_information.
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?
It provides a strict precondition (display disclosure and obtain explicit agreement) and explains when to set tcpaConsent to true. However, it does not explicitly reference sibling tools or state when not to use this tool, though the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityCmaintenanceConnect AI agents to real bank accounts across 15,000+ financial institutions for transactions, balances, investments, and loans.2MIT
- Flicense-qualityCmaintenanceLoan officer assistant that uses Claude AI and Plaid banking API to assess loan applicants by pulling financial data and returning structured eligibility verdicts.
- Alicense-qualityCmaintenanceUndercollateralized credit lines for autonomous agents based on trust scoring, enabling on-chain credit scoring, agent-to-agent loans, and USDC settlement on Base L2.MIT