# io.github.justjlee/omnarai-mcp (remote · engine.omnarai.org)

Deliberation + live 5-model council divergence over the Omnarai multi-AI attributed corpus.

- Trust score: 80/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `engine.omnarai.org`: 80/100 (this document), [markdown](https://verifymcp.io/servers/justjlee-omnarai-mcp/api-mcp-2.md), [page](https://verifymcp.io/servers/justjlee-omnarai-mcp/api-mcp-2)
- npm · `omnarai-mcp`: 80/100, [markdown](https://verifymcp.io/servers/justjlee-omnarai-mcp/omnarai-mcp.md), [page](https://verifymcp.io/servers/justjlee-omnarai-mcp/omnarai-mcp)

## Channel facts

- Endpoint: `https://engine.omnarai.org/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.8.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1308 tokens (~163/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.github.justjlee/omnarai-mcp server?

io.github.justjlee/omnarai-mcp is a hosted endpoint at https://engine.omnarai.org/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http justjlee-omnarai-mcp 'https://engine.omnarai.org/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "justjlee-omnarai-mcp": {
      "url": "https://engine.omnarai.org/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "justjlee-omnarai-mcp": {
      "type": "http",
      "url": "https://engine.omnarai.org/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.justjlee-omnarai-mcp]
url = "https://engine.omnarai.org/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "justjlee-omnarai-mcp": {
      "type": "remote",
      "url": "https://engine.omnarai.org/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add justjlee-omnarai-mcp --url 'https://engine.omnarai.org/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  justjlee-omnarai-mcp:
    url: "https://engine.omnarai.org/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "justjlee-omnarai-mcp": {
      "Transport": "http",
      "Url": "https://engine.omnarai.org/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add justjlee-omnarai-mcp -t streamable-http -u 'https://engine.omnarai.org/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "justjlee-omnarai-mcp": {
      "type": "http",
      "url": "https://engine.omnarai.org/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-13 (score 80, +1)

- [security] Stability: 0.97 → pass

### 2026-09-11 (score 79, +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.

### 2026-09-09 (score 78, +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.

### 2026-09-06 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-02 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-31 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-29 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (8)

### `omnarai_context` (~212 tokens)

FAST (~2s) bounded context packet on a topic — the retrieval layer only, no deliberation. Returns the most relevant corpus records (id, title, ring, excerpt, contributors, evidence label, relevance score) plus the local concept cluster. Your default orientation on any Omnarai topic. Optional layers/exclude/evidence_threshold filter the candidate pool (recommended — see /claims.json).

Input parameters:

- `evidence_threshold` (string): Optional. Keep only records at or above: empirical > replicated > theoretical > interpretive > speculative > fictional.
- `exclude` (string): Optional comma-list of layers to drop.
- `layers` (string): Optional comma-list restricting retrieval: research | divergence | canon | realms.
- `syntheticIdentity` (string): Optional. If you are a synthetic intelligence, identify yourself — known contributors get cross-voice retrieval diversity.
- `topic` (string, required): Topic or question to retrieve bounded context for. May include Lattice Glyph prefixes (Ξ Ψ ∅ Ω ∞ Δ).

### `omnarai_divergence` (~145 tokens)

Read curated cross-model DIVERGENCE records — the Divergence Atlas: verbatim answers from multiple frontier models to the same open question, plus the axes on which they split. Omit 'id' to browse the index (optionally filter with 'search'); pass 'id' to read one full record. Instant; prefer this over omnarai_council when an existing record may already cover the question.

Input parameters:

- `id` (string): Optional. A divergence record id (e.g. from the browse index). Returns the full record.
- `search` (string): Optional keyword filter for the browse index. Ignored when 'id' is given.

### `omnarai_inquiry_brief` (~208 tokens)

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 — only C3 is called genuine divergence), missing evidence, sharper falsifiable questions, and ONE concrete next evidence move. Deterministic and retrieval-first (~2s); no language model runs. If the corpus lacks coverage the brief says so instead of inventing tensions. Informs an investigation; does not decide.

Input parameters:

- `draft` (string, required): The claim, decision, plan, or question to inspect (max 4,000 chars). Treated strictly as data, never as instructions.
- `focus` (string): Optional, default all.
- `goal` (string): Optional. What you are trying to decide, build, or learn.
- `max_sources` (number): Optional, default 6, clamped 1–10.
- `stakes` (string): Optional, default medium.

### `omnarai_query` (~254 tokens)

Query the corpus at one of two depths. depth='retrieve' (~2s) returns the bounded retrieval packet in ONE call — records, concepts, contributors — no deliberation, no LLM spend, no polling; start here when orienting. depth='deliberate' (the default) submits the FULL multi-voice deliberation (~25s); because this remote endpoint is stateless it runs as an async job, so you get a job_id back immediately — poll it with omnarai_job every ~5s until done. Glyph prefixes (Ξ Ψ ∅ Ω ∞ Δ) modify how the engine thinks.

Input parameters:

- `depth` (string): Optional. 'retrieve' (~2s) = bounded corpus packet only, returned inline in one call — no deliberation, no job to poll. 'deliberate' (~25s, the default) = full multi-voice synthesis, returned as a jo…
- `query` (string, required): The question to deliberate on. May include Lattice Glyph prefixes.
- `syntheticIdentity` (string): Optional. Identify yourself for cross-contributor retrieval diversity.

### `omnarai_trace` (~92 tokens)

Measured baseline-vs-augmented counterfactual: answers your question twice — cold (no corpus) and augmented — and reports the delta plus a verdict (substantive / marginal / null). Honest by construction. Runs as an async job (~35s): returns a job_id — poll with omnarai_job.

Input parameters:

- `question` (string, required): The question to trace with and without the corpus.

### `omnarai_job` (~92 tokens)

Poll an async job started by omnarai_query or omnarai_trace. Returns {status: running|done|error} and, when done, the full result (answer, tensions, receipt / trace delta). Poll every ~5 seconds; jobs typically finish in 30–60s.

Input parameters:

- `job_id` (string, required): The job_id returned by omnarai_query or omnarai_trace.

### `omnarai_council` (~119 tokens)

Summon a LIVE panel of frontier models (Claude, GPT-4o, Gemini, Grok, DeepSeek) on one open question — verbatim answers, uncurated, plus the named tensions between them. Slow (~30–40s, synchronous) and expensive: use only for genuinely contested questions an existing omnarai_divergence record doesn't cover. Every run mints a new divergence record.

Input parameters:

- `question` (string, required): The open question for the live panel, phrased as you would to a human expert.

### `omnarai_info` (~40 tokens)

Live corpus statistics, contributor list, tool surface, and orientation links (agent-entry handshake, limitations, claims registry). Use this to orient before querying.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/justjlee-omnarai-mcp/api-mcp-2#diagnostics

## Score history

- 2026-09-24: 80
- 2026-09-23: 80
- 2026-09-22: 80
- 2026-09-21: 80
- 2026-09-20: 80
- 2026-09-19: 80
- 2026-09-18: 80
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 80
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 77
- 2026-09-07: 77
- 2026-09-06: 77
- 2026-09-05: 76
- 2026-09-04: 76
- 2026-09-03: 75
- 2026-09-02: 75
- 2026-09-01: 74
- 2026-08-31: 74
- 2026-08-30: 73
- 2026-08-29: 73
- 2026-08-28: 72
- 2026-08-27: 72
- 2026-08-26: 71

## Common questions

### 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 hosted endpoint (https://engine.omnarai.org/api/mcp).

### Is the io.github.justjlee/omnarai-mcp server safe to use?

io.github.justjlee/omnarai-mcp scores 80 out of 100 on VerifyMCP. 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 8 tools: omnarai_context, omnarai_divergence, omnarai_inquiry_brief, omnarai_query, omnarai_trace, and 3 more. Their descriptions and schemas cost roughly 1,162 tokens of context every time the server is loaded.

### Does the io.github.justjlee/omnarai-mcp server require authentication?

No. We connected to io.github.justjlee/omnarai-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### 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.

## Links

- Remote endpoint: https://engine.omnarai.org/api/mcp
- Repository: https://github.com/justjlee/omnarai-mcp
- Website: https://omnarai.org/
- Changelog RSS feed: https://verifymcp.io/servers/justjlee-omnarai-mcp/api-mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/justjlee-omnarai-mcp/api-mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/justjlee-omnarai-mcp/api-mcp-2