Troubleshooting
Common issues and solutions when using Universal Crypto MCP.
🔴 Connection Issues
MCP Server Not Starting
Symptom: Server doesn't start, no response from Claude/ChatGPT
Solutions:
-
Check Node.js version
-
Reinstall dependencies
-
Check for port conflicts (HTTP/SSE mode)
-
Verify config path (Claude Desktop)
"Tool not found" Error
Symptom: Claude says it can't find a tool
Solutions:
- Restart Claude Desktop after config changes
- Check tool name spelling - use exact names from docs
- Verify server is running:
ChatGPT Not Connecting (HTTP Mode)
Symptom: ChatGPT can't reach the MCP server
Solutions:
-
Ensure server is running:
-
Check firewall settings - allow port 3001
-
Verify URL in ChatGPT:
- Correct:
http://localhost:3001/mcp -
Wrong:
http://localhost:3001(missing/mcp) -
Try with explicit host:
🟡 Transaction Errors
"Insufficient Funds"
Symptom: Transaction fails with insufficient balance
Solutions:
-
Check native token balance for gas:
-
Check token balance:
-
Reduce amount to leave room for gas
"Transaction Reverted"
Symptom: Transaction submitted but reverted on-chain
Common Causes:
| Cause | Solution |
|---|---|
| Slippage too low | Increase slippage to 1-3% |
| Token has transfer tax | Account for tax in amount |
| Approval not set | Approve token first |
| Contract paused | Check if protocol is active |
| Price moved | Get fresh quote and retry |
Debug Steps:
-
Simulate first:
-
Check token security:
"Nonce Too Low"
Symptom: Transaction rejected with nonce error
Solutions:
- Wait for pending transactions to confirm
- Cancel pending transaction:
- Speed up transaction:
"Gas Estimation Failed"
Symptom: Can't estimate gas for transaction
Solutions:
- Check if contract allows the operation
- Verify you have required approvals
- Try with explicit gas limit:
🟠 API & Data Issues
"API Key Required"
Symptom: Tool returns API key error
Solutions:
| API | How to Get Key |
|---|---|
| CoinGecko | coingecko.com/api |
| LunarCrush | lunarcrush.com/developers |
| CryptoPanic | cryptopanic.com/developers |
Set in environment:
Or in Claude config:
"Rate Limited"
Symptom: API returns 429 error
Solutions:
- Wait and retry - usually 1 minute
- Use API key for higher limits
- Reduce request frequency
- Use cached data when possible
Stale/Wrong Price Data
Symptom: Prices seem outdated or incorrect
Solutions:
-
Specify the source:
-
Check multiple sources:
-
Use on-chain price:
🔵 Security Issues
"Honeypot Detected"
Symptom: Token flagged as honeypot
What It Means: - Token cannot be sold after buying - Common scam tactic
Action: - ❌ DO NOT BUY this token - Report to community
"High Risk Score"
Symptom: Token has risk score > 7/10
Check These Factors:
| Factor | Why It's Risky |
|---|---|
| Ownership not renounced | Owner can rug |
| Hidden mint function | Unlimited supply |
| Blacklist function | Can block your wallet |
| High holder concentration | Whale dump risk |
| Liquidity not locked | Can pull liquidity |
Action: - Proceed with extreme caution - Never invest more than you can lose
Approval Concerns
Symptom: Worried about token approvals
Check Your Approvals:
Revoke Suspicious Approvals:
🟣 Environment Issues
Private Key Not Working
Symptom: Transactions fail with signing errors
Checklist:
-
Format check - Must start with
0x: -
No quotes in .env:
-
Correct length - 64 hex characters after
0x -
Test with read-only first:
Wrong Network
Symptom: Operations happening on wrong chain
Solutions:
-
Always specify network:
-
Check supported networks:
🔧 Debug Mode
Enable Verbose Logging
Use MCP Inspector
This opens a web UI where you can: - See all available tools - Test tools manually - View request/response logs
📞 Getting Help
Before Asking for Help
- ✅ Check this troubleshooting guide
- ✅ Search existing issues
- ✅ Try with latest version:
How to Report a Bug
Include:
- Environment:
- Node.js version
- OS (macOS/Windows/Linux)
-
Client (Claude/ChatGPT/Cursor)
-
Steps to reproduce
-
Expected vs actual behavior
-
Error messages (full text)
-
Relevant logs (with
LOG_LEVEL=DEBUG)