RateSpot MCP Server

# RateSpot MCP Timeout Fix Update ## Issue Resolved Fixed timeout issues where requests were failing after 15 seconds despite the TypeScript source having a 30-second timeout. ## Changes Made ### 1. Main Server Update - **File**: `ratespot_mcp_server.ts` - **Status**: Already had correct 30-second timeout - **Action**: Recompiled TypeScript to ensure JavaScript is up to date ### 2. DXT Extension Update - **File**: `dxt-extension/server/ratespot_mcp_server.js` - **Issue**: Had hardcoded 15-second timeout - **Fix**: Updated from `timeoutMs = 15000` to `timeoutMs = 30000` - **Action**: Rebuilt DXT package with updated timeout ## Results - Main server (`ratespot_mcp_server.js`): ✅ 30-second timeout - DXT extension: ✅ 30-second timeout - New DXT package: ✅ `ratespot-mcp-1.0.0.dxt` (5.8MB) ## Next Steps 1. **For Claude Desktop users**: Restart Claude Desktop to load the updated server 2. **For DXT installation users**: Use the new `ratespot-mcp-1.0.0.dxt` package ## Why This Happened The RateSpot API sometimes takes 15-25 seconds to respond, especially for certain ZIP codes like those in Oregon. The 15-second timeout was too short, causing requests to fail even though the API was working correctly. ## Verification The successful request we saw earlier took 18.14 seconds and returned 726 mortgage products. With the 30-second timeout, these requests should now complete successfully.