Stellar Agent Search MCP Server

What the code does

We read the source, 22 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

      detail: `Could not safely update Cursor config: ${(error as Error).message}`,

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add stellar-agent-search -- npx -y stellar-agent-search

{
  "mcpServers": {
    "stellar-agent-search": {
      "args": [
        "-y",
        "stellar-agent-search"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.stellar-agent-search]
command = "npx"
args = ["-y", "stellar-agent-search"]

{
  "mcpServers": {
    "stellar-agent-search": {
      "args": [
        "-y",
        "stellar-agent-search"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "stellar-agent-search": {
      "args": [
        "-y",
        "stellar-agent-search"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: STELLAR_NETWORK (Stellar network to target: mainnet | testnet. testnet also requires EXPLORER_BASE_URL — the default explorer indexes mainnet only, and the server refuses to start on the mismatched pair.), EXPLORER_BASE_URL (Override the stellar-8004 explorer API base URL.), STELLAR_RPC_URL (Override the Soroban RPC URL used for the bounded Reputation-contract probe.), VERIFY_ONCHAIN (Set to 'false' to skip the bounded contract probe; reputation fields remain Explorer-declared either way.). The author declared them in the registry entry; get the values from the project itself.