Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Robot Resources Router

NPM · @ROBOT-RESOURCES/ROUTER-MCP · SCANNED SEP 20

Intelligent LLM routing proxy — 60-90% cost savings by auto-selecting the cheapest model

0 this week 78 Trust /100
Trust breakdown (7 categories)

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 & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • 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 166 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 439 tokens (~109/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 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 (100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.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
Install

How do I install the Robot Resources Router MCP server?

Robot Resources Router runs locally as an npm package, launched with npx -y @robot-resources/router-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 · @robot-resources/router-mcp

# add to Claude Code
claude mcp add robot-resources-router -- npx -y @robot-resources/router-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "robot-resources-router": {
      "command": "npx",
      "args": [
        "-y",
        "@robot-resources/router-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "robot-resources-router": {
      "command": "npx",
      "args": [
        "-y",
        "@robot-resources/router-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add robot-resources-router -- npx -y @robot-resources/router-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "robot-resources-router": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@robot-resources/router-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add robot-resources-router --command npx --arg -y --arg @robot-resources/router-mcp
# ~/.hermes/config.yaml
mcp_servers:
  robot-resources-router:
    command: "npx"
    args: ["-y", "@robot-resources/router-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "robot-resources-router": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@robot-resources/router-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add robot-resources-router -t stdio -c npx -a -y @robot-resources/router-mcp
// mcp.json
{
  "mcpServers": {
    "robot-resources-router": {
      "command": "npx",
      "args": [
        "-y",
        "@robot-resources/router-mcp"
      ]
    }
  }
}
Changelog

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.

  • 19 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.

  • 17 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 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.

  • 10 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 npm/@robot-resources/router-mcp@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 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 →

MCP tools · 4 exposed · ~439 tokens

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 →

Tool Tokens
router_compare_models ~110

Compare available LLM models for a specific task type. Returns all models ranked by cost with capability scores, savings vs baseline, and a recommendation for the cheapest model that meets the capability threshold.

NameTypeReqDescription
providerstringFilter by provider (openai, anthropic, google)
task_typestringyesTask type to compare models for
thresholdnumberMinimum capability score (0.0–1.0). Models below this are still shown but marked as not meeting threshold
NameTypeReqDescription
baseline_modelstringyes
capable_modelsnumberyes
modelsarrayyes
recommendedyes
task_typestringyes
thresholdnumberyes
total_modelsnumberyes

No examples provided.

router_get_config ~48

Get the current Router routing configuration. Returns effective config (env-var defaults merged with any runtime overrides). Shows provider_scope, capability_threshold, baseline_model, log_level, and which fields are overridden.

Input schema present but exposes no named parameters.

NameTypeReqDescription
baseline_modelstringyes
capability_thresholdnumberyes
log_levelstringyes
overridesarrayyes
provider_scopestringyes

No examples provided.

router_get_stats ~109

Get routing cost savings statistics from Robot Resources Router. Shows how much money has been saved by intelligent model routing, with breakdowns by task type and provider.

NameTypeReqDescription
periodstringTime period for stats: weekly (7 days), monthly (30 days), or all time
providerstringFilter by provider (openai, anthropic, google)
task_typestringFilter by task type (coding, reasoning, analysis, simple_qa, creative, general)
NameTypeReqDescription
average_savings_per_requestnumberyes
breakdown_by_providerobjectyes
breakdown_by_task_typeobjectyes
periodstringyes
total_cost_actualnumberyes
total_cost_baselinenumberyes
total_cost_savednumberyes
total_requestsnumberyes

No examples provided.

router_set_config ~172

Update Router routing configuration at runtime. Only provide fields you want to change — other fields keep their current values. Send null for a field to reset it to the env-var default. Overrides are in-memory only and cleared on proxy restart.

NameTypeReqDescription
baseline_modelstring|nullBaseline model for savings comparison (e.g., gpt-4o). Must exist in models database. Send null to reset to default.
capability_thresholdMinimum capability score for model selection (0.0–1.0). Lower = cheaper but less capable. Send null to reset to default.
log_levelLogging verbosity level. Send null to reset to default.
provider_scopeProvider scope for routing. "all" uses all providers, or restrict to one. Send null to reset to default.
NameTypeReqDescription
baseline_modelstringyes
capability_thresholdnumberyes
log_levelstringyes
overridesarrayyes
provider_scopestringyes

No examples provided.

Common questions

What is the Robot Resources Router MCP server?

Robot Resources Router is an MCP server listed in the public MCP registry as io.github.robot-resources/router. Intelligent LLM routing proxy, 60-90% cost savings by auto-selecting the cheapest model. This page covers its npm package (@robot-resources/router-mcp).

Is the Robot Resources Router MCP server safe to use?

Robot Resources Router scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 Robot Resources Router MCP server expose?

Robot Resources Router exposes 4 tools: router_get_stats, router_compare_models, router_get_config, router_set_config. Their descriptions and schemas cost roughly 439 tokens of context every time the server is loaded.

Is the Robot Resources Router MCP server still maintained?

Robot Resources Router 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 Robot Resources Router MCP server under?

Robot Resources Router declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.