Grok 0xinsider get_suspicious_trades
How to: Grok 0xinsider get_suspicious_trades
Add 0xinsider to Grok
-
01
Open .mcp.json (in your project root) and merge this in. Keep any servers already there.
{
"mcpServers": {
"mcp": {
"type": "http",
"url": "https://api.0xinsider.com/api/v1/mcp"
}
}
}-
02
Save the file and restart Grok.
-
03
Ask for something get_suspicious_trades does. Grok lists the server's tools on connect and calls get_suspicious_trades itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that 0xinsider's identifier in your config matches the one above exactly.
Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs
Set these first
0xinsider will not start until these are set, so get_suspicious_trades never becomes available.
-
OXINSIDER_API_KEY
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.