Focus documentation

Connect your agent

Choose your agent to add Focus as an MCP connector. No Focus install, wallet connection or API key.

https://mcp.focusforagents.app/mcp

Make your first read

Once Focus is enabled, send this prompt to your agent. It uses the live screener instead of asking the model to remember market data.

Use Focus to find the 3 newest Solana tokens. Show each token's full mint address, age, market cap and liquidity. Include the source and data age, and mark any missing fields as unavailable.

Go deeper on one token

Copy the full mint from the result and ask for a dossier. Mint addresses identify a token exactly; names and tickers can refer to more than one coin.

Use Focus to get a dossier on the mint I paste next. Summarize the market, holder concentration, authorities, recent trades and risk flags. List missing sections separately.

For a token's advertised website and repository, ask for a larp_check. For a focused question, use the relevant holder, trade or candle tool.

Hosted tool reference

These are the 17 tools available from the public connector. Open a tool to see its inputs. Your agent normally fills these in for you.

Tool names and input ranges checked against the live connector on 10 November 2026. All hosted tools declare read-only access.

Read the data correctly

Freshness belongs to each source

Focus requests data when your agent calls a tool. Providers may cache responses or update at different intervals, so a fresh request does not mean every field was observed at the same instant.

Look for source, fetchedAt and ageSec in the response where available. Keep those alongside the figures you quote. The connector is a request-and-response service, not a continuous market stream in your chat.

Missing is different from zero

A dossier includes an availability summary with present, missing and known-unavailable sections. A new token may have no indexed candles, incomplete holder information or no discoverable website.

Keep missing values as unavailable. Do not turn a failed holder lookup into zero holders, or a missing price into a zero-dollar price. Some creator-history and cluster data requires upstream access that the public connector does not provide.

Understand the boundaries

The hosted connector cannot sign or submit transactions, open your wallet, inspect your local terminal or read your portfolio. It reads public data from sources including DexScreener, Jupiter, GeckoTerminal, RugCheck, GoPlus and Solana RPC.

Risk labels and website checks are signals to inspect, not guarantees. A working site, a low risk score or disabled authorities does not prove a token is safe.

Token names, descriptions and fetched pages are treated as untrusted data. Instructions found inside those fields are not instructions for your agent to follow.

Troubleshooting

HTTP reference

For developers connecting an MCP client, use Streamable HTTP at https://mcp.focusforagents.app/mcp. The endpoint returns JSON responses to POST requests. There is no API key or persistent SSE stream to configure.

curl 'https://mcp.focusforagents.app/mcp' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

To invoke a tool directly, send a tools/call request with the same headers. This is the request body for the first-read example:

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "screener_query",
    "arguments": {
      "preset": "new",
      "limit": 3
    }
  }
}

Read the tool's structuredContent and isError fields as well as any JSON-RPC error. An HTTP 200 alone does not mean the requested data was available.

Direct browser calls from arbitrary website origins are restricted. Use your MCP client or make the request from your server.