LiquiLens MCP Client: Bank Asset-Quality Evidence Review (n8n)

Instantly fetch and validate a bank’s asset-quality evidence record with LiquiLens (MCP) in n8n

Need a complete, evidence-backed research record for a covered bank? This LiquiLens MCP Client: Bank Asset-Quality Evidence Review manual workflow retrieves the specified bank’s asset-quality evidence from the LiquiLens MCP API, validates the returned structure, and outputs a full-context record—ready for your downstream review in n8n.

What this workflow does

• Manually runs when you execute the workflow in n8n.
• Calls the LiquiLens MCP endpoint (https://api.liquilens.in/mcp) requesting an asset-quality evidence review for a given bank slug (e.g., a covered institution such as “cosmos-ucb”).
• Validates response structure against the LiquiLens bank-specialisation evidence schema, and stops if an error or unexpected structure is returned.
• Outputs the complete evidence record unchanged, preserving key details such as reporting periods, source documents, retrieval dates, availability status, nulls, missing-figure flags, eligibility markers, and interpretation limits.

Use cases

• Research and due-diligence teams verifying bank asset-quality evidence for specific institutions.
• Automation engineers building a “request → validate → review” pipeline for LiquiLens evidence records in n8n.
• SaaS operators who need consistent retrieval of evidence, including interpretation limits, before using any returned figures.

Technical details

• n8n workflow type: Manual execution trigger.
• MCP client: Configured with authentication set to None (public read-only endpoint).
• Endpoint URL: https://api.liquilens.in/mcp
• Bank selection: Set the bank slug (optionally include_history) to match an institution covered by LiquiLens’s banking_specialisation_coverage tool.
• Validation: Uses the Code node and workflow logic to confirm the response matches the LiquiLens schema.

Note: Inspect the final research record and its source documents before using any figures returned by the workflow.