Omnia MCP server
Commit Nov 14, 2026Enables AI agents to perform structured decision-making, classifications, and scored assessments using JEV and local LAYA intelligence.
Also known as Omniaeye/omnia-mcp
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 14, 2026
- License
- Apache-2.0
What is Omnia MCP?
Omnia enables AI agents to perform structured decision-making, classifications, and scored assessments using JEV and local LAYA intelligence.
Summary generated from the project's README
About Omnia MCP server
Developers building AI agents can use omnia-mcp to implement structured decision-making, classifications, and scored assessments. By providing context and specific questions, agents receive usable results like probabilities, ordinal scores, and categorical choices. This allows for complex tasks such as evaluating news relevance, checking document completeness, or routing workflows based on specific criteria.
The server supports two distinct intelligence providers: JEV, which uses a hosted evaluation API from TypeSafe requiring an API key, and LAYA, which enables local inference through a runtime. Users can choose between hosted requests or offline operation using local weights and a configured device. The system includes a validation layer that applies review thresholds and records every decision in a SQLite ledger with model identity and evidence references.
Integration is handled via the Model Context Protocol, making it compatible with clients like Claude Desktop, Cursor, and VS Code. The server provides specific tools such as omnia_evaluate for single requests, omnia_evaluate_batch for collections, and omnia_get_decision to retrieve previous results by ID.
What you can do with it
- 1Classify software update typesAn agent can determine if a repository change is a product launch, a security update, or routine maintenance.
- 2Score editorial significanceA developer can task an agent with rating the importance of an update based on a custom rubric.
- 3Verify evidence supportAgents can assess whether a provided source supports or contradicts a specific claim.
- 4Check policy completenessThe server can evaluate if an observation contains all the required fields defined by a specific policy.
Written from the project's README. Every use case is checked against a quote from it.
Configuration
OMNIA_ALLOWED_PROVIDERSOMNIA_DEFAULT_PROVIDEROMNIA_LAYA_DEVICEOMNIA_LAYA_MODELOMNIA_LAYA_REVISIONOMNIA_LAYA_THREADSTYPESAFE_API_KEY
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableomniaeye/omnia-mcp is public and reachablegithub.com/omniaeye/omnia-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-14github.com/omniaeye/omnia-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubOMNIA MCP brings JEV and local LAYA into agent workflows through the Model Context Protocol. Give an agent the context, define the questions that matter, and receive decisions it can use: classifications, scored assessments, and probabilities for specific claims.
A single request can assess several dimensions of a document, conversation, software update, or market observation. OMNIA validates the answers, applies your review thresholds, and records the result with its model identity, policy, and evidence references.
Intelligence in context
The intelligence is in evaluating meaning against context and criteria. The answer format makes that assessment usable by software.
For a news item, an agent can assess the event type, its relevance, who made a claim, and whether the supplied source supports it. For a token observation, it can assess whether fields are complete, whether reported conditions match a policy, and which review category applies. Each question addresses a distinct part of the decision.
| Assessment | Question you can define | Native result |
|---|---|---|
| Event classification | Is this a product launch, a security update, routine maintenance, or something else? | choice: selected category and the probability of each alternative |
| Relevance and priority | How significant is the update under our editorial rubric? | score: a position across your ordered levels, with its distribution |
| Evidence support | Does the supplied source support, contradict, or leave a claim unaddressed? | choice: a bounded assessment of the supplied evidence |
| Attribution | Is the claim made by the main author, a quoted author, or is attribution unclear? | choice: explicit alternatives, including an unknown category |
| Completeness | Does this observation contain the fields required by our policy? | noul: a probability for the defined true/yes condition |
| Workflow routing | Which review queue or next step best fits this context? | choice: an application-defined route |
These are questions you configure through the same evaluation interface. Your application supplies the records and defines the available answers. Exact arithmetic, transaction limits, and mandatory requirements belong in deterministic application checks.
Several assessments can inform one action. An application can combine relevance, source support, and attribution before routing an item to an editor. It can combine field completeness, reported risk, and freshness checks before requesting a deeper market review. OMNIA returns the assessments; the application owns their combination and the action that follows.
JEV/LAYA, natively
OMNIA uses the providers' native decision types. It preserves selected labels, ordinal score semantics, probabilities, and available confidence fields in a common MCP response.
| JEV | LAYA | |
|---|---|---|
| Inference | TypeSafe's hosted evaluation API | Local inference through the public laya==0.3.20 runtime |
| Model identity | Explicit version; default jev-1.13.0 |
Explicit checkpoint family and full revision SHA |
| Input | Supplied text, JSON objects, or JSON arrays | The same request contract, within the selected checkpoint's input budget |
| Answers | choice, score, noul |
choice, score, noul |
| Operation | API credential, bounded HTTP requests, retry controls | Optional runtime, isolated worker, configured device and threads |
| Data path | Context and questions go to TypeSafe | Inference stays local; offline operation uses prepared dependencies and weights |
Choice compares the alternatives you define. Score evaluates an ordered rubric and can return a value between levels. Noul expresses the probability of a specified condition, retaining uncertainty instead of reducing the result to a bare boolean.
Questions in one request share the supplied state and are evaluated independently. For a dependent sequence, the calling agent can pass an earlier result into the next request. Provider selection is explicit; OMNIA does not silently move local context to a hosted service.
The decision path
flowchart LR
Agent[MCP client or agent] --> Context[Context and questions]
Context --> Model{JEV / LAYA}
Model --> Answers[Native typed answers]
Answers --> Policy[Validation and review policy]
Policy --> Record[Decision record]
Record --> Agent
The record includes a decision ID, input fingerprint, provider/model identity, answers, applied policy, review reasons, evidence references, timing, and available usage metadata. Repeated identical requests can reuse the configured cache. Earlier decisions can be retrieved by ID.
accepted means the response passed the configured checks. needs_review preserves answers that fall below a probability or margin threshold. Neither status grants permission to publish, trade, or execute an external action.
Evaluate several dimensions
This example asks three independent questions about one software update. It keeps the maintainer's statement separate from the quoted comment.
Call omnia_capabilities first, then send these arguments to omnia_evaluate:
{
"request": {
"state": {
"source": "GitHub",
"project": "Atlas SDK",
"main_author": "maintainer",
"main_update": "Version 2.4 is available. It adds streaming responses and fixes connection recovery.",
"quoted_comment": {
"author": "community_member",
"text": "This will double every customer's revenue."
}
},
"questions": {
"event_type": {
"type": "choice",
"instructions": "Classify main_update. Keep quoted_comment separate from the maintainer's statement.",
"criteria": {
"release": "An available software version with described changes",
"maintenance": "Routine repository upkeep without a release announcement",
"other": "Neither category is supported by the main update"
}
},
"relevance": {
"type": "score",
"instructions": "Rate the user-facing significance described in main_update, excluding quoted_comment.",
"criteria": [
"Routine bookkeeping with no described user-facing change",
"A minor improvement to existing behavior",
"A new capability or a described reliability fix"
]
},
"author_claim": {
"type": "noul",
"instructions": "Does main_update itself claim that customer revenue will double? Do not attribute quoted_comment to the maintainer."
}
},
"policy": {
"min_probability": 0.8,
"min_margin": 0.1
}
}
}
The response contains a separate answer for each question, plus the decision record and review status. The request above is an illustrative input; recorded provider results are in the validation report.
Quickstart
Requires Python 3.11–3.14. Install the released source with uv:
uv tool install "git+https://github.com/Omniaeye/omnia-mcp.git@v0.1.0"
omnia-mcp version
omnia-mcp doctor
To use JEV, set these variables in the environment that launches your MCP server:
OMNIA_DEFAULT_PROVIDER=jev
OMNIA_ALLOWED_PROVIDERS=jev
TYPESAFE_API_KEY=<your TypeSafe API key>
Register the installed executable in your client:
{
"mcpServers": {
"omnia": {
"command": "omnia-mcp",
"args": ["serve"]
}
}
}
Use an absolute executable path when the client cannot find omnia-mcp. The server reads its process environment; it does not automatically load .env files. .env.example lists every setting.
| Client | Configuration example |
|---|---|
| Claude Code | .mcp.json |
| Claude Desktop | claude_desktop_config.json |
| Cursor | mcp.json |
| VS Code | mcp.json |
These recipes follow each client's documented configuration format. See compatibility for client checks and supported transport.
Run LAYA locally
Install from a checkout when configuring the local runtime:
git clone https://github.com/Omniaeye/omnia-mcp.git
cd omnia-mcp
git checkout v0.1.0
python -m venv .venv
| Platform | Install the local runtime |
|---|---|
| macOS / Linux | .venv/bin/python -m pip install ".[local-laya]" |
| Windows PowerShell | .\.venv\Scripts\python.exe -m pip install ".[local-laya]" |
Configure the provider and checkpoint:
OMNIA_DEFAULT_PROVIDER=laya
OMNIA_ALLOWED_PROVIDERS=laya
OMNIA_LAYA_MODEL=english
OMNIA_LAYA_REVISION=55cf4c4ebb4ebe31b2550e8bdf3bd21b99753851
OMNIA_LAYA_DEVICE=cpu
OMNIA_LAYA_THREADS=2
Point your MCP client at .venv/bin/omnia-mcp or .venv\Scripts\omnia-mcp.exe. This configuration selects the checkpoint used in the recorded local smoke tests. typed-decisions and multilingual are also supported checkpoint-family selections; choose and validate the corresponding revision and input limits for your task.
For offline operation, prepare the exact snapshot and dependencies before setting OMNIA_LAYA_OFFLINE=true. To enable both providers, use OMNIA_ALLOWED_PROVIDERS=jev,laya, configure each, and select one through request.provider or OMNIA_DEFAULT_PROVIDER. See configuration.
MCP interface
| Tool | Arguments | Purpose |
|---|---|---|
omnia_evaluate |
request |
Evaluate the questions against one supplied state. |
omnia_evaluate_batch |
request.items |
Evaluate a bounded collection of requests with per-item results or errors. |
omnia_capabilities |
None | Inspect enabled providers, question types, and operating limits. |
omnia_get_decision |
decision_id |
Retrieve a persisted decision without another inference call. |
Resources: omnia://guide for usage and omnia://schemas for complete contracts. The same schemas are available locally:
omnia-mcp schemas
doctor checks configuration and package presence without loading a model or making a provider call. serve starts the stdio server; running omnia-mcp with no subcommand does the same.
Operating controls
Configure input size, question count, batch size, concurrency, queue capacity, deadlines, retries, and per-minute/per-day evaluation allowances. Responses are validated against the submitted questions, including rubric identity and rounded probability consistency. Failed requests return explicit errors.
The SQLite ledger retains answers, labels, rubric descriptions, evidence references, fingerprints, and model metadata. It does not retain the full input state by default. Cache lifetime and automatic retention are configurable; records can still contain sensitive application data.
Evidence references are carried with a decision, not fetched. Supply the actual source text when a question needs it. Applications own collection, exact rule enforcement, publication, and execution. OMNIA MCP provides typed assessments rather than free-form text generation or autonomous trading.
Validation
The release has recorded real JEV and local LAYA inference checks, stdio integration tests, Docker checks, and Windows/Linux CI across Python 3.11–3.13.
The multilingual JEV acceptance suite covers software updates, quoted authorship, missing fields, and explicit snapshot rules in English, Portuguese, Chinese, and Japanese. Its initial 100 evaluations exposed a rounding-validation defect. After the correction, a fresh run passed 20/20 cases and 48/48 answer checks. The complete controlled suite passed 175 tests.
Read the results and original evidence. These results describe the recorded cases; choose thresholds against reviewed examples from your own workload.
OMNIA software
| Project | Focus |
|---|---|
| OMNIA MCP | The agent-facing interface to hosted JEV and local LAYA. |
| OMNIA LAYA | OMNIA's independent Laya integration fork for local decision workflows. |
| OMNIA News | Source-content assessment and configurable feed decisions. |
| OMNIA Trading | Market, holder, liquidity, and risk observation assessments. |
These are separate repositories. This MCP package connects directly to TypeSafe and the public LAYA runtime; it does not automatically install or run the News and Trading pipelines.
Documentation and development
Architecture · Configuration · Compatibility · Releasing · Security · Contributing
python -m pip install --upgrade pip
python -m pip install -e . --group dev
python -m ruff check .
python -m ruff format --check .
python -m pytest
python -m build
python -m twine check dist/*
The default suite requires no provider credentials. Live inference remains explicit opt-in.
Provider references: JEV state and context · Composing assessments · Evidence assessment · LAYA upstream.
License and attribution
Apache License 2.0. Original OMNIA MCP code is maintained by OMNIA EYE Corporation. JEV is provided through TypeSafe; LAYA is developed by Convai Innovations. Upstream authorship, licenses, service terms, and model terms remain with their respective projects. See NOTICE.
Omnia MCP questions
What can OMNIA evaluate?
It can perform event classification, relevance and priority scoring, evidence support assessment, attribution, completeness checks, and workflow routing.
How does OMNIA handle decision records?
It uses a SQLite ledger to retain answers, labels, rubric descriptions, evidence references, and model metadata, allowing decisions to be retrieved by ID.