ooruby: verified AI agents and MCP servers

Neo Mjs

tobiu · MCP server

Neo.mjs is a self-evolving software organism: a professional end-to-end AI engineering team whose cross-model swarm inhabits live apps via Neural Link, Active Hybrid GraphRAG, DreamService, and self-h

Not claimed by its maker. Is this yours? Prove it and answer the findings

From the maker

From the README of neo.mjs 13.1.0

Not yet tested

No shipped credentials: finding; The scan matched 5 credential-shaped strings in the published files. Location withheld pending disclosure to the maker.
Command execution is bounded: inventory; node child_process (test/playwright/unit/hooks/codexLaneStateStopHook.spec.mjs:2); node child_process (test/playwright/unit/hooks/laneStateStopHook.spec.mjs:5); node child_process (test/playwright/unit/ai/ensureAgentRepoGit.spec.mjs:2); synchronous shell execution (test/playwright/unit/ai/ensureAgentRepoGit.spec.mjs:20); An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.

Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.

What this does not cover

Everything. Treat it as you would software from anywhere else.

Receipt history: every signed receipt for every version of this listing, and what changed between them.

What it does

Compare with

Compare all 4

How far this has been checked

Static scanned

What it establishes: Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
What it does not: How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
Exactly what was read: Version 13.1.0, the file with digest sha512-FT0jTyH6tdzKPFv/GC1+wXRERSyjw/ZVFrkJmqsrNijYbQQTrVncA5NGt9W83ftwFweAZDmXf9uuA1fWurW0tw==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.

How the rungs work

Adding it

Paste this into your client's MCP configuration.

{
  "mcpServers": {
    "neo-cc": {
      "command": "npx",
      "args": [
        "-y",
        "neo.mjs@13.1.0"
      ]
    }
  }
}

Or run it directly.

npx -y neo.mjs@13.1.0

Pinned to 13.1.0, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.

18,163 installs last month (via ecosyste.ms) · build provenance signed · no published advisories · version current · checked 2026-10-04

Where this came from

Registry: npm
Package: neo.mjs
Version read: 13.1.0
Resolved: 2026-08-22

Open the source

Built from source, attested

npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.

Repository: github.com/neomjs/neo
Commit: 69d254a74f7b
Built by: github.com/actions/runner/github-hosted

The badge, if this is your listing

It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.

[![ooruby: static scanned](https://ooruby.com/api/badge/neo-mjs)](https://ooruby.com/market/neo-mjs)

About this listing

Kind: MCP server
Category: Developer tools
Pricing: Free
Sandbox: No
Hosted: No
Updated: 2026-08-22

Similar MCP servers

Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.