ooruby: verified AI agents and MCP servers

Agent Swarm

agent-swarm.dev — an open-source operating system for AI work: a lead agent breaks goals into tasks, routes them to specialized workers such as Claude Code or Codex, runs each worker in an isolated co

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

The registry now serves 1.161.0. Everything measured on this page describes 1.155.1.

Findings, provenance and the install command are records of the scanned version, not the one npm would give you today. Treat them as history until this listing is rescanned. Registry checked 2026-10-02.

Not yet tested

Command execution is bounded: inventory; node child_process (templates/community/dora-metrics/report.mjs:3); synchronous shell execution (templates/community/dora-metrics/report.mjs:58); dynamic Function constructor (src/workflows/wait-filter.ts:213); dynamic Function constructor (src/workflows/executors/code-match.ts:50); 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.

Corrected after a reading by hand on 2026-09-30

No shipped credentials: the automated note “The scan matched 17 credential-shaped strings in the published files. Location withheld pending disclosure to the maker.” was withdrawn. Test values in its secret-scrubbing and extension tests.

How it was read

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 1.155.1, the file with digest sha512-L+9Wuc8cbKcma4EIMBahdaIjEiefjc01aUokixZJiNImVWDOMlOs0gKtyb4/KF7kUbQgPSyxD6ITrUVjcY0BtQ==, 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

Its entry in the official MCP registry says the server is started with arguments this page cannot print without guessing, so there is no command here rather than one that would not start it. The maker's own instructions are at the source linked on this page.

35,117 installs last month (via ecosyste.ms) · build provenance signed · no published advisories · checked 2026-10-02

Where this came from

Registry: npm
Package: @desplega.ai/agent-swarm
Version read: 1.155.1
Resolved: 2026-09-25

Open the source

No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.

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/desplega-ai-agent-swarm)](https://ooruby.com/market/desplega-ai-agent-swarm)

About this listing

Kind: MCP server
Category: Sales & CRM
Pricing: Free
Sandbox: No
Hosted: No
Updated: 2026-09-25

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.