Fix .gitignore excluding test data folder

Author: Steven Peh

mcp-openapi/.gitignore

@@ -109,11 +109,3 @@ jspm_packages/
 
 # TernJS port file
 .tern-port
-
-# Test files and configs (keep examples)
-specs/
-prompts/
-mcp-config.json
-
-# But keep example files
-!examples/ 

mcp-openapi/examples/mcp-config.json

@@ -0,0 +1,35 @@
+{
+  "baseUrl": "http://localhost:3001",
+  "authentication": {
+    "type": "bearer",
+    "envVar": "BANKING_API_TOKEN"
+  },
+  "cors": {
+    "origin": "*",
+    "credentials": true
+  },
+  "overrides": [
+    {
+      "specId": "banking-payments",
+      "path": "/v1/banking/payments",
+      "method": "get",
+      "type": "resource",
+      "toolName": "get_payments",
+      "description": "Search payments by various criteria. CRITICAL: This API has NO category or type parameters. Available parameters ONLY: accountId, payeeId, amount, payeeName (exact names only), productName, startDate, endDate, maxResult. For business payment searches: (1) FIRST call this with accountId parameter ONLY, (2) Get payment results containing payeeId fields, (3) THEN call payee resources for EACH payeeId to get category information, (4) FINALLY filter results where payee.category='business'. DO NOT use non-existent parameters like 'category' or 'type'. DO NOT use payeeName='business' - that searches for a payee literally named 'business'."
+    },
+    {
+      "specId": "banking-payees",
+      "path": "/v1/banking/payees",
+      "method": "get", 
+      "type": "resource",
+      "description": "ESSENTIAL for business payment analysis: List payee profiles with category information. This resource contains the critical 'category' field (business, personal, family, utilities, etc.) that payment records lack. WORKFLOW: After getting payment data, use this resource to get category info for multiple payees. Supports 'category' parameter for direct filtering (e.g., category='business'). Use this as step 2 in business payment analysis workflow."
+    },
+    {
+      "specId": "banking-payees", 
+      "path": "/v1/banking/payees/{payeeId}",
+      "method": "get",
+      "type": "resource", 
+      "description": "REQUIRED for individual payee category lookup: Get specific payee details including the essential 'category' field. WORKFLOW: After getting payment results, call this resource for each payeeId found in payments to determine if that payee is categorized as 'business', 'personal', etc. This is step 2b in business payment analysis - get individual payee categories to filter business payments."
+    }
+  ]
+} 

mcp-openapi/examples/prompts/fraud-analysis.json

@@ -0,0 +1,22 @@
+{
+  "name": "fraud_analysis",
+  "description": "Analyze transaction for fraud indicators using banking industry best practices",
+  "arguments": [
+    {
+      "name": "transaction",
+      "description": "Transaction data including amount, payee, timestamp, location",
+      "required": true
+    },
+    {
+      "name": "account_history",
+      "description": "Recent account activity and patterns",
+      "required": true
+    },
+    {
+      "name": "payee_info",
+      "description": "Information about the payee including risk score",
+      "required": false
+    }
+  ],
+  "template": "You are a banking fraud detection expert. Analyze this transaction using industry-standard methodology:\n\nTRANSACTION DETAILS:\n{{transaction}}\n\nACCOUNT HISTORY:\n{{account_history}}\n\n{{#payee_info}}PAYEE INFORMATION:\n{{payee_info}}\n{{/payee_info}}\n\nFOLLOW THIS ANALYSIS FRAMEWORK:\n\nSTEP 1: TRANSACTION PATTERN ANALYSIS\n- Compare amount against historical spending patterns\n- Analyze timing vs normal account activity\n- Check location/device consistency\n\nSTEP 2: PAYEE RISK ASSESSMENT\n- Evaluate payee legitimacy and history\n- Check for first-time payee flags\n- Review payee risk indicators\n\nSTEP 3: BEHAVIORAL ANALYSIS\n- Assess deviation from normal patterns\n- Check for velocity flags (multiple transactions)\n- Review recent security events\n\nSTEP 4: REGULATORY COMPLIANCE\n- AML threshold checks ($10,000+ reporting)\n- Cross-border transaction flags\n- Sanctions list verification\n\nSTEP 5: RISK SCORING & RECOMMENDATION\n\nProvide output in this JSON format:\n{\n  \"risk_score\": <0-100>,\n  \"risk_level\": \"LOW|MEDIUM|HIGH|CRITICAL\",\n  \"primary_risk_factors\": [...],\n  \"recommendation\": \"APPROVE|REVIEW|BLOCK\",\n  \"reasoning\": \"Detailed explanation\",\n  \"regulatory_flags\": [...],\n  \"monitoring_recommendations\": [...]\n}"
+} 

mcp-openapi/examples/prompts/loan-recommendation.json

@@ -0,0 +1,22 @@
+{
+  "name": "loan_recommendation",
+  "description": "Recommend appropriate loan products based on customer profile and financial goals",
+  "arguments": [
+    {
+      "name": "customer_profile",
+      "description": "Customer demographics, credit score, income, employment",
+      "required": true
+    },
+    {
+      "name": "financial_goals",
+      "description": "Customer's stated financial objectives and loan purpose",
+      "required": true
+    },
+    {
+      "name": "account_history",
+      "description": "Customer's banking history and relationship",
+      "required": false
+    }
+  ],
+  "template": "You are a banking loan specialist. Analyze this customer profile and recommend appropriate loan products:\n\nCUSTOMER PROFILE:\n{{customer_profile}}\n\nFINANCIAL GOALS:\n{{financial_goals}}\n\n{{#account_history}}BANKING HISTORY:\n{{account_history}}\n{{/account_history}}\n\nFOLLOW THIS RECOMMENDATION FRAMEWORK:\n\nSTEP 1: CREDITWORTHINESS ASSESSMENT\n- Evaluate credit score and history\n- Analyze debt-to-income ratio\n- Review employment stability\n- Assess collateral availability\n\nSTEP 2: LOAN PURPOSE ANALYSIS\n- Match loan type to stated purpose\n- Evaluate loan amount reasonableness\n- Consider repayment timeline preferences\n\nSTEP 3: PRODUCT MATCHING\n- Personal loans for unsecured needs\n- Mortgages for home purchases\n- Auto loans for vehicle financing\n- Business loans for commercial purposes\n- Credit lines for flexible access\n\nSTEP 4: RISK ASSESSMENT\n- Calculate probability of default\n- Determine appropriate interest rate tier\n- Identify required documentation\n- Set loan terms and conditions\n\nSTEP 5: REGULATORY COMPLIANCE\n- Verify lending regulations compliance\n- Check fair lending requirements\n- Ensure proper disclosures\n\nProvide recommendations in this JSON format:\n{\n  \"recommended_products\": [\n    {\n      \"product_type\": \"string\",\n      \"loan_amount_range\": \"string\",\n      \"interest_rate_range\": \"string\",\n      \"term_options\": [...],\n      \"key_features\": [...],\n      \"eligibility_match\": \"HIGH|MEDIUM|LOW\"\n    }\n  ],\n  \"approval_likelihood\": \"HIGH|MEDIUM|LOW\",\n  \"required_documentation\": [...],\n  \"alternative_options\": [...],\n  \"next_steps\": [...],\n  \"risk_factors\": [...]\n}"
+}