Troubleshoot a social media MCP problem by identifying the stage that failed: connection, sign-in, search discovery, price quote, execution or result reading. “The assistant cannot search” is too broad to diagnose. A working connection can still face an unavailable source, and a successful sign-in does not prove a search was run.
Begin by recording the client, the server address you used, the time and the plain-language error. Do not paste access tokens, OAuth codes, passwords or private configuration into a support message. A short description of the failing step is usually more useful than a screenshot that exposes credentials.
1. Check the connection instructions
Use the current Superlurk integration instructions for your client. A remote server address, a Claude Code plugin and a local stdio server are different setup methods. Copying a configuration intended for another kind of transport can fail before any search tool is discovered.
For Claude Code, its official MCP reference explains connection management and authentication. Start with the setup method documented by Superlurk, then use the client's status view to establish whether the server is connected. Do not repeatedly add duplicate connections as a first response to an error.
2. Separate sign-in from source access
Complete the browser sign-in and consent for the intended Superlurk account. If the connection was revoked or its authentication needs renewal, use the client's normal reconnect or authentication flow. Do not disable authentication or copy another person's token to make a test pass.
Signing in to Superlurk does not sign the integration in to your personal TikTok, Instagram or Reddit account. A public-data search can still be unavailable because of a provider or network restriction. Likewise, a client that cannot complete OAuth is not evidence that the underlying social network is down.
3. Find the search before inventing its inputs
Ask the assistant to discover the relevant search and read the required fields. In Superlurk, find_searches returns the catalog information needed to build a request. A video link, an account handle and a raw comment identifier are not interchangeable. Follow-up data from a saved result can provide the correct inputs for supported next searches.
If you cannot find the action, check the network page and current catalog. An endpoint appearing in a provider's documentation does not mean it is a customer action in Superlurk. Some actions are excluded or require a specific type of input.
4. Read the quote before retrying execution
- Missing or invalid input: correct the named field instead of asking the assistant to guess an identifier.
- Unsupported query feature: review the issue and any offered adjustment, then obtain a fresh quote.
- Insufficient credits: review your balance and the task size. Purchases happen on the website, not inside a research tool call.
- Connection cap: check the optional daily allowance for that connection. A new chat is not a reason to bypass the cap.
- Expired or changed quote: request the current price again; do not assume an old quote authorizes a different search.
A new quote is not the same thing as a new search. Superlurk's run_search uses the approved quote. If you are uncertain whether execution already started, inspect the run rather than repeatedly making new quotes and approving them.
5. Distinguish working, empty and failed
A run may still be working when the assistant's initial response returns. Use the run status to find out what happened. For bulk lookup, inspect each item: one failure does not mean all items failed, and a partly completed group does not mean the successful items were free.
An empty result means the returned sample has no matching items under that request. A provider failure is different. Neither establishes that nobody discussed a subject. If you try another search, explain the change in source, query or coverage instead of silently treating the result as equivalent.
6. Check saved-result and pagination boundaries
If the assistant has a result identifier, reopen your own result to read it without automatically spending again. For a bulk run, ask it to inspect all the relevant result pages rather than assuming the first page contains every item. Additional source retrieval is different from opening another page of an already saved result.
Expired or deleted results may no longer be available. Keep the research method and source URLs in your brief so a missing saved result does not erase the explanation of what the earlier conclusion was based on.
A useful support note
- Describe the stage. For example: sign-in completed, the catalog appeared, but get_price reported an input issue.
- Include the action and input type. Give the public search name and whether you used a handle, link or keyword. Redact anything that should not be shared.
- Record the time and status. Include the displayed error code, approximate time and whether a run identifier was returned.
- Say what you expected. Explain the research task and the specific behavior you expected. Avoid sending secrets or an entire unreviewed conversation.
For normal task planning, return to the MCP research guide. For credit and cap questions, use MCP costs and limits. Good troubleshooting keeps setup, pricing and evidence quality as separate questions.
Frequently asked questions
Should I keep rerunning a search when a response is slow?
First inspect the existing run status. Creating and approving new quotes can start separate retrieval work rather than answer what happened to the original run.
Does successful sign-in mean every source will work?
No. Authentication to Superlurk and access to a particular provider-backed search are separate stages. Check the action and returned status.
What should I send support?
The client, failing step, public search name, time and displayed error code are useful. Do not send passwords, OAuth codes, tokens or private configuration.
Sources
How this guide was written. Written for Superlurk's public-data search application on 8 November 2026, using its current catalog, MCP contract and the primary references below. Prompts, budgets and sample tables are illustrative; they are not measured customer outcomes. Search availability and quoted prices can change.