A MCP server for the Ankr Advanced API
Free
Nothing to run from here
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.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
MCP Thin Client for Orchestrator - delegates to REST API
Quickstart
# 1 — run it from where its publisher ships it
npx -y @orchestrator-claude/mcp-server
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> MCP Thin Client for Orchestrator - delegates to REST API
Publishernot claimed
ORAll 1 server
@orchestrator-claude1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add orchestrator-claude-mcp -- npx -y @orchestrator-claude/mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing, so the CLI has to be signed in and the licence has to be on your account — how the login works. Until then the install stops with the price rather than half-writing a config entry.
What it writes
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.
What you approve
73 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
Takes no parameters.
Example callreturns →
Get detailed content about a specific topic
Takes no parameters.
Example callreturns →
Check if the Perplexity API is available
Takes no parameters.
Example callreturns →
Get a summarized overview of a topic with key facts
Takes no parameters.
Example callreturns →
Detect workflow type from user prompt
Takes no parameters.
Example callreturns →
Start a new workflow
Takes no parameters.
Example callreturns →
Advance workflow to next phase
Takes no parameters.
Example callreturns →
Get workflow status
Takes no parameters.
Example callreturns →
Create a git checkpoint for workflow
Takes no parameters.
Example callreturns →
Validate artifact against schema
Takes no parameters.
Example callreturns →
Get next pending action for workflow (Ping-Pong pattern)
Takes no parameters.
Example callreturns →
Set a pending action for workflow
Takes no parameters.
Example callreturns →
Clear pending action for workflow
Takes no parameters.
Example callreturns →
Approve a pending action (e.g., before IMPLEMENT phase)
Takes no parameters.
Example callreturns →
Get workflow metrics
Takes no parameters.
Example callreturns →
Get agent invocation history
Takes no parameters.
Example callreturns →
Start tracking an agent invocation
Takes no parameters.
Example callreturns →
Mark agent invocation as complete
Takes no parameters.
Example callreturns →
Search the knowledge base
Takes no parameters.
Example callreturns →
Get a knowledge base document by slug
Takes no parameters.
Example callreturns →
Get the project constitution (governance document)
Takes no parameters.
Example callreturns →
List all documents in the knowledge base
Takes no parameters.
Example callreturns →
List all hook definitions
Takes no parameters.
Example callreturns →
Get a hook definition by ID
Takes no parameters.
Example callreturns →
Get a hook definition by slug
Takes no parameters.
Example callreturns →
Create a new hook definition
Takes no parameters.
Example callreturns →
Update a hook definition
Takes no parameters.
Example callreturns →
Deprecate (soft delete) a hook definition
Takes no parameters.
Example callreturns →
List all templates, optionally filtered by type and domain
Takes no parameters.
Example callreturns →
Get a template by ID
Takes no parameters.
Example callreturns →
Create a new template
Takes no parameters.
Example callreturns →
Update an existing template
Takes no parameters.
Example callreturns →
Delete a template
Takes no parameters.
Example callreturns →
List all schema definitions
Takes no parameters.
Example callreturns →
Get a schema definition by ID
Takes no parameters.
Example callreturns →
Create a new schema definition
Takes no parameters.
Example callreturns →
Update an existing schema definition
Takes no parameters.
Example callreturns →
Delete a schema definition
Takes no parameters.
Example callreturns →
List all code patterns, optionally filtered by language and framework
Takes no parameters.
Example callreturns →
Get a pattern by ID
Takes no parameters.
Example callreturns →
List all checkpoints, optionally filtered by workflow
Takes no parameters.
Example callreturns →
Get a checkpoint by ID
Takes no parameters.
Example callreturns →
Lists all code-defined workflow type definitions from the in-memory WorkflowModeRegistry (not DB records)
Takes no parameters.
Example callreturns →
Returns a single workflow type definition from the in-memory WorkflowModeRegistry (registry-sourced, not a DB record)
Takes no parameters.
Example callreturns →
Register a new project
Takes no parameters.
Example callreturns →
List all registered projects
Takes no parameters.
Example callreturns →
Get a project by ID
Takes no parameters.
Example callreturns →
Persists the operator
Takes no parameters.
Example callreturns →
List all agent definitions
Takes no parameters.
Example callreturns →
Get an agent definition by name or slug
Takes no parameters.
Example callreturns →
Create a new agent definition
Takes no parameters.
Example callreturns →
Update an existing agent definition
Takes no parameters.
Example callreturns →
Delete an agent definition
Takes no parameters.
Example callreturns →
Create a new skill definition
Takes no parameters.
Example callreturns →
List all skill definitions, optionally filtered by category
Takes no parameters.
Example callreturns →
Get a skill definition by ID
Takes no parameters.
Example callreturns →
Update an existing skill definition
Takes no parameters.
Example callreturns →
Delete a skill definition
Takes no parameters.
Example callreturns →
Create a new knowledge base document
Takes no parameters.
Example callreturns →
Update an existing knowledge base document
Takes no parameters.
Example callreturns →
Delete a knowledge base document
Takes no parameters.
Example callreturns →
Create a new phase on a dynamic workflow (ADR-017 Phase 2)
Takes no parameters.
Example callreturns →
Complete a workflow, transitioning status to completed
Takes no parameters.
Example callreturns →
Store artifact content for a workflow phase
Takes no parameters.
Example callreturns →
Retrieve artifact content for a workflow phase
Takes no parameters.
Example callreturns →
List all versions of an artifact for a workflow phase
Takes no parameters.
Example callreturns →
Verify artifact integrity (checksum validation)
Takes no parameters.
Example callreturns →
Correct artifact content for a past phase (admin-only, bypasses phase gate). Requires correctionReason for audit trail.
Takes no parameters.
Example callreturns →
Add a relationship between two KB documents
Takes no parameters.
Example callreturns →
Get documents related to a specific document via graph traversal
Takes no parameters.
Example callreturns →
Get document graph for visualization
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Validate convention pack content against official documentation via Context7 + semantic comparison. Returns per-section freshness status (fresh/stale/unknown) with confidence scores.
Takes no parameters.
Example callreturns →
Startermost installed
$14 / month
- 11,000 calls a month, included
- 132 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Pro
$44 / month
- 60,000 calls a month, included
- 720 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Scale
$94 / month
- 280,000 calls a month, included
- 3,360 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $14 a month covers every tool at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 99 / 100
Release 3.37.0 · scanned 25 Aug 2026
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.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digestdb6f5fd1deb7c6e3e416d9128534cc9900850685c9aa7646f00c18f411a22b3f
Score vectorthreat 100 → client 99
| 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 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (73 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>".
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.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search | no tags | |
| getTopicContent | no tags | |
| isAvailable | no tags | |
| summarize | no tags | |
| detectWorkflow | no tags | |
| startWorkflow | no tags | |
| advancePhase | no tags | |
| getStatus | no tags | |
| createCheckpoint | no tags | |
| validateArtifact | no tags | |
| getNextAction | no tags | |
| setPendingAction | no tags | |
| clearPendingAction | no tags | |
| approveAction | no tags | |
| getMetrics | no tags | |
| getInvocations | no tags | |
| startAgentInvocation | no tags | |
| completeAgentInvocation | no tags | |
| kbSearch | no tags | |
| kbGetDocument | no tags | |
| kbGetConstitution | no tags | |
| kbListDocuments | no tags | |
| listHooks | no tags | |
| getHook | no tags | |
| getHookBySlug | no tags | |
| createHook | no tags | |
| updateHook | no tags | |
| deprecateHook | no tags | |
| listTemplates | no tags | |
| getTemplateById | no tags | |
| createTemplate | no tags | |
| updateTemplate | no tags | |
| deleteTemplate | no tags | |
| listSchemas | no tags | |
| getSchema | no tags | |
| createSchema | no tags | |
| updateSchema | no tags | |
| deleteSchema | no tags | |
| listPatterns | no tags | |
| getPattern | no tags | |
| listCheckpoints | no tags | |
| getCheckpoint | no tags | |
| listWorkflowDefinitions | no tags | |
| getWorkflowDefinition | no tags | |
| registerProject | no tags | |
| listProjects | no tags | |
| getProject | no tags | |
| selectSessionProject | no tags | |
| listAgentDefinitions | no tags | |
| getAgentDefinition | no tags | |
| createAgentDefinition | no tags | |
| updateAgentDefinition | no tags | |
| deleteAgentDefinition | no tags | |
| createSkillDefinition | no tags | |
| listSkillDefinitions | no tags | |
| getSkillDefinition | no tags | |
| updateSkillDefinition | no tags | |
| deleteSkillDefinition | no tags | |
| createKBDocument | no tags | |
| updateKBDocument | no tags | |
| deleteKBDocument | no tags | |
| createPhase | no tags | |
| completeWorkflow | no tags | |
| artifactStore | no tags | |
| artifactRetrieve | no tags | |
| artifactListVersions | no tags | |
| artifactVerify | no tags | |
| artifactCorrect | no tags | |
| addKBRelationship | no tags | |
| getRelatedDocuments | no tags | |
| getDocumentGraph | no tags | |
| getStackConventions | no tags | |
| validatePackFreshness | 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
Integrityfirst-seen
Surface digestdb6f5fd1deb7c6e3
Scanned2026-08-25
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
Pinned to 3.37.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
3.37.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Orchestrator Claude in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
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 an account with 50 real tool calls against it.