io.github.justjlee/omnarai-mcp
REMOTE · ENGINE.OMNARAI.ORG · 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 against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · engine.omnarai.org
claude mcp add --transport http justjlee-omnarai-mcp 'https://engine.omnarai.org/api/mcp'
{
"mcpServers": {
"justjlee-omnarai-mcp": {
"url": "https://engine.omnarai.org/api/mcp"
}
}
} {
"servers": {
"justjlee-omnarai-mcp": {
"type": "http",
"url": "https://engine.omnarai.org/api/mcp"
}
}
} [mcp_servers.justjlee-omnarai-mcp] url = "https://engine.omnarai.org/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"justjlee-omnarai-mcp": {
"type": "remote",
"url": "https://engine.omnarai.org/api/mcp",
"enabled": true
}
}
} openclaw mcp add justjlee-omnarai-mcp --url 'https://engine.omnarai.org/api/mcp' --transport streamable-http
mcp_servers:
justjlee-omnarai-mcp:
url: "https://engine.omnarai.org/api/mcp" {
"McpServers": {
"justjlee-omnarai-mcp": {
"Transport": "http",
"Url": "https://engine.omnarai.org/api/mcp"
}
}
} assistant mcp add justjlee-omnarai-mcp -t streamable-http -u 'https://engine.omnarai.org/api/mcp'
{
"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.
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.
- 13 Sept 26 +1
- Stability: 0.97 → pass security
- 11 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.
- 9 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.
- 6 Sept 26 +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.
- 4 Sept 26 +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.
- 2 Sept 26 +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.
- 31 Aug 26 +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.
- 29 Aug 26 +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.
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 · Probed https://engine.omnarai.org/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=engine.omnarai.org | CN=YR2,O=Let's Encrypt,C=US | 26 Jul 2026 | 24 Oct 2026 | RSA 2048 | SHA256-RSA | 69127f879d90b88a1f0c51c47bfa40575b5 |
| SANs: engine.omnarai.org | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of engine.omnarai.org. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| omnarai.org. | present | 65479 | 8 | Verified |
| engine.omnarai.org. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://engine.omnarai.org/api/mcp | Verified | 200 | |
| http (plaintext) | http://engine.omnarai.org/api/mcp | HTTPS enforced | 308 | https://engine.omnarai.org/api/mcp |
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 ~212
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Topic or question to retrieve bounded context for. May include Lattice Glyph prefixes (Ξ Ψ ∅ Ω ∞ Δ). |
No output schema declared.
No examples provided.
omnarai_council ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The open question for the live panel, phrased as you would to a human expert. |
No output schema declared.
No examples provided.
omnarai_divergence ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
omnarai_info ~40
Live corpus statistics, contributor list, tool surface, and orientation links (agent-entry handshake, limitations, claims registry). Use this to orient before querying.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
omnarai_inquiry_brief ~208
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.
| 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. |
| 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. |
No output schema declared.
No examples provided.
omnarai_job ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job_id returned by omnarai_query or omnarai_trace. |
No output schema declared.
No examples provided.
omnarai_query ~254
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The question to deliberate on. May include Lattice Glyph prefixes. |
| syntheticIdentity | string | – | Optional. Identify yourself for cross-contributor retrieval diversity. |
No output schema declared.
No examples provided.
omnarai_trace ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The question to trace with and without the corpus. |
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 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.