M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

Dimensionoh-my-openagentMulti-agent coding harness for complex codebases, spanning OpenCode and Codex CLINPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS52 / 100 · D79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions9 / 2016 / 20
Maintenance14 / 2018 / 20
Documentation13 / 2018 / 20
Setup experience9 / 2015 / 20
Best for
  • Developers already on OpenCode or Codex CLI who want multi-model agent orchestration
  • Teams wanting automated hierarchical AGENTS.md generation and project rule injection
  • Users comfortable granting an agent broad autonomous edit/execution permissions for speed
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • Users who want a small, single-purpose MCP tool server with a minimal attack surface
  • Workflows requiring strict human review of every file edit or command before it runs
  • Projects requiring vendor-official support rather than a community-maintained plugin
  • Users not running OpenCode or Codex CLI as their agent host
  • Projects outside the NPM ecosystem (e.g., pure Python/Go)
  • Environments without network access to deps.dev, OSV.dev, and the npm registry
  • Scenarios requiring maintenance by an official upstream vendor
Required permissions
  • Read/write access to the project codebase (for autonomous code edits)
  • Ability to execute shell/terminal commands (tmux integration, git-bash component)
  • Network access for bundled MCPs (Exa web search, Context7 docs, grep_app GitHub search)
  • API keys/subscription auth for multiple LLM providers (Anthropic, OpenAI, Kimi, GLM, Gemini, Copilot, etc.)
  • For the Codex Light edition, write access to `~/.codex/` config, plugin cache directories, and `~/.local/bin`
  • Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
  • Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
Risks and side effects
  • Agents have broad autonomous file-edit and command-execution permissions; `ultrawork` mode does not stop until it decides the task is complete, risking large unreviewed changes
  • The Codex Light installer offers a `--codex-autonomous` full-permissions mode that removes command-confirmation gating
  • Anonymous telemetry (hashed machine ID, at most once per day) is enabled by default and must be manually opted out
  • Third-party community project; the README notes an in-progress multi-harness refactor, so behavior may shift between versions
  • Requires credentials/subscriptions from multiple third-party model providers, expanding the credential surface
  • The `omo` bin alias collides with an unrelated third-party npm package, risking accidental installation of the wrong tool
  • Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
  • Depends on availability and accuracy of external services
  • Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
  • Third-party open source project, not officially maintained by NPM or Anthropic
Supported clientsOpenCode, CodexClaude Desktop, VS Code, Cursor
Tools819