Validate Formhaus form definitions and simulate multi-step paths against the real engine.
Orchestrator Claude is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
MCP Thin Client for Orchestrator - delegates to REST API
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user orchestrator-claude-mcp '--' npx -y @orchestrator-claude/mcp-server
# 2 — ask your agent for something these tools do
# search, getTopicContent, isAvailable and 72 more
Orchestrator Claude costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Orchestrator Claude as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user orchestrator-claude-mcp '--' npx -y @orchestrator-claude/mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
75 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search for information using Perplexity AI
No parameter schema on file.
Get detailed content about a specific topic
No parameter schema on file.
Check if the Perplexity API is available
No parameter schema on file.
Get a summarized overview of a topic with key facts
No parameter schema on file.
Detect workflow type from user prompt
No parameter schema on file.
Start a new workflow
No parameter schema on file.
Advance workflow to next phase
No parameter schema on file.
Get workflow status
No parameter schema on file.
Create a git checkpoint for workflow
No parameter schema on file.
Validate artifact against schema
No parameter schema on file.
Get next pending action for workflow (Ping-Pong pattern)
No parameter schema on file.
Set a pending action for workflow
No parameter schema on file.
Clear pending action for workflow
No parameter schema on file.
Approve a pending action (e.g., before IMPLEMENT phase)
No parameter schema on file.
Get workflow metrics
No parameter schema on file.
Get agent invocation history
No parameter schema on file.
Start tracking an agent invocation
No parameter schema on file.
Mark agent invocation as complete
No parameter schema on file.
Search the knowledge base
No parameter schema on file.
Get a knowledge base document by slug
No parameter schema on file.
Get the project constitution (governance document)
No parameter schema on file.
List all documents in the knowledge base
No parameter schema on file.
List all hook definitions
No parameter schema on file.
Get a hook definition by ID
No parameter schema on file.
Get a hook definition by slug
No parameter schema on file.
Create a new hook definition
No parameter schema on file.
Update a hook definition
No parameter schema on file.
Deprecate (soft delete) a hook definition
No parameter schema on file.
List all templates, optionally filtered by type and domain
No parameter schema on file.
Get a template by ID
No parameter schema on file.
Create a new template
No parameter schema on file.
Update an existing template
No parameter schema on file.
Delete a template
No parameter schema on file.
List all schema definitions
No parameter schema on file.
Get a schema definition by ID
No parameter schema on file.
Create a new schema definition
No parameter schema on file.
Update an existing schema definition
No parameter schema on file.
Delete a schema definition
No parameter schema on file.
List all code patterns, optionally filtered by language and framework
No parameter schema on file.
Get a pattern by ID
No parameter schema on file.
List all checkpoints, optionally filtered by workflow
No parameter schema on file.
Get a checkpoint by ID
No parameter schema on file.
Lists all code-defined workflow type definitions from the in-memory WorkflowModeRegistry (not DB records)
No parameter schema on file.
Returns a single workflow type definition from the in-memory WorkflowModeRegistry (registry-sourced, not a DB record)
No parameter schema on file.
Register a new project
No parameter schema on file.
List all registered projects
No parameter schema on file.
Get a project by ID
No parameter schema on file.
Persists the operator
No parameter schema on file.
List all agent definitions
No parameter schema on file.
Get an agent definition by name or slug
No parameter schema on file.
Create a new agent definition
No parameter schema on file.
Update an existing agent definition
No parameter schema on file.
Delete an agent definition
No parameter schema on file.
Create a new skill definition
No parameter schema on file.
List all skill definitions, optionally filtered by category
No parameter schema on file.
Get a skill definition by ID
No parameter schema on file.
Update an existing skill definition
No parameter schema on file.
Delete a skill definition
No parameter schema on file.
Create a new knowledge base document
No parameter schema on file.
Update an existing knowledge base document
No parameter schema on file.
Delete a knowledge base document
No parameter schema on file.
Create a new phase on a dynamic workflow (ADR-017 Phase 2)
No parameter schema on file.
Complete a workflow, transitioning status to completed
No parameter schema on file.
Store artifact content for a workflow phase
No parameter schema on file.
Retrieve artifact content for a workflow phase
No parameter schema on file.
List all versions of an artifact for a workflow phase
No parameter schema on file.
Verify artifact integrity (checksum validation)
No parameter schema on file.
Correct artifact content for a past phase (admin-only, bypasses phase gate). Requires correctionReason for audit trail.
No parameter schema on file.
Add a relationship between two KB documents
No parameter schema on file.
Get documents related to a specific document via graph traversal
No parameter schema on file.
Get document graph for visualization
No parameter schema on file.
Get detailed stack conventions for the current project from the Vault KB. Use when baseline context is insufficient — e.g. when you need framework-specific patterns for testing, routing, or error handling.
No parameter schema on file.
Validate convention pack content against official documentation via Context7 + semantic comparison. Returns per-section freshness status (fresh/stale/unknown) with confidence scores.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Orchestrator Claude or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (70 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
57 of the 70 recovered tools are registered only when toolSet === 'core' || toolSet === 'all' holds (dist/handlers/index.js:704) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 4.
9 of the 70 recovered tools are registered only when toolSet === 'extended' || toolSet === 'all' holds (dist/handlers/index.js:707) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 4.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
4 tools are registered unconditionally · (1) 57 more only when toolSet === 'core' || toolSet === 'all' holds (dist/handlers/index.js:704) · (2) 9 more only when toolSet === 'extended' || toolSet === 'all' holds (dist/handlers/index.js:707) — typically when a key or option is configured. All 70 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search | no tags | |
| getTopicContent | no tags | |
| isAvailable | no tags | |
| summarize | no tags | |
| detectWorkflow conditional (1) | no tags | |
| startWorkflow conditional (1) | no tags | |
| advancePhase conditional (1) | no tags | |
| getStatus conditional (1) | no tags | |
| createCheckpoint conditional (1) | no tags | |
| validateArtifact conditional (1) | no tags | |
| getNextAction conditional (1) | no tags | |
| setPendingAction conditional (1) | no tags | |
| clearPendingAction conditional (1) | no tags | |
| approveAction conditional (1) | no tags | |
| getMetrics conditional (1) | no tags | |
| getInvocations conditional (1) | no tags | |
| startAgentInvocation conditional (1) | no tags | |
| completeAgentInvocation conditional (1) | no tags | |
| kbGetDocument conditional (1) | no tags | |
| kbGetConstitution conditional (1) | no tags | |
| listHooks conditional (1) | no tags | |
| getHook conditional (1) | no tags | |
| getHookBySlug conditional (1) | no tags | |
| createHook conditional (1) | no tags | |
| updateHook conditional (1) | no tags | |
| deprecateHook conditional (1) | no tags | |
| listTemplates conditional (1) | no tags | |
| getTemplateById conditional (1) | no tags | |
| createTemplate conditional (1) | no tags | |
| updateTemplate conditional (1) | no tags | |
| deleteTemplate conditional (1) | no tags | |
| listSchemas conditional (1) | no tags | |
| getSchema conditional (1) | no tags | |
| createSchema conditional (1) | no tags | |
| updateSchema conditional (1) | no tags | |
| deleteSchema conditional (1) | no tags | |
| listPatterns conditional (1) | no tags | |
| getPattern conditional (1) | no tags | |
| listCheckpoints conditional (1) | no tags | |
| getCheckpoint conditional (1) | no tags | |
| listWorkflowDefinitions conditional (1) | no tags | |
| getWorkflowDefinition conditional (1) | no tags | |
| registerProject conditional (1) | no tags | |
| updateProject conditional (1) | no tags | |
| listProjects conditional (1) | no tags | |
| getProject conditional (1) | no tags | |
| selectSessionProject conditional (1) | no tags | |
| listAgentDefinitions conditional (1) | no tags | |
| getAgentDefinition conditional (1) | no tags | |
| createAgentDefinition conditional (1) | no tags | |
| updateAgentDefinition conditional (1) | no tags | |
| deleteAgentDefinition conditional (1) | no tags | |
| createSkillDefinition conditional (1) | no tags | |
| listSkillDefinitions conditional (1) | no tags | |
| getSkillDefinition conditional (1) | no tags | |
| updateSkillDefinition conditional (1) | no tags | |
| deleteSkillDefinition conditional (1) | no tags | |
| createKBDocument conditional (1) | no tags | |
| updateKBDocument conditional (1) | no tags | |
| deleteKBDocument conditional (1) | no tags | |
| vaultGraphQuery conditional (1) | no tags | |
| createPhase conditional (2) | no tags | |
| completeWorkflow conditional (2) | no tags | |
| artifactStore conditional (2) | no tags | |
| artifactRetrieve conditional (2) | no tags | |
| artifactListVersions conditional (2) | no tags | |
| artifactVerify conditional (2) | no tags | |
| artifactCorrect conditional (2) | no tags | |
| getStackConventions conditional (2) | no tags | |
| validatePackFreshness conditional (2) | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 3.44.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Orchestrator Claude can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.