io.github.rupinder2/mcp-orchestrator
PYPI · MCP-ORCHESTRATOR · SCANNED SEP 20
Aggregates tools from multiple MCP servers with unified BM25/regex search and deferred loading.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 3 of 47 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 206 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 248 tokens (~124/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.rupinder2/mcp-orchestrator server?
io.github.rupinder2/mcp-orchestrator runs locally as a PyPI package, launched with uvx mcp-orchestrator. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-orchestrator
claude mcp add rupinder2-mcp-orchestrator -- uvx mcp-orchestrator
{
"mcpServers": {
"rupinder2-mcp-orchestrator": {
"command": "uvx",
"args": [
"mcp-orchestrator"
]
}
}
} {
"servers": {
"rupinder2-mcp-orchestrator": {
"command": "uvx",
"args": [
"mcp-orchestrator"
]
}
}
} codex mcp add rupinder2-mcp-orchestrator -- uvx mcp-orchestrator
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rupinder2-mcp-orchestrator": {
"type": "local",
"command": [
"uvx",
"mcp-orchestrator"
],
"enabled": true
}
}
} openclaw mcp add rupinder2-mcp-orchestrator --command uvx --arg mcp-orchestrator
mcp_servers:
rupinder2-mcp-orchestrator:
command: "uvx"
args: ["mcp-orchestrator"] {
"McpServers": {
"rupinder2-mcp-orchestrator": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcp-orchestrator"
]
}
}
} assistant mcp add rupinder2-mcp-orchestrator -t stdio -c uvx -a mcp-orchestrator
{
"mcpServers": {
"rupinder2-mcp-orchestrator": {
"command": "uvx",
"args": [
"mcp-orchestrator"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 19 Sept 26 −2
- Stability: pass → 0.83 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 16 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +13
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/mcp-orchestrator@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 47 packages
| Packages resolved | 47 |
|---|---|
| Stale | 2 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
call_remote_tool Call Remote Tool ~115
Call a tool directly on a registered remote MCP server through the orchestrator. This tool allows direct invocation of any tool on a downstream MCP server. The tool name should be in the format 'server_name__tool_name' (e.g., 'context7__query-docs').
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | – | – | Tool arguments as a dictionary (optional) |
| auth_header | – | – | Optional auth header to use for this call (overrides registered auth) |
| tool_name | string | yes | Full tool name in format 'server_name__tool_name' |
No output schema declared.
No examples provided.
tool_search Tool Search ~133
Search for tools using BM25 relevance ranking or regex pattern matching. Searches across tool names, descriptions, and argument names/descriptions. By default, uses BM25 natural language search. Set use_regex=True to search using Python regex patterns instead. Returns tool_reference blocks for discovered tools with deferred loading.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | Maximum number of results (1-10, default 3) |
| query | string | yes | Natural language query (BM25) or regex pattern (if use_regex=True) |
| use_regex | boolean | – | If True, treat query as regex pattern; otherwise use BM25 search |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.rupinder2/mcp-orchestrator server?
io.github.rupinder2/mcp-orchestrator is listed in the public MCP registry as io.github.rupinder2/mcp-orchestrator. Aggregates tools from multiple MCP servers with unified BM25/regex search and deferred loading. This page covers its PyPI package (mcp-orchestrator).
Is the io.github.rupinder2/mcp-orchestrator server safe to use?
io.github.rupinder2/mcp-orchestrator scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.rupinder2/mcp-orchestrator server expose?
io.github.rupinder2/mcp-orchestrator exposes 2 tools: tool_search, call_remote_tool. Their descriptions and schemas cost roughly 248 tokens of context every time the server is loaded.
Is the io.github.rupinder2/mcp-orchestrator server still maintained?
io.github.rupinder2/mcp-orchestrator is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.rupinder2/mcp-orchestrator server under?
io.github.rupinder2/mcp-orchestrator declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.