Connection issues
| Problem | What to check |
|---|---|
| The client rejects the server URL | Use https://mcp.storeinspect.com/mcp exactly. |
| The client asks for a transport | Choose HTTP, Streamable HTTP, or remote MCP server. |
| OAuth does not start | Confirm the client supports OAuth for remote MCP servers. |
| The browser opens but sign-in fails | Sign in with the StoreInspect account that has API access. |
| The client shows no StoreInspect tools | Disconnect and reconnect the MCP server, then approve the requested scopes. |
Permission and plan issues
StoreInspect checks account access when tools are called.| Error type | What it usually means |
|---|---|
| No API access | The StoreInspect account is not on a plan with API access. |
| Missing scope | The client did not request or receive the scope required by the tool. |
| Revoked client | The OAuth connection was revoked in StoreInspect MCP settings. |
| Expired or invalid token | Reconnect the MCP client and complete OAuth again. |
Quota and credit issues
Ask the client:- Request quota
- Search-row quota
- Remaining shared contact credits
- Current plan and API access
Contact reveal refused
Thereveal_contacts tool requires explicit credit-spend confirmation.
This fails:
Cursor and VS Code JSON issues
For Cursor-style configuration, use:Still blocked
Include the StoreInspectrequest_id when contacting support. MCP tool responses include a request_id when StoreInspect receives the request.