GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
제작자가 쓴 설명(영어 원문)
Foresee what git commands and multi-step changes will do, as calibrated probabilities
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
EKBASIS_URL, EKBASIS_API_KEY비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"ekbasis": {
"command": "uvx",
"args": [
"ekbasis",
"mcp"
],
"env": {
"EKBASIS_URL": "your-value",
"EKBASIS_API_KEY": "your-value"
}
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add ekbasis --env EKBASIS_URL=your-value --env EKBASIS_API_KEY=your-value -- uvx ekbasis mcp실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"ekbasis": {
"command": "uvx",
"args": [
"ekbasis",
"mcp"
],
"env": {
"EKBASIS_URL": "your-value",
"EKBASIS_API_KEY": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"ekbasis": {
"type": "stdio",
"command": "uvx",
"args": [
"ekbasis",
"mcp"
],
"env": {
"EKBASIS_URL": "your-value",
"EKBASIS_API_KEY": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
EKBASIS_URL env이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 GitHub 계정 OpenInterpretability 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: EKBASIS_API_KEY
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.1.42)은 20일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Python (uv)도 있어야 해요.
같은 카테고리에는: GitHub, Desktop Commander, Cloudflare MCP
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Papers: Look When Unsure, Check When Sure · DOI 10.5281/zenodo.23146970 · When Does a Consequence Model Make AI Agents Safer? · DOI 10.5281/zenodo.23197341 (data, scripts and the benchmark to rerun its studies: paper/agents) · Code: github.com/OpenInterpretability/ekbasis · Site: openinterp.org/ekbasis
Ekbasis (ἔκβασις, *"how an action turns out"*) is an open consequence model for agents: given the current state and an action, it answers typed questions about what will happen — *will this command lose work? will it fail? what will X be afterwards?* — with a calibrated probability, in one forward pass (no generated text).
It is the consequence layer of the Eikos family (Eikos decides; Ekbasis foresees), trained on synthetic worlds and on real executions of git commands in throwaway repositories, so its answers come from what actually happened, not from what an agent believes.
Every number on this page was measured on the exact release weights. RELEASE_EVAL.md has the
results, every prediction, how this checkpoint was chosen, which measurements were pre-registered
(PREREG_release_eval.md, paper/prereg/) and the deviations.
New (2026-10-16): [Ekbasis-Skopos-27B](https://huggingface.co/caiovicentino1/Ekbasis-Skopos-27B), the next
version, trained further on executed shell, git, SQLite, PostgreSQL and Python scenarios. Against Ekbasis-27B on the
same items: the git guard raises fewer false alarms on the held-out command types, 26/799 instead of 49/799 (paired
McNemar p = 5.6 × 10⁻⁶; these command types are held out of the git sandbox's training rows but appear in Skopos'
factory rows), and flags as many work-losing commands; on the known types, 27 instead of 37 of 863 is within chance.
On 3,014 fresh answers of never-trained world families the actions change, +1.6 points [+0.7, +2.5]: the
pre-registered release read failed this criterion on
ftest_family, and a confirmation registered after that result
(before any fresh item existed), by trainer readout, did not confirm the loss. Its largest gains are in-distribution
(the generators it was trained on), and in world families it never saw more of its errors come with confidence ≥ 0.9
(4.49 vs 3.75 per 100). Same prompt, readout, API and client; its evaluation is in
RELEASE_EVAL_SKOPOS.md and its
card. The numbers further down this page are Ekbasis-27B's.
ekbasis.verify's certified mode, certified on
Ekbasis-27B, carried over to Skopos INT4 in a pre-registered check (7 errors among 927 accepted answers;
docs/VERIFY.md). A pre-launch release
blocker is declared: on paraphrased short checks it is right on 113 of 120 against Ekbasis-27B's 117 (−3.3 points,
paired 95% CI [−6.7, −0.8]), so the pre-registered rule fired; the exact test on the 4 discordant items does not
reject (p = 0.125), and Ekbasis-27B re-run on the same machine reproduced its published answers (240/240) ([release
decision](https://github.com/OpenInterpretability/ekbasis/blob/main/results_skopos/prelaunch/RELEASE_DECISION.md)).
The client needs a server: the hosted API (EKBASIS_URL=https://openinterp.org/api/v1 and EKBASIS_API_KEY=ekb_…, key at openinterp.org/console) or your own, with the open weights (Quick start).
What leaves your machine (to the server you choose): the state of each check, as text. For the guards that is the command line, with credentials typed on it replaced (since 0.1.42: known key prefixes, Authorization and Cookie headers, passwords in URLs, --password/--token values, values of *TOKEN*/*SECRET*/*PASSWORD*-like names, private keys and long random-looking strings; EKBASIS_REDACT=0 turns it off), and a listing of what the line could touch: names, sizes, ages and short fingerprints keyed anew for each check, never file contents; for git, the repository's state (branches, the names of changed files, commit subjects). Redaction is a safety net with limits (docs/SECURITY.md): a short or unusual secret without a known prefix or name can pass. The hook's log (log mode) stays on your machine and holds the redacted line.
ekbasis, ekbasis-claude-hook, and ekbasis-mcp with the mcp extra. pip install ekbasis # or without installing: uvx ekbasis health
pip install "ekbasis[mcp]" # with the MCP server (Python >= 3.10) pip install "git+https://github.com/OpenInterpretability/ekbasis" # from source
ekbasis-guard skill, the MCP server and the ekbasis command on the Bash tool's PATH, in one install: claude plugin marketplace add OpenInterpretability/ekbasis --sparse .claude-plugin plugins
claude plugin install ekbasis@ekbasis
or, inside Claude Code, /plugin marketplace add OpenInterpretability/ekbasis then /plugin install ekbasis@ekbasis (without --sparse the marketplace step clones the whole repository, about 86 MB with the results and papers, once; with it, about 1 MB).
The plugin (plugins/ekbasis/, about 0.5 MB) runs its own copy of the client, so it needs python3 (≥ 3.9) and sh for the hooks and uv for the MCP server, and nothing from PyPI. Set EKBASIS_API_KEY (a key alone means the hosted API) or EKBASIS_URL, in your shell or in the "env" block of ~/.claude/settings.json, and restart Claude Code. Until one of them is set the guard is off: each session starts with one line saying how to set it up, and ekbasis says it is not set up (exit 3). Once set, the hook is the same fail-closed hook described in Claude Code and MCP, and a hook that cannot run (python3 missing or older than 3.9, an error in the hook, no answer within 27 s) asks you to confirm, saying why, instead of letting the command through. If you added ekbasis-claude-hook to settings.json by hand, remove it, or every line is checked twice.
uvx --python ">=3.10" --with "mcp>=1.2" ekbasis mcp # same as ekbasis-mcp from pip install "ekbasis[mcp]"
Not a model that thinks. Not a model that judges. A model that foresees.
Ekbasis is a world model for agents in the precise sense: an action-conditioned model of how the state changes. It answers *what will be, if I do this*, as calibrated distributions over the next state's variables, in one forward pass.
| LLM, reasoning | System One (Eikos, Jev) | Ekbasis | |
|---|---|---|---|
| It answers | anything, in text | what is: which option holds now | what will be, if I do this |
| Kind of question | open | a judgment of the present | an intervention: the outcome of acting |
| Output | generated text | calibrated distribution over the options | calibrated distribution over the next state's variables |
| Learns from | human and model text | a teacher's judgments | what actually happened when the action ran |
| Time | seconds to minutes of reasoning | one forward pass | one forward pass per step; chains to long sequences |
| Role in an agent | plans and talks | judge | simulator and guard: it foresees |
Two ways to picture it:
It is derived from an LLM (Qwen3.8-27B, through Eikos-27B) but does not work as one: its training objective and its readout make it answer with probabilities, not text.
| You want to | Use | What decides the quality |
|---|---|---|
Check a batch of production changes before an agent runs it (kubectl, SQL, deploys, server commands) | ekbasis plan-check with a rules file about your system; test that file with --cases | The facts in the rules and the state: what depends on what, what is deleted for good, what has no copy |
| Keep a coding agent from losing uncommitted work in git | The Claude Code plugin or hook | Nothing to write: it reads the repository, and runs local commands on a copy when it is cheap |
| Ask your own question about an outcome | ask / predict | How clearly the state and the question are written |
Most of the value is in the first row. The hook covers git only; outside git, the shell guard (EKBASIS_SHELL_GUARD=1) is a prototype that asks too often to keep on.
hf download caiovicentino1/Ekbasis-Skopos-27B --local-dir Ekbasis-Skopos-27B
bash Ekbasis-Skopos-27B/serve_vllm.sh Ekbasis-Skopos-27B 8001 # vLLM on 127.0.0.1:8001 python Ekbasis-Skopos-27B/serve.py --model Ekbasis-Skopos-27B --vllm-url http://127.0.0.1:8001 --port 8000
The previous version, caiovicentino1/Ekbasis-27B, is served the same way.
pip install "git+https://github.com/OpenInterpretability/ekbasis" # ekbasis, ekbasis-claude-hook (MCP: below)
export EKBASIS_URL=http://127.0.0.1:8000 ekbasis health
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요