@physics91/openrouter-mcp
npm
v1.3.1
Published by @physics91 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
A Model Context Protocol (MCP) server for OpenRouter API with Collective Intelligence - Multi-model consensus, ensemble reasoning, and collaborative problem solving
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 7.5 = 93. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Untrusted input concatenated into a command sink MTC-SRC-009 | injection |
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 93 − 7 = 86. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In the server's implementation (`bin/check-python.js:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: st { spawn } = require('child_process'); const chalk = require('chalk'); function checkPython() { return new Prom
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server bin/check-python.js
In the server's implementation (`bin/openrouter-mcp.js:5`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: st { spawn } = require('child_process'); const fs = require('fs'); const path = require('path'); const os = require('
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server bin/openrouter-mcp.js
In the server's implementation (`bin/secure-credentials.js:230`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: { execSync } = require('child_process'); const username = process.env.USERNAME; // Remove inheritance an
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server bin/secure-credentials.js
In the server's implementation (`bin/secure-credentials.js:235`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: r try { execSync(`icacls "${filePath}" /inheritance:r /grant:r "${username}:F"`, { stdio: 'pi
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server bin/secure-credentials.js
"@physics91/openrouter-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: node bin/check-python.js
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package @physics91/openrouter-mcp
Each tool and what it can reach — statically extracted from the published source.
adaptive_model_selectionno sensitive capabilitybenchmark_modelsno sensitive capabilitychat_with_modelno sensitive capabilitychat_with_visionno sensitive capabilitycollaborative_problem_solvingno sensitive capabilitycollective_chat_completionno sensitive capabilitycompare_model_categoriesno sensitive capabilitycompare_model_performanceno sensitive capabilitycross_model_validationno sensitive capabilityensemble_reasoningno sensitive capabilityexport_benchmark_reportno sensitive capabilityget_benchmark_historyno sensitive capabilityget_usage_statsno sensitive capabilitylist_available_modelsno sensitive capabilitylist_vision_modelsno sensitive capabilitymy_toolno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.3.1 latest |
B 86/100 | 5 | 1.13.0 | 2026-09-07 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @physics91/openrouter-mcp --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →
MCP server for consulting AI models via OpenRouter
MCP server providing access to OpenRouter's unified API for 500+ AI models
OpenRouter Models MCP.
MCP server for OpenRouter model discovery
FDA device & vehicle recall risk for AI agents: recall history, MAUDE trend, risk score.
Open-source MCP server exposing Agent402.Tools' catalog — 500+ strong: 400+ self-hostable tools + 100 multi-tool skill packs (security-audit, trend-analysis, structured-scrape, decode-blob, forecasting-bake-off) for AI agents — browser, web search & answe
Zero-dependency MCP server that gives AI agents a self-updating project memory in AGENTS.md. Returns merge instructions instead of mutating state, so every change is a reviewable diff.
MCP Apps UI resources and server helpers for n8n
MCP server providing comprehensive access to BookStack knowledge management system
MCP server for tracking achievements with STAR methodology