geo-score MCP Server

What the code does

We read the source, 19 h ago · rules ccca72095570

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

    r = subprocess.run([sys.executable, "benchmark/build_page.py"],

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 geo-score -- uvx geo-score

{
  "mcpServers": {
    "geo-score": {
      "args": [
        "geo-score"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.geo-score]
command = "uvx"
args = ["geo-score"]

{
  "mcpServers": {
    "geo-score": {
      "args": [
        "geo-score"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "geo-score": {
      "args": [
        "geo-score"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: OPENAI_API_KEY (Optional. OpenAI key; enables ask and run on that engine.), PERPLEXITY_API_KEY (Optional. Perplexity key; enables ask and run on that engine.), GEMINI_API_KEY (Optional. Gemini (Google AI Studio) key; enables ask and run on that engine.), ANTHROPIC_API_KEY (Optional. Anthropic key; enables ask and run on that engine.), OPENROUTER_API_KEY (Optional. OpenRouter key; enables ask and run on that engine.), GEO_SCORE_WATCH_CONFIG (Optional. Path to geo-score-watch.json for run, list_runs, report and diff.). The author declared them in the registry entry; get the values from the project itself.