Claude Desktop Stelar Signals factcheck

How to: Claude Desktop Stelar Signals factcheck

client:Claude Desktop transport:streamable-http tool:factcheck

Add Stelar Signals to Claude Desktop

01
Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "stelar-signals-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.stelardigital.com/mcp"
      ]
    }
  }
}

02
Save the file and restart Claude Desktop.
03
Ask for something factcheck does. Claude Desktop lists the server's tools on connect and calls factcheck itself — you do not invoke it by name.
04
If nothing happens, check the server is running and that Stelar Signals's identifier in your config matches the one above exactly.

Claude Desktop has no remote transport in its config file, so this bridges through mcp-remote. Restart the app after saving. Claude Desktop docs

Set these first

Stelar Signals will not start until these are set, so factcheck never becomes available.

RAPIDAPI_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.

Stelar Signals MCP server