Troubleshooting
Common errors, how to verify your connection, and how to get help.
Verify Your Connection Is Working
The quickest way to verify everything is working is to ask Claude a simple question that triggers an Investra tool:
What is the current mortgage interest rate?
This calls the get_interest_rate tool, which requires no parameters. If you get a rate back (e.g. "The
current 30-year fixed rate is 6.78%"), your connection and authentication are both working.
If it fails, work through the sections below to diagnose the issue.
How to Check Which Tools Are Available
Depending on your client:
- Claude Code: Run
/mcpin a session. Investra should appear with a green checkmark and "17 tools". - Claude Desktop: Click the hammer/tools icon in the message input area. You should see 15 Investra tools listed.
- claude.ai: In a new conversation, look for the integrations icon near the message input. Investra should be listed. You can also ask Claude: "What Investra tools do you have access to?"
If tools are missing or the count is less than 15, try removing and re-adding the Investra connection. This forces a fresh tool discovery.
Common Errors
| Error | Cause | Solution |
|---|---|---|
401 Unauthorized |
Invalid, expired, or missing API key | Re-authenticate with a valid key from Profile > Developer. Make sure the key starts with inv_. |
403 Forbidden |
Your plan does not include this tool | Off-market search and skip trace require paid plans. Check your plan at investraapp.com/pricing. |
429 Too Many Requests |
Rate limit or daily quota exceeded | Wait for the Retry-After period, or upgrade your plan for higher limits. |
500 Internal Server Error |
Server-side issue | Try again in a few minutes. If it persists, check status.investraapp.com or contact support. |
| Connection refused / timeout | Network issue or incorrect URL | Verify you can reach https://www.investraapp.com in your browser. Check that the MCP URL is exactly https://www.investraapp.com/api/mcp. |
| Tools not showing up | Connection succeeded but tools not discovered | Remove and re-add the Investra server. For Claude Desktop, fully quit and relaunch after config changes. |
| "No results found" | Query returned zero matches | This is not an error — your search criteria may be too narrow. Try broadening the location, price range, or removing filters. |
Network and Firewall Issues
If you are on a corporate or restricted network:
- Ensure outbound HTTPS (port 443) is allowed to
investraapp.com. - If your network uses a proxy, configure your MCP client or system to use it. Claude Code respects the
HTTPS_PROXYenvironment variable. - Some VPNs can interfere with WebSocket or SSE connections. Try disconnecting your VPN temporarily to test.
Quick connectivity test:
Open your browser and navigate to:
https://www.investraapp.com/api/mcp
You should see a response (even if it is an error page or JSON). If the page does not load at all, the issue is network connectivity, not Investra configuration.
Full Reset (Start Fresh)
If nothing else works, try a complete reset:
- Revoke your API key at Profile > Developer and generate a new one.
- Remove the Investra MCP server from your client:
- Claude Code:
claude mcp remove investra - Claude Desktop: Remove the
investraentry from your config file and restart. - claude.ai: Go to Customize > Connectors and remove Investra.
- Claude Code:
- Re-add the server following the setup guide for your client.
- Authenticate with your new API key.
- Test with a simple prompt: "What is the current mortgage interest rate?"
Contact Support
If you are still having trouble after trying the steps above, reach out to us:
- Email: support@investraapp.com
- Discord: Join the Investra community and ask in the
#mcp-supportchannel.
When contacting support, please include:
- Which client you are using (Claude Code, Claude Desktop, or claude.ai).
- The exact error message or behavior you are seeing.
- Your operating system (macOS, Windows, Linux).
- Whether you are on a free, Pro, or Pro Plus plan.
Never share your full API key in support requests, Discord, or any public forum. If we need to look up your account, we will ask for the last 4 characters of your key (e.g. "...7f3a") or your account email.