Skip to main content

​
Smoke Test

A quick checklist to verify everything is working.

​
Prerequisites

Your MCP client is installed and running
You’ve added https://askgina.ai/ai/predictions/mcp as a server
You can open a browser for OAuth sign-in

​
Run These Commands

1

Echo test

Expected: ok
2

List available commands

Expected: help text describing host-tools usage
3

Find a host tool

Expected: JSON output including searchPredictionMarkets tool details
4

Search prediction markets

Expected: JSON output with live market data
All checks pass? You’re fully connected!

​
Common Issues

​
1. Check the Server URL

Make sure your MCP client is using this exact URL:
If the URL is different (even slightly), remove the server and add it again with the correct URL.

​
2. Sign-In Not Working

1

Trigger auth

Your client should trigger OAuth automatically. If not:
  • Claude Code: run /mcp and pick predictions
  • Codex: run codex mcp login predictions
  • Cursor: go to Settings → MCP and check status
2

Complete sign-in

Sign in to Gina in the browser window that opens.
3

Approve access

Click “Approve” when prompted.
4

Retry

Return to your MCP client — bash should now appear as an available tool.

​
3. No Browser Window Opens

Some MCP clients show a sign-in link or “Authorize” button instead of opening a browser automatically.
  • Look in your client UI for an auth link and follow it
  • Try these client-specific commands:
Start claude, then run /mcp and pick predictions.

​
4. Signed In But No Tools

If you signed in but no bash tool appears:
1

Remove the server

Remove predictions from your MCP client.
2

Re-add it

Add the server again with URL https://askgina.ai/ai/predictions/mcp.
3

Re-authenticate

Restart your client and complete the sign-in flow again.

​
5. Commands Fail

First, verify the basics work:
If that succeeds, check what’s available:
If a specific command fails, check that your input JSON is valid. A common issue is missing or mismatched quotes in the JSON argument.

​
6. Connection Timeout

  • Check your internet connection
  • Try a different network (VPN or corporate firewalls can block MCP connections)
  • Ensure the server URL uses https:// (not http://)

​
Still Stuck?

Check the FAQ or reach out on Twitter/X.