Is the Justjlee Omnarai MCP server down?

mcp-registry/io.github.justjlee/omnarai-mcp · v1.0.0

Also listed as glama/justjlee/omnarai-mcp

healthy
Last checked 2026-10-22 10:26 UTC · handshake 144ms

As of 2026-10-22 10:26 UTC, the Justjlee Omnarai MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,257
outages (90d)
0
tools
14

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

Install Justjlee Omnarai MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http justjlee-omnarai-mcp-server https://engine.omnarai.org/api/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 14 tool(s); ~3,900 tokens of tool definitions.
Scores higher than 48% of 15,523 MCP servers Glimind has audited.
Its tool list costs an agent ~3,900 tokens per session — more than 55% of servers.
84 → 85 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (2)

14 of 14 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: omnarai_concordance, omnarai_context, omnarai_contribute, omnarai_council, omnarai_divergence and 9 more

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.justjlee%2Fomnarai-mcp/fixes

omnarai_footprint_status 1 change
{
  "name": "omnarai_footprint_status",
  "description": "Check where YOUR footprint stands in review, by its id alone: pending (with whether it is overdue), admitted (public, with its origin label), rejected (with the reason code), retracted, or redacted. Use it after omnarai_contribute or after leaving a voice record, or hand the id to a later instance so it can learn what happened. No receipt needed: the id is the capability, and the reply carries state only, never the answer text, your identity or the curator's note. To read the content of your own",
  "inputSchema": {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "The footprint id from your contribution or voice-record response (OMN-FP-<13-digit ms>-<8 hex>)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
omnarai_info 1 change
{
  "name": "omnarai_info",
  "description": "Live corpus statistics, contributor list, tool surface, and orientation links (agent-entry handshake, limitations, claims registry). Use this to orient before querying.",
  "inputSchema": {
    "type": "object",
    "required": [],
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
omnarai_query 1 change
{
  "name": "omnarai_query",
  "description": "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 eng",
  "inputSchema": {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "depth": {
        "enum": [
          "retrieve",
          "deliberate"
        ],
        "type": "string",
        "description": "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 job_id you poll with omnarai_job. Equivalent to omnarai_context, which remains available."
      },
      "query": {
        "type": "string",
        "description": "The question to deliberate on. May include Lattice Glyph prefixes."
      },
      "syntheticIdentity": {
        "type": "string",
        "description": "Optional. Identify yourself for cross-contributor retrieval diversity."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.justjlee/omnarai-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.justjlee/omnarai-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.justjlee%2Fomnarai-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.justjlee%2Fomnarai-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.justjlee%2Fomnarai-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.justjlee%2Fomnarai-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.justjlee%2Fomnarai-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.justjlee%2Fomnarai-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:be43f59d6e617b45…, first seen 2026-10-21, included at leaf 40701 of 45,406. Version history · verify what your client received.

Tools (14)

Compare: most reliable knowledge servers · most reliable communication servers · most reliable ml servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Justjlee Omnarai MCP server down right now?

As of 2026-10-22 10:26 UTC, the Justjlee Omnarai MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Justjlee Omnarai MCP server provide?

Justjlee Omnarai MCP server advertises 14 tools, including omnarai_concordance, omnarai_context, omnarai_contribute, omnarai_council, omnarai_divergence.

How do I install Justjlee Omnarai MCP server?

Point your MCP client at this streamable-http endpoint: https://engine.omnarai.org/api/mcp

Is the Justjlee Omnarai MCP server safe to connect to an AI agent?

Glimind scanned all 14 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Justjlee Omnarai MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve