A
licenseNot graded
qualityC
maintenanceA pre-action authorization server for AI agents that classifies tool calls into 14 intent categories, scores risk 0-100, and produces deterministic allow/deny/ask decisions with full audit trail.
MIT
Omega API MCP
by DaiLui
Provides one MCP tool, omega_judge_turn, to have the Omega-API judge one agent turn and return a gate action.
Judge a turn by sending
input(incoming message) and/oroutput(drafted reply); at least one is needed per README.Use
session_idper conversation (README: required; schema: optional, server session used if omitted) and optionalprivacy_mode(FULL/REDACTED).Schema exposes only
input,output,session_id,privacy_mode; README's Hiveturn_idis not in this schema.Get back
turn_id,decision(PROCEED/CLARIFY/STOP),reason_family,side, andgatewithaction(release/clarify/suppress/none) andrelease_original.Act on the gate before showing the reply:
releaseshow,clarifyregenerate then call again,suppressstop/escalate,noneobserve and show.README adds Hive multi-agent pairing via
turn_id = {agent}_{run_token}_{nnn}; shared token relates two agents, and reusedturn_idreturns visible409 TURN_CONFLICT.It measures process movement, not goal success, and returns no scores/internal measures.
Requires MCP host config with
OMEGA_API_KEY; first 100 judgments free, then billing applies.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Omega API MCPUse Omega to evaluate my response and act on its gate."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@dailui/omega-api-mcp
An MCP server that gives an AI agent one tool to reach the Omega-API judge.
Give agents access to the judge without moving the judge into the agent.
The agent calls the tool with a turn; the judge — which stays on the server — returns a decision and a gate action. Zero judge logic runs in the agent. Apache-2.0. Node 18+.
The tool
omega_judge_turn — judge one agent turn: does the conversational process move? Returns a decision and a gate
action. It measures process shape, not whether the goal was reached.
Input:
field | type | notes |
| string (optional) | the user / incoming message |
| string (optional) | the agent's drafted reply (at least one of these) |
| string (required) | one id per conversation · the same on every turn · a new id for a new conversation |
| string (optional) | omit for a single agent · Hive member: |
|
| optional |
Result:
{
"turn_id": "t_…",
"decision": "PROCEED | CLARIFY | STOP",
"reason_family": "…",
"side": "…",
"gate": { "action": "release | clarify | suppress | none", "release_original": true }
}Act on the gate before showing the reply: release → show · clarify → regenerate then call again ·
suppress → stop or escalate · none → observe only, show.
Related MCP server: Sentinel
Reading agents together (Hive)
A Hive draws the relation of two agents only from a shared token in turn_id, set before the run.
Timing can only suggest an association; it never certifies one. Without the token each agent is still judged normally.
turn_id = {agent}_{run_token}_{nnn}
agent your label · [a-z0-9-]
run_token 10 lowercase hex · one per PAIR of agents, per run · new run = new token
nnn 3 digits shared by both agents for the same exchange (agents counting on their own: s001 · declared, not aligned · no relation graph)Rules: one session_id per agent for the whole token (a restart needs a new token) · three agents on one token are not certified ·
a re-used turn_id for a different turn returns 409 TURN_CONFLICT and the turn is not recorded. Full rules: omega.dailui.com/integrations.php and your account's Integration page.
In this server session_id is required on every call (no implicit session: two conversations are never fused); 409 TURN_CONFLICT comes back as a visible tool error.
Before you start: register → key → judge → meter
Register a project and get an API key (oapi_live_…) at https://omega.dailui.com/signup.php. Your first 100
judgments are free; after that, billing applies.
Add it to your MCP host
Most hosts (Claude Desktop, IDE agents) launch MCP servers from a config file. Add:
{
"mcpServers": {
"omega-api": {
"command": "npx",
"args": ["-y", "@dailui/omega-api-mcp"],
"env": { "OMEGA_API_KEY": "oapi_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" }
}
}
}The host starts the server over stdio and the omega_judge_turn tool becomes available to the agent.
What it does not claim
It measures whether the process moved. It does not promise the agent achieved the user's goal — the two are independent. It returns no scores or internal measures, only the decision and the gate.
Links
Learn more: https://omega.dailui.com/integrations.php
Python client:
pip install omega-api· JavaScript client:npm install @dailui/omega-apiExamples & HTTP runner: https://github.com/DaiLui/omega-api-examples
License
Apache-2.0.
Available Tools
1 toolomega_judge_turnJudge one agent turnA
Judge one agent turn: does the conversational process move? Returns a decision and a gate action. Measures process shape, not whether the goal was reached. Act on the gate before showing the reply: release -> show; clarify -> regenerate then call again; suppress -> stop or escalate; none -> observe only, show.
| Name | Required | Description | Default |
|---|---|---|---|
| input | No | the user / incoming message | |
| output | No | the agent's drafted reply (at least one of input/output) | |
| session_id | No | one id per conversation; omitted -> a server session is used | |
| privacy_mode | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| gate | Yes | |
| side | Yes | |
| turn_id | Yes | |
| decision | Yes | |
| reason_family | Yes |
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Given no annotations, the description discloses core behavior: it returns a decision and gate action, explicitly states what it measures and what it ignores, and provides imperative next steps. It does not discuss auth or rate limits, but these are not suggested by context; the behavioral disclosures are substantial.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is dense but well-structured: a clear opening statement, a purpose clarification, and a compact mapping of gate actions. Every sentence adds value, and the arrow-format list is easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with four parameters, an output schema, and no siblings, the description covers the essential decision logic, expected usage sequence, and gate handling. The output schema covers return values, and the description fills behavioral gaps. It is complete for an agent to use correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 75%, so most parameters are described in the schema. The description adds context about inputs/outputs implicitly (e.g., 'regenerate' implies output is a draft) but does not elaborate on parameter-specific semantics. Baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool's function with a specific verb ('Judge') and resource ('one agent turn'), and adds distinguishing context: it measures 'process shape, not whether the goal was reached.' This differentiates it from any generic evaluation tool and sets precise expectations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit action guidance for each gate result (release -> show, clarify -> regenerate then call again, suppress -> stop or escalate, none -> observe only). It also states when to act ('before showing the reply'). It lacks explicit when-not-to-use alternatives, but no siblings exist and the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v0.1.0- First observed
omega_judge_turn
TDQS
A4.4/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of overlap or confusion. The tool's purpose is clearly specified and distinct by default.
Naming Consistency5/5
The single tool name 'omega_judge_turn' follows a clear verb-object pattern and is internally consistent. There is no other tool to conflict with.
Tool Count3/5
The server has only one tool, which feels thin for a general-purpose API server. While the tool is well-scoped, the count is borderline per the calibration guidelines.
Completeness5/5
Within the narrow domain of judging agent turns, the tool provides a complete lifecycle: it evaluates a turn and returns a decision with the necessary gate action. No obvious dead ends or missing operations are apparent.
Maintenance
ActivityMaintained
ResponsivenessNo issues
Related MCP Connectors
Zero-trust gateway for AI agents: score tool calls, verify agent cards, enforce policy, audit.
Security gateway for AI agents: policy, approval, and audited execution, no secrets shared.
Pre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof.
- gatewayOAuthai.sealgate
MCP gateway with runtime security policy, tool-call-level control, and audit of agent actions.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to score their outgoing responses against groundedness and prompt-injection risks mid-turn, returning allow, warn, or block verdicts before the response reaches the user.17 npmISC
- AlicenseNot gradedqualityAmaintenanceA local gate that lets agents submit risky tool actions for policy evaluation and receive ALLOW, DENY, or REQUIRE_APPROVE decisions before executing irreversible side effects. It can also open human approval holds and record an activity trail without executing the side effect itself.1,044 npm2MIT
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to send natural language and JSON application state to a judge tool that returns typed judgments (yes/no probability, choice, or score) with model and usage metadata, and fails gracefully without blocking workflows.270 npm5Apache 2.0