VERAX

Name: VERAX
Author: verax-ai

제작자: verax-ai버전 0.8.2i★ –i내 컴퓨터에서 실행

레지스트리 이름io.github.verax-ai/verax

설치

개요

제작자가 쓴 설명(영어 원문)

The body an agent asks before it acts: decide, approve, and keep a signed record on your machine.

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

사용자 의견i아직 리뷰가 없어요리뷰는 다음 단계에서 계정 기능과 함께 열려요
우리의 기본 점검i1개 중 1개 통과공개된 정보로 점검했으며, 코드는 아직 스캔하지 않았어요
사용 정도i아직 측정 안 함★ –

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

연결 방식: 내 컴퓨터에서 실행
전송 방식: Streamable HTTP
카테고리: 기타
입력해야 할 값: VERAX_ISSUER, VERAX_JWKS_URL, VERAX_AUDIENCE, VERAX_STATE_DIR, VERAX_POLICY_FILE

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

기본 점검: 1개 중 1개 통과
내 컴퓨터에서 내 사용자 계정의 권한(파일, 네트워크, 앱)으로 실행돼요.
직접 입력할 값: VERAX_ISSUER, VERAX_JWKS_URL, VERAX_AUDIENCE, VERAX_STATE_DIR, VERAX_POLICY_FILE, VERAX_BIND, VERAX_INVENTORY_FILE

필요한 것

npmNode.js 설치(npx 명령어용)

어떤 앱을 쓰세요?

ClaudeClaude CodeCursorVS CodeChatGPT

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요

{
  "mcpServers": {
    "verax": {
      "command": "npx",
      "args": [
        "-y",
        "@verax-ai/body"
      ],
      "env": {
        "VERAX_ISSUER": "your-value",
        "VERAX_JWKS_URL": "your-value",
        "VERAX_AUDIENCE": "your-value",
        "VERAX_STATE_DIR": "your-value",
        "VERAX_POLICY_FILE": "your-value",
        "VERAX_BIND": "your-value",
        "VERAX_INVENTORY_FILE": "your-value"
      }
    }
  }
}

터미널에서 이 명령어를 실행하세요

claude mcp add verax --env VERAX_ISSUER=your-value --env VERAX_JWKS_URL=your-value --env VERAX_AUDIENCE=your-value --env VERAX_STATE_DIR=your-value --env VERAX_POLICY_FILE=your-value --env VERAX_BIND=your-value --env VERAX_INVENTORY_FILE=your-value -- npx -y @verax-ai/body

실행하기 전에 빈 값을 채워 주세요.

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

{
  "mcpServers": {
    "verax": {
      "command": "npx",
      "args": [
        "-y",
        "@verax-ai/body"
      ],
      "env": {
        "VERAX_ISSUER": "your-value",
        "VERAX_JWKS_URL": "your-value",
        "VERAX_AUDIENCE": "your-value",
        "VERAX_STATE_DIR": "your-value",
        "VERAX_POLICY_FILE": "your-value",
        "VERAX_BIND": "your-value",
        "VERAX_INVENTORY_FILE": "your-value"
      }
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

{
  "servers": {
    "verax": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@verax-ai/body"
      ],
      "env": {
        "VERAX_ISSUER": "your-value",
        "VERAX_JWKS_URL": "your-value",
        "VERAX_AUDIENCE": "your-value",
        "VERAX_STATE_DIR": "your-value",
        "VERAX_POLICY_FILE": "your-value",
        "VERAX_BIND": "your-value",
        "VERAX_INVENTORY_FILE": "your-value"
      }
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

VERAX_ISSUER 필수 env
Issuer the agent's token must carry. The body refuses to start without one; `verax doctor` names what is missing.
VERAX_JWKS_URL 필수 env
Where the body fetches the keys that verify that token.
VERAX_AUDIENCE 필수 env
Audience the token must name, so a token minted for something else is refused.
VERAX_STATE_DIR 필수 env
Directory the ledger, keys and approvals live in. It stays on this machine.
VERAX_POLICY_FILE 필수 env
Policy the gate applies. @verax-ai/proxy ships policy/default.json, which denies what it does not name.
VERAX_BIND env
host:port the body listens on. Anything but loopback needs VERAX_TLS_TERMINATED=1.
VERAX_INVENTORY_FILE env
Roster document the body serves; the format is @verax-ai/inventory.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검

✓ 통과
제작자와 저장소 일치
레지스트리 이름이 GitHub 계정 verax-ai 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
… 아직 점검 안 함
계속 관리되고 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
… 아직 점검 안 함
라이선스 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
– 해당 없음
엔드포인트 응답
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
– 해당 없음
OAuth로 로그인
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
… 아직 점검 안 함
도구 설명에 숨겨진 지시 없음
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요

기타 카테고리의 다른 서버와 비교i

이 카테고리의 다른 서버 18336개 중 0%보다 스타가 많아요
이 카테고리의 다른 서버 18336개 중 93%보다 최근에 레지스트리에 공개됐어요
기본 점검 결과가 이 카테고리의 다른 서버 18336개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

VERAX, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

입력해야 할 값: VERAX_ISSUER, VERAX_JWKS_URL, VERAX_AUDIENCE, VERAX_STATE_DIR, VERAX_POLICY_FILE

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.8.2)은 3일 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, NexusWindows

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Spec Driven Development

제작자: formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

내 컴퓨터에서 실행★ 440MIT14개월 전 업데이트

설치

Remote Desktop Commander

제작자: desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

클라우드에서 실행★ 211그저께 업데이트

설치

NexusWindows

제작자: pironjulien

Windows computer use in the background: desktop apps driven without your mouse or keyboard.

내 컴퓨터에서 실행오늘 업데이트

설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

Verax

The body an agent asks before it acts.

Listed on: npm · Glama · MCP Registry · MCP Market · mcp.so · Docker Hub · Zenodo

Verax is an MCP server that sits between an agent and its tools. Every tool call passes a policy gate and leaves a signed decision record before anything runs; every call that ran leaves an effect row that is reconciled against its record afterwards. A refusal is recorded the same way as an approval. A call the policy will not decide alone is held until an operator approves it, at this machine or, with the operator door set up, from another device with a passkey. The ledger stays on the machine the body runs on, and the body opens only when its authorization is configured: there is no default token.

Break it, and we pay. USD 100 for each valid report of a way for the agent's account to get a refused call allowed, run a call with no decision record, or change the service's code, keys or ledger. The budget is USD 500 in total. Terms: SECURITY.md.

By VERAX Teknoloji. Sister projects: Conarium · Tugra · Cedulon. Decision records use the Cedulon record format.

How Verax compares, dated 15 October 2026: of 40 projects that gate, log or approve an agent's tool calls, nine are compared on four questions with a source for every cell, and the page says where Verax falls short: verax-ai.com/compare.html.

See it run

npx @verax-ai/body demo

The recording is the output of one run in a terminal where the approval question was answered y and the amount was typed. That run took about a second; it is played back slowly here so it can be read.

What it prints, without a terminal to answer the approval question:

verax demo

memory.put / memory.get allowed; two signed records

message.send -> ops@blocked.test refused egress-blocked (signed) ref 6c6e4925-b769-4a8b-8fc4-e2443613a5b6

spend 100 minor USD sample-merchant held no terminal to ask, so it stays held (run this in a terminal to be asked)

audit.explain of the refuse finding none trust-root own-key chain and signatures read back

records 5 effects 3 ledger removed on exit (run with --keep to keep it and check it with verax verify)

Not shown here: data masking arrives with a downstream server such as Conarium; statement reconciliation needs a real statement (verax reconcile).

Node 22.6 or newer, @verax-ai/body 0.2.1 or later. The command records an allowed memory write and read, a signed refuse of a message to a host off the policy list, and a payment held for the operator on this machine (approved when the terminal answers y and then types the amount, 100; up to 0.5.0 the demo did not print that second question).

--keep leaves the temporary ledger on disk. verax verify reads it back without a body, as in Read the ledger back without us. To keep it and check it:

npx @verax-ai/body demo --keep

npx -y -p @verax-ai/body verax verify

The same rules, animated

Four short episodes show the same gate, with characters in place of a terminal. They are sample scenarios: the scenes are drawn in three.js and the voices are generated with ElevenLabs.

Episode 1, "$1,850": a payment is held until a person approves it on a phone, and changing one cent in the record breaks its signature.

https://github.com/user-attachments/assets/772ae1c4-2697-47a0-a228-36f0508b0d93

Episode 2, "No rule, no way through": a call with no rule is refused, the same call under a new name is refused again, and both refusals are signed.

https://github.com/user-attachments/assets/4fb86627-3310-4f10-b1a9-059d8fcffb28

Episode 3, "The red lever": an operator halts the body, every later call is refused and signed, and a call that was already running is not cut off.

https://github.com/user-attachments/assets/8d19eed9-3359-46b3-bd77-f2b1b1c4dd75

Episode 4, "Who approved?": a held spend waits for verax approve on the machine, the agent cannot approve it, and the approver's operator id goes into the record.

https://github.com/user-attachments/assets/0b8aade4-a970-4b63-835e-4837e2a39cc9

Connect your agent

Elevated verax install and verax approve run a copy of this program that only an administrator can change; a copy your account can change is refused. On Windows a passkey through the operator door (verax install --operator-door ) approves without an elevated shell; without the door, an elevated CLI approve is the way. It has to be run from a separate administrator account, not this account elevated, because a same-user elevated shell inherits that user's environment variables and PowerShell profile, which the agent can set. Clear NODE_OPTIONS in that shell (Remove-Item Env:NODE_OPTIONS). Start that other account's PowerShell with -NoProfile (an elevated shell otherwise runs your $PROFILE, which your account can change):

npm install -g --prefix "$env:ProgramFiles\verax-cli" @verax-ai/body

& "$env:ProgramFiles\verax-cli\verax.cmd" install

On Linux and macOS, with a root-owned Node (the distribution's /usr/bin/node, or /opt/verax-node/ /bin/node; the installer prints those steps when the Node it was started from can be changed by your account). Do not start an elevated command with env node:

sudo npm install -g --prefix /opt/verax-cli @verax-ai/body

sudo /usr/bin/node /opt/verax-cli/lib/node_modules/@verax-ai/body/dist/cli.js install

The command installs @verax-ai/body from the npm registry into an administrator-owned directory after signature checks, runs that Node, and keeps the ledger under a service account. On Windows the agent token is %ProgramData%\Verax\agent-token\ \agent.token (Administrators and SYSTEM have full control, your SID can read the file and read-execute the directory). On Linux and macOS a child process running as your uid writes ~/.verax/agent.token from its stdin. It prints the Claude Code line that reads that file. Port 8787 taken? verax install --port 8797. Node must be the all-users installer from nodejs.org on Windows; a Node your account can rewrite is refused. On macOS the remedy extracts the official tarball as root into /opt/verax-node (root:wheel, not group- or other-writable). On Linux the same place, /opt/verax-node (root:root), which SELinux labels usr_t. On SELinux systems install requires Node labelled bin_t or usr_t (distribution Node is; a tarball under /usr/local/lib is not) and prints the one-line fix. The service then runs in unconfined_service_t. The service account and the file permissions are the boundary.

Approve a held call with verax approve, or, when the install named an origin with --operator-door, from another device through the operator door with a passkey enrolled by a pairing code from verax operator enroll. The passkey panel (verax desktop) is not released yet. On Windows run the approve from a separate administrator account, not this account elevated, in a -NoProfile PowerShell after Remove-Item Env:NODE_OPTIONS: & "$env:ProgramFiles\verax-cli\verax.cmd" approve. Linux and macOS, naming the root-owned Node: sudo /usr/bin/node /opt/verax-cli/lib/node_modules/@verax-ai/body/dist/cli.js approve or sudo /opt/verax-node/ /bin/node /opt/verax-cli/lib/node_modules/@verax-ai/body/dist/cli.js approve. Uninstall the same way, with uninstall in place of approve.

To try it in your own user, which is not a boundary:

verax init --local ~/.verax

verax serve --env-file ~/.verax/verax.env

claude mcp add --transport http verax http://127.0.0.1:8787/mcp --header "Authorization: Bearer $(cat ~/.verax/local-issuer/agent.token)"

The token can read and write memory through the gate; it cannot approve. The shipped policy refuses spend until you add a rule for it; a call your policy holds waits for verax approve on this machine, or for an approval through the operator door when one is set up. See docs/THREAT_MODEL.md.

With Conarium

@verax-ai/body 0.2.2 and later accepts --with-conarium. 0.2.1 does not carry the flag. The flag has npx download @conarium-ai/core from npm and run it as a child process; that needs a network.

Conarium masks the rows, and its sample policy denies its public.secrets table. Verax puts each call through the same gate as its own tools, keeps a signed record and a hash of the answer, and refuses a downstream tool the policy does not name before the child sees the call. When Conarium answers with an error, the body tells the caller that it did, not what it said.

What it prints, without a terminal to answer the approval question:

verax demo

memory.put / memory.get allowed; two signed records

message.send -> ops@blocked.test refused egress-blocked (signed) ref 6c6e4925-b769-4a8b-8fc4-e2443613a5b6

spend 100 minor USD sample-merchant held no terminal to ask, so it stays held (run this in a terminal to be asked)

conarium.query customers allowed; masked by Conarium before the rows left it measured [MASKED_PII] on every email and card

conarium.query public.secrets allowed by this gate; Conarium answered with an error and no rows recorded as a failed call

conarium.list_tables refused no-rule (signed) refused by this gate; the downstream server never saw the call

audit.explain of the refuse finding none trust-root own-key chain and signatures read back

records 8 effects 5 ledger removed on exit (run with --keep to keep it and check it with verax verify)

Not shown here: a real database (these are Conarium's sample rows); statement reconciliation needs a real statement (verax reconcile).

What ships

Package	What it is
`@verax-ai/body`	The MCP server and the `verax` command: serve, `install`, `uninstall`, `init`, `doctor`, `approve`, `operator`, `downstream`, `reconcile`, `witness`, `halt`, `resume`, `unlock` (`desktop` is not released yet).
`@verax-ai/proxy`	The decision proxy the body is built on: policy, signed records, ledger, `explain`, reconcile.
`@verax-ai/inventory`	The roster document a body serves and the panel lists, with its strict parser.

The three packages are published together and carry the same version; the capability matrix in docs/STATUS.md names the current one, and it is the version on npm. The body is also listed in the MCP registry as io.github.verax-ai/verax. What that version carries, what it does not, and the test holding each row up are in the capability matrix at the top of docs/STATUS.md.

Read the ledger back without us

A ledger only the vendor's running service can read is evidence a buyer rents, not evidence they hold. verax verify reads a state directory on its own — no body listening, nothing on the network — and states each check on its own line, because they fail separately. On a copy of the ledger `npx @verax-ai

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

VERAX

개요

PopNx MCP의 세 기둥

할 수 있는 일

설치

설치하기 전에

직접 입력할 값

할 수 있는 일

기본 점검i

제작자와 저장소 일치

계속 관리되고 있음

라이선스 있음

엔드포인트 응답

OAuth로 로그인

도구 설명에 숨겨진 지시 없음

기타 카테고리의 다른 서버와 비교i

자주 묻는 질문

대안

Spec Driven Development

Remote Desktop Commander

NexusWindows

제작자의 README

Verax

See it run

The same rules, animated

Connect your agent

With Conarium

What ships

Read the ledger back without us