Omega Mcp

io.github.aien-devPublished by GitHub account aien-devv0.1.0Updated Oct 29, 2026

Compile and run Omega (.om) programs in a sandbox, and look up Omega errors and keywords.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Lets an assistant compile and run Omega (.om) programs in a sandboxed local process, and look up Omega errors, traps and keywords.

What you can do
  • Compile Omega source and get a binary size and hash, or a structured compile error with line, code, meaning and fix
  • Run Omega programs with stdin and a timeout, returning capped output and the exit status, trap or resource limit that stopped it
  • Explain Omega error codes, compiler error lines, traps and exit statuses with meaning, cause, fix and a minimal example
  • Look up Omega keywords and topics, or search for up to 20 matching entries
When to use it
Useful when an assistant needs to write, check or debug Omega code, or answer questions about the Omega language, its compiler diagnostics and its runtime traps, without leaving the chat.
Requirements
Runs as a local process on the user's machine (desktop only, stdio transport). Built from an omega-mv checkout at a pinned commit with the seeded compiler; the server refuses any other compiler and re-checks its hash at start-up. Needs bubblewrap and prlimit on the host, and its reference data files beside the executable. No accounts, keys or environment variables are declared.
Before you install
The run tool executes arbitrary Omega code, so isolation matters: it relies on bubblewrap with no network, no host files and an empty environment, plus CPU, memory, file-size and wall-clock limits. The README states the isolation evidence covers only Linux arm64 with the tested bubblewrap and util-linux versions. A test-only flag that disables isolation exists and should never be given to an agent. Compile diagnostics are returned as successful results, not errors.

Installation

In SourceWeft

  1. Open Omega Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

omega-mcp

[Omega MCP on mcprush]

An MCP server, written in Omega, that lets an agent compile and run Omega (.om) programs with the pinned seeded compiler and look up the language. It speaks MCP (protocol version 2025-06-18) as newline-delimited JSON-RPC 2.0 over stdio.

Pin: omega-mv e5b32567a7aff3ce594e3254a622a846a6cd190b, omc sha256 2c82480596bbdc50cda9626866209ef662d5834f278f839ff4ce0250c495029f. build.sh refuses any other compiler, and the server checks the sha256 of its compiler again at start-up.

Tools

ToolArgumentsResult
compilesourceok, binary size and sha256, or the compile error {line, code, meaning, fix}
runsource, stdin, timeout_ms (1..30000, default 5000)compile result, capped stdout/stderr, and the exit: normal, trap (with its meaning), or the limit that stopped it (cpu_time, file_size, wall_clock, killed)
explain_errorquery: an error code 1..30, an omc: line N: error K line, trap T, or an exit status 101..114meaning, cause, fix, a minimal example and citations into omega-mv@e5b32567
lookupquery: a keyword or topic, or a substringthe entry (form, arity, types, result, example, citations), or up to 20 search hits

A compile diagnostic is a successful tool result (isError: false); isError is true when nothing could be run (sandbox failure, a refused compile stage) or when explain/lookup found no entry. Bad arguments are JSON-RPC errors (-32602).

Isolation

Each compile and run stage gets a fresh /tmp/omega-mcp-<16 hex> directory (mode 0700, removed after the reply) and runs under bwrap --unshare-all --clearenv. The sandbox sees only the compiler or the program (read-only), its in-sandbox reaper and a 16 MiB tmpfs working directory: no network, no host files, an empty environment. prlimit applies the resource limits to the sandbox before it starts, and the server kills the whole sandbox at the wall clock.

StageCPUAddress spaceFile sizeProcessesWall clock
run10 s256 MiB1 MiB5timeout_ms (default 5 s, max 30 s)
compile20 s512 MiB16 MiB420 s

Both stages also get 64 open files and no core dumps. --test-only-no-isolation turns all of this off and exists only so the trust gate can prove it detects an escape; never give it to an agent.

Build and use

sh
OMEGA_SRC=/path/to/omega-mv ./build.sh      # omega-mv checkout at e5b32567 with seed/out/omc builtbuild/omega-mcp                              # reads JSON-RPC on stdin; logs one line per request on stderr

The server loads data/reference.json and data/examples/ from beside its executable. Start-up exit codes: 2 bad arguments, 3 compiler not the pin, 4 data missing, 5 bwrap/prlimit missing. mcp.json is an example client configuration; point its command at your build/omega-mcp.

Gates

sh
python3 gates/smoke.py      # MCP client session; transcript in evidence/smoke-transcript.jsonlpython3 gates/trust.py      # trust boundary: 4 attacks plus negative controls; evidence/trust-gate.jsonpython3 tools/check-reference.py --omega-src $OMEGA_SRC --omc $OMEGA_SRC/seed/out/omc --self-test

trust.py sends, through the run tool, a read of a canary under ~/.local/state, a fork bomb, an infinite loop and a 10 GiB write, and requires each to be refused or killed with no process left behind. A second server started with --test-only-no-isolation runs bounded versions of the same attacks and must see them succeed, so a gate that cannot see an escape fails. check-reference.py re-derives every keyword, error and trap entry from the pinned source, compiles and runs every example with the pinned omc, and runs three negative controls.

These gates are host evidence on Linux arm64 (bubblewrap 0.9.0, util-linux 2.39.3); they say nothing about other kernels or about a sandbox configuration other than the one in src/sandbox.om.

Layout

  • src/*.om: the server (src/UNITS lists the concatenation order; build.sh builds it)
  • vendor/omega-mv/: sha256 and JSON units copied unchanged from omega-mv@e5b32567
  • data/: reference data and example programs, written by tools/gen-reference.py and checked by tools/check-reference.py
  • gates/, evidence/: verification oracles and their recorded results
  • DEPENDENCIES.md: every host tool in the build, runtime and verification paths

License: Apache-2.0 (see LICENSE and NOTICE).

Human-Directed Agentic Engineering

Development follows Human-Directed Agentic Engineering (HDAE): humans define goals, architecture, constraints, acceptance criteria, and stopping points; agents implement, execute checks, diagnose failures, and revise within those boundaries. Human review retains responsibility for claims, acceptance, and release decisions. This describes the development method, not a change to runtime autonomy or historical evidence.

For the documented method and a systems-software case study, see Gregory M. Kurtzer (2026), Ginux: Building an Independent Kernel That Runs Linux Userspace through Human-Directed Agentic Engineering, technical report, v1, Zenodo, https://doi.org/10.5281/zenodo.23682548.

Source: README.md at commit 784e47b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts