orchex
orchex is an MCP server published by wundam, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does orchex support the current MCP specification (2026-07-28)?
Not yet confirmed. orchex is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is orchex a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for orchex (as of 2026-08-20).
How do I connect to orchex?
orchex is available via the package npm:@wundam/orchex, the official MCP Registry under io.github.wundam/orchex, the source repository at https://github.com/wundam/orchex. Authentication: unknown. Transports: stdio.
Does orchex support MCP revision 2025-11-25?
Yes. orchex supports MCP revision 2025-11-25 (checked 2026-08-20).
Does orchex support MCP revision 2026-07-28?
No. orchex was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were orchex's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Autopilot AI orchestration — auto-plan, parallelize, self-heal, and route across 6 LLMs.
Which MCP spec revisions does orchex support?
orchex has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is orchex?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for orchex
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
The repository this server declares no longer resolves. That is a measurement, not
a failed lookup: https://github.com/wundam/orchex returned 404 when checked.
Package (npm) as of
- Latest version
1.0.0-rc.32- Last published
- First published
- Releases
- 31
- License (package)
- BUSL-1.1
- Maintainers
- 1
- Direct dependencies
- 7
- Unpacked size
- 728 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.wundam/orchex at version 1.0.0-rc.11 - lists package npm:@wundam/orchex and repository https://github.com/wundam/orchex - accessed
- npm registry metadata for @wundam/orchex at published version 1.0.0-rc.32, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed