@likhithreddy/nexus
npm
v0.3.0
Source verified
Published by likhithreddy — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Nexus — an MCP aggregator with a memory layer.
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 − 6.3 = 94. 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 |
2. Client adoption risk — 94 − 6 = 88. 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 |
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 (`dist/index.js:10`): 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: ; import { exec } from "child_process"; import { existsSync } from "fs"; import { StdioServerTransport } from "@modelcon
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 dist/index.js
In the server's implementation (`dist/index.js:2077`): 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: .platform === "darwin") exec(`open ${url}`); else if (process.platform === "linux") exec(`xdg-open ${url} 2>/dev/nul
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 dist/index.js
Each tool and what it can reach — statically extracted from the published source.
example-remoteno sensitive capabilityfilesystemno sensitive capabilitygithubno sensitive capabilitymemoryno sensitive capabilitynexus.graphno sensitive capabilitynexus.memory_forgetno sensitive capabilitynexus.memory_listno sensitive capabilitynexus.memory_statsno sensitive capabilitysequential-thinkingno 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 |
|---|---|---|---|---|
v0.3.0 latest |
B 88/100 | 2 | 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 @likhithreddy/nexus --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 10 side by side →
Nexus MCP server - Intelligent AI model search and discovery with OpenRouter integration
MCP client server for Createve.AI Nexus API
Distributed impact analysis MCP. Analyzes code changes, propagates dependencies, generates docs and detects technical debt.
MCP server for the Gatewarden Nexus platform — mediation layer between local agent runtimes and the Nexus HTTP API
Nexus AI Agent MCP Server — domain-specific tools for a decentralized AI dataset marketplace on Sui + Walrus
KR: Nexus Repository Manager 3 API 연동 MCP 서버. EN: MCP server for Nexus Repository Manager 3 operations over stdio and Streamable HTTP.
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.