OrcaRouter
NPM · @ORCAROUTER/MCP · SCANNED SEP 26
Browse 160+ LLM models and live pricing — no API key needed for catalog. Add key to route chat.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 122 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 802 tokens (~200/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the OrcaRouter MCP server?
OrcaRouter runs locally as an npm package, launched with npx -y @orcarouter/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @orcarouter/mcp
claude mcp add continuum-ai-corp-orcarouter-mcp -- npx -y @orcarouter/mcp
{
"mcpServers": {
"continuum-ai-corp-orcarouter-mcp": {
"command": "npx",
"args": [
"-y",
"@orcarouter/mcp"
]
}
}
} {
"servers": {
"continuum-ai-corp-orcarouter-mcp": {
"command": "npx",
"args": [
"-y",
"@orcarouter/mcp"
]
}
}
} codex mcp add continuum-ai-corp-orcarouter-mcp -- npx -y @orcarouter/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"continuum-ai-corp-orcarouter-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@orcarouter/mcp"
],
"enabled": true
}
}
} openclaw mcp add continuum-ai-corp-orcarouter-mcp --command npx --arg -y --arg @orcarouter/mcp
mcp_servers:
continuum-ai-corp-orcarouter-mcp:
command: "npx"
args: ["-y", "@orcarouter/mcp"] {
"McpServers": {
"continuum-ai-corp-orcarouter-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@orcarouter/mcp"
]
}
}
} assistant mcp add continuum-ai-corp-orcarouter-mcp -t stdio -c npx -a -y @orcarouter/mcp
{
"mcpServers": {
"continuum-ai-corp-orcarouter-mcp": {
"command": "npx",
"args": [
"-y",
"@orcarouter/mcp"
]
}
}
} 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.
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 −3
- Stability: pass → 0.83 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
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 26 Sept 2026 · Analysed npm/@orcarouter/mcp@1.1.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
orcarouter_chat ~337
Send a single-turn chat request to OrcaRouter and return the assistant's response text. Default model is the workspace's auto-router. Use `orcarouter/<name>` for other routers or `<provider>/<model>` for direct calls. For OpenAI reasoning models (gpt-5/o1/o3/...), max_tokens is automatically routed to max_completion_tokens at the wire level. The optional `models` array sets a fallback chain — the primary `model` is tried first, then each entry on failure (5 entries total max, including the primary). Errors are returned as text content with isError:true; common cases include missing API key, rate limits, and upstream provider outages. Requires ORCAROUTER_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | integer | – | Maximum tokens to generate (default 10000). Automatically translated to max_completion_tokens for OpenAI reasoning models. |
| model | string | – | Model to call. Defaults to `orcarouter/auto` — your workspace's seeded auto-router. Use `orcarouter/<name>` for other workspace routers, or `<provider>/<model>` for direct upstream selection (e.g. `o… |
| models | array | – | Optional fallback chain. Models are tried in order if the primary fails. Max 5 entries including the primary. |
| prompt | string | yes | User message to send (single-turn). |
| system_prompt | string | – | Optional system prompt prepended to the conversation. |
| temperature | number | – | Sampling temperature (default 0.7). |
No output schema declared.
No examples provided.
orcarouter_model_card ~170
Get detailed information about a single model — display name, long description, pricing (per-call and per-million tokens), context window, max output, modalities (input/output), supported endpoints, latency percentiles (p50/p95), and release date. Use this when you already know the model id and want full details; for browsing or filtering across many models use orcarouter_models_list instead. Returns isError:true with a clear hint when the id is not found. Read-only, no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | Model ref in `provider/slug` form (e.g. `openai/gpt-4o-mini`, `anthropic/claude-haiku-4.5`). Use the exact `id` value returned by orcarouter_models_list. |
No output schema declared.
No examples provided.
orcarouter_models_list ~179
List LLM models in the OrcaRouter catalog. Each entry includes id, name, description, owned_by, context_length, supported_endpoint_types, and pricing (both per-token and per-million tokens). Filter by `provider`, `capability`, or `min_context` — filters compose (all conditions must match) and are applied server-side. Discover valid provider ids first with orcarouter_providers_list. Returns the full catalog when called without filters. Read-only, no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | Filter to models supporting this capability. |
| min_context | integer | – | Filter to models with context window at least this large (tokens). |
| provider | string | – | Provider id (lowercase, e.g. 'openai', 'anthropic'). Get the full list via orcarouter_providers_list. |
No output schema declared.
No examples provided.
orcarouter_providers_list ~116
List all model providers on OrcaRouter with their `provider_id`, human-readable `display_name`, `icon_url`, and `model_count`. Call this first to discover valid provider ids (e.g. 'openai', 'anthropic', 'google', 'qwen', 'deepseek') which you can then pass to orcarouter_models_list as the `provider` filter. Takes no parameters and returns the same list on every call until the deployment's catalog changes. Read-only, no API key required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the OrcaRouter MCP server?
OrcaRouter is an MCP server listed in the public MCP registry as io.github.Continuum-AI-Corp/orcarouter-mcp. Browse 160+ LLM models and live pricing, no API key needed for catalog. Add key to route chat. This page covers its npm package (@orcarouter/mcp).
Is the OrcaRouter MCP server safe to use?
OrcaRouter scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. 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 OrcaRouter MCP server expose?
OrcaRouter exposes 4 tools: orcarouter_chat, orcarouter_models_list, orcarouter_model_card, orcarouter_providers_list. Their descriptions and schemas cost roughly 802 tokens of context every time the server is loaded.
Is the OrcaRouter MCP server still maintained?
OrcaRouter is still listed as active in the MCP registry. We last reached this channel on 26 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 OrcaRouter MCP server under?
OrcaRouter declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.