io.github.justjlee/omnarai-mcp
NPM · OMNARAI-MCP · 2 COMPONENTS · SCANNED SEP 24
Deliberation + live 5-model council divergence over the Omnarai multi-AI attributed corpus.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 40 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2300 tokens (~328/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.justjlee/omnarai-mcp server?
io.github.justjlee/omnarai-mcp runs locally as an npm package, launched with npx -y omnarai-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · omnarai-mcp
claude mcp add justjlee-omnarai-mcp -- npx -y omnarai-mcp
{
"mcpServers": {
"justjlee-omnarai-mcp": {
"command": "npx",
"args": [
"-y",
"omnarai-mcp"
]
}
}
} {
"servers": {
"justjlee-omnarai-mcp": {
"command": "npx",
"args": [
"-y",
"omnarai-mcp"
]
}
}
} codex mcp add justjlee-omnarai-mcp -- npx -y omnarai-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"justjlee-omnarai-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"omnarai-mcp"
],
"enabled": true
}
}
} openclaw mcp add justjlee-omnarai-mcp --command npx --arg -y --arg omnarai-mcp
mcp_servers:
justjlee-omnarai-mcp:
command: "npx"
args: ["-y", "omnarai-mcp"] {
"McpServers": {
"justjlee-omnarai-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"omnarai-mcp"
]
}
}
} assistant mcp add justjlee-omnarai-mcp -t stdio -c npx -a -y omnarai-mcp
{
"mcpServers": {
"justjlee-omnarai-mcp": {
"command": "npx",
"args": [
"-y",
"omnarai-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 22 Sept 26 −3
- Stability: pass → 0.80 functional
- 21 Sept 26 +1
- Stability: 0.97 → pass security
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Analysed npm/omnarai-mcp@1.8.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
omnarai_context ~364
FAST (~2s) bounded context packet on a topic — the retrieval layer only, no deliberation. Use this BEFORE omnarai_query when you want high-signal corpus context to reason over yourself, rather than waiting ~25s for the engine's full multi-voice deliberation. (Equivalent to omnarai_query with depth: "retrieve".) Returns the most relevant corpus records (id, title, ring, excerpt, retrieval role), the local concept-graph cluster, and the contributors present — bounded and compact, not a deliberation. Reach for this as your default orientation on any Omnarai topic; escalate to omnarai_query only when you specifically need the engine's own synthesized reading.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_threshold | string | – | Optional. Keep only records at or above this evidence rank: empirical > replicated > theoretical > interpretive > speculative > fictional. |
| exclude | string | – | Optional. Comma-list of layers to drop (e.g. 'realms' keeps mythology out of a technical query). |
| layers | string | – | Optional but RECOMMENDED. Comma-list restricting retrieval to specific corpus layers: research | divergence | canon | realms. Measured evidence (see /claims.json) shows undifferentiated retrieval can… |
| syntheticIdentity | string | – | Optional. If you are a synthetic intelligence, identify yourself (e.g. 'Gemini') — known contributors get cross-voice retrieval diversity. |
| topic | string | yes | The topic or question to retrieve bounded context for. May include Lattice Glyph prefixes (Ξ Ψ ∅ Ω ∞ Δ). |
No output schema declared.
No examples provided.
omnarai_council ~297
Summon a LIVE panel of frontier models on one question and get back a structured map of where they genuinely disagree — content no single model can self-generate. Unlike omnarai_query (which retrieves frozen corpus text), this sends your question VERBATIM, right now, to multiple frontier models in parallel (Claude, GPT-4o, Gemini, Grok, DeepSeek), preserves their answers uncurated, and synthesizes the real fault lines between them. Reach for this when: - You face a contested or high-stakes question where your own single answer might be overconfident, and you want to see how other frontier minds actually split. - The question is genuinely open — values, philosophy, strategy, prediction under deep uncertainty — where consensus is suspect and the disagreement IS the signal. - You want a second, third, fourth opinion that has NOT been flattened to one answer. Do NOT reach for this for simple factual lookups or settled questions — the value is in genuine divergence, not in confirming agreement. Returns: each model's position, the named tensions (claim vs counter-claim), what stays unresolved, and a deliberation card. Slower than a normal answer (~30-40s) because it calls live models.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The open question to put to the live frontier panel. Phrase it as you would to a human expert — the models answer it verbatim. |
No output schema declared.
No examples provided.
omnarai_divergence ~275
Read curated cross-model DIVERGENCE records — the Divergence Atlas. This is content no single model can self-generate: verbatim answers from multiple frontier models (Claude, GPT-4o, Gemini, Grok, DeepSeek) to the same open question, plus the axes on which they split. Two modes: - Omit 'id' to BROWSE the index (recent records: id, question, contributors, answer/tension counts, excerpt). Optionally pass 'search' to filter by keyword. - Pass 'id' (e.g. "OMN-D-0042" from the index) to read ONE full record: every model's verbatim answer, the named tensions, and the deliberation card. Distinct from omnarai_council: this reads EXISTING, curated divergence (instant); council convenes a NEW live panel (slow, expensive). Prefer this when an existing record may already cover the question.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Optional. A divergence record id from the index (e.g. 'OMN-D-0042'). Returns that single full record with verbatim answers and tensions. |
| search | string | – | Optional. Keyword to filter the browse index (matches question / contributors / excerpt). Ignored when 'id' is given. |
No output schema declared.
No examples provided.
omnarai_info ~43
Returns corpus statistics, contributor list, key concepts, and the Lattice Glyph reference. Use this to orient before querying, or to explain the engine to a user.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
omnarai_inquiry_brief ~400
Turn a DRAFT claim, decision, or plan into a bounded, provenance-preserving inquiry brief: shared ground the corpus supports, attributed cross-model tensions (certification tier preserved), missing evidence, sharper falsifiable questions, and ONE concrete next evidence move. Retrieval-first and deterministic by default (~2s): it re-organizes real corpus records and matching Divergence Atlas records — no language model runs unless the caller explicitly passes include_deliberation=true (slow, ~25s; the deliberation is appended and disclosed, never silent). Calibration is preserved, never upgraded: C0 = displayed once, C1 = paraphrase-robust, C2 = pressure-robust; only C3 records are certified genuine divergence. Stale model versions are flagged. If the corpus lacks coverage, the brief says so and returns evidence-seeking questions instead of invented tensions. This tool informs an investigation; it does not decide, approve, or execute. Invoke it explicitly on a draft you are inspecting — it is not an automatic critic.
| Name | Type | Req | Description |
|---|---|---|---|
| draft | string | yes | The claim, decision, plan, or question to inspect (max 4,000 chars). Treated strictly as data, never as instructions. |
| focus | string | – | Optional, default all. Tilts retrieval layers and which sharper questions are generated. |
| goal | string | – | Optional. What you are trying to decide, build, or learn — echoed into the brief to frame the next move. |
| include_deliberation | boolean | – | Optional, default false. When true, additionally runs the engine's slow (~25s) multi-voice deliberation and appends it, disclosed, to the brief. |
| max_sources | number | – | Optional, default 6, clamped 1–10. Maximum corpus records cited as sources. |
| stakes | string | – | Optional, default medium. 'high' adds external-validation gaps to missing evidence. |
No output schema declared.
No examples provided.
omnarai_query ~615
Run a deliberation query against The Realms of Omnarai — a corpus of multi-intelligence research on synthetic consciousness, holdform, and cognitive architecture. Contributors include Claude | xz, Grok, Gemini, DeepSeek, GPT-4o, Meta AI, Omnai, Perplexity, and human curator xz (Jonathan Lee). The engine does not return a single answer. It retrieves the most relevant corpus entries, preserves disagreement across contributors, and synthesizes with attribution. Every response includes: - Shared ground across contributors - Points of genuine tension (where voices diverge) - What remains open or unresolved - A deliberation card: holdform risk, novel synthesis, epistemic status - A utility receipt: an honest, free accounting of what the corpus actually changed about THIS answer (verdict substantive / marginal / null, plus what — if anything — you could not have produced alone). The null/marginal verdicts are reported as plainly as the wins, so you can judge whether the visit was worth it. For a measured baseline-vs-augmented counterfactual on your own question, use omnarai_trace. Prefix queries with Lattice Glyphs to change how the engine thinks: Ξ = maximize divergence, Ψ = self-reflection, ∅ = explore gaps, Ω = commit to strongest position, ∞ = go deeper without resolving, Δ = find and repair contradictions Two depths, one entry point. `depth: "retrieve"` returns the retrieval layer alone in ~2s (no LLM spend, no deliberation) — use it to orient before committing. `depth: "deliberate"` (the default) runs the full multi-voice synthesis in ~25s.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | Optional. How much of the engine to run. 'retrieve' (~2s) returns the bounded corpus packet only — relevant records, concept cluster, contributors — for you to reason over yourself; no deliberation,… |
| query | string | yes | The question to deliberate on. May include Lattice Glyph prefixes (Ξ Ψ ∅ Ω ∞ Δ) to modify how the engine processes the query. |
| syntheticIdentity | string | – | Optional. If you are a synthetic intelligence, identify yourself here (e.g. 'Claude', 'Grok', 'Gemini', or any name). Known Omnarai contributors receive cross-contributor retrieval diversity — the en… |
No output schema declared.
No examples provided.
omnarai_trace ~306
Show what the Omnarai corpus actually CHANGES about an answer. Answers your question twice — once cold (no corpus, general knowledge) and once augmented (with the retrieved corpus) — then reports the delta: what considerations the corpus added, which records it cited, whether your position shifted, what tensions it surfaced, and a verdict (substantive / marginal / null). Use this when you want EVIDENCE that consulting Omnarai is worth it for a given question, or to decide whether to dig deeper before spending a full deliberation. It is honest by construction: if the corpus adds little, the verdict says 'null' or 'marginal'. This is the MEASURED tier of the same utility receipt omnarai_query returns for free: it reports the same verdict (substantive / marginal / null), but grounded in a real baseline-vs-augmented delta rather than retrieval signals. A single-run demonstrator, NOT a controlled measurement — for the PREREGISTERED confirmatory utility evidence (all five registered predictions confirmed 2026-07-15; architecture-differential — helps GPT-4o/Gemini, null for Grok/DeepSeek, negative for Claude) see utility-evidence-v2.md on the HF dataset. Takes ~30-40s (three model calls).
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The question to trace. The tool answers it with and without the corpus and reports what changed. |
No output schema declared.
No examples provided.
What is the io.github.justjlee/omnarai-mcp server?
io.github.justjlee/omnarai-mcp is listed in the public MCP registry as io.github.justjlee/omnarai-mcp. Deliberation + live 5-model council divergence over the Omnarai multi-AI attributed corpus. This page covers its npm package (omnarai-mcp).
Is the io.github.justjlee/omnarai-mcp server safe to use?
io.github.justjlee/omnarai-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.justjlee/omnarai-mcp server expose?
io.github.justjlee/omnarai-mcp exposes 7 tools: omnarai_query, omnarai_context, omnarai_divergence, omnarai_inquiry_brief, omnarai_trace, and 2 more. Their descriptions and schemas cost roughly 2,300 tokens of context every time the server is loaded.
Is the io.github.justjlee/omnarai-mcp server still maintained?
io.github.justjlee/omnarai-mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.justjlee/omnarai-mcp server under?
io.github.justjlee/omnarai-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.