Ekbasis runs on your own machine — the client starts it, so there is no endpoint to ping. 840 installs a week from pypi. Last commit 16 Oct 2026.
Foresee what git commands and multi-step changes will do, as calibrated probabilities
We read the source, 7 d ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
"if the previous one succeeded and `||` only if it failed; so when `cd DIR` fails, `cd DIR; rm -rf *` "
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.
subprocess.run([CHROME, "--headless=new", "--disable-gpu", "--hide-scrollbars", "--force-device-scale-factor=2", "--window-size=1600,900",
fig.savefig(os.path.join(OUT, name), facecolor=BG)
n_in = n_drop = n_dup = 0
for p in sorted(glob.glob(f"{FX}/data/raw/*.jsonl.gz") + glob.glob("/dev/shm/fx/raw2/*.jsonl.gz")):
ns = {"__name__": "helpers"}
exec(compile(src[:src.index("report = {}")], "release_eval.py", "exec"), ns) # post, answer, boot (no evaluation run)
puzzles = pickle.load(open(f"{d}/puzzles.pkl", "rb"))
p = subprocess.run(["git", *args], cwd=repo, env=dict(os.environ, **ENV), stdout=subprocess.PIPE,
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Ekbasis and you get told the day something new turns up.
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 ekbasis -- uvx ekbasis
{
"mcpServers": {
"ekbasis": {
"command": "uvx",
"args": [
"ekbasis"
]
}
}
}
[mcp_servers.ekbasis]
command = "uvx"
args = ["ekbasis"]
{
"mcpServers": {
"ekbasis": {
"command": "uvx",
"args": [
"ekbasis"
]
}
}
}
{
"servers": {
"ekbasis": {
"type": "stdio",
"command": "uvx",
"args": [
"ekbasis"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
EKBASIS_URL (Ekbasis server: the hosted API, or your own server (open weights)), EKBASIS_API_KEY (Key for the hosted API (ekb_..., from https://openinterp.org/console); not needed for your own server).
Calibrated decisions for agents: choice, yes/no and score questions answered with probabilities.
Calibrated probability ranges for forecasting questions, with the assumptions behind them.
Calibrated probabilities for Kalshi markets, a news wire and Polymarket outliers (Pro).
MCP server for Jev (TypeSafe System One): typed decisions with calibrated probabilities.
MCP server over TypeSafe Jev: typed ask, rank and check judgments return calibrated probabilities.
Commit-pace and release probabilities for open-source repositories. Docs: anteproof.com/docs
Calibrated advice for coding agents: typed questions in, probabilities out. Apple Silicon.
Compare STEP CAD files locally: identical, moved, or different, and what changed.
Answers built from our own checks of this server.