RiskRover MCP
NPM · RISKROVER-MCP-SERVER · SCANNED AUG 23
Draft RiskRover PBS structures and assess automated test evidence against product risks.
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 →
Supply Chain Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency6
- 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
- License check failed: the license (SEE LICENSE IN LICENSE.md) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 11 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified
Unverified: 4 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the RiskRover MCP server?
RiskRover MCP runs locally as an npm package, launched with npx -y riskrover-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · riskrover-mcp-server
claude mcp add be-sure-consulting-riskrover-mcp -- npx -y riskrover-mcp-server
{
"mcpServers": {
"be-sure-consulting-riskrover-mcp": {
"command": "npx",
"args": [
"-y",
"riskrover-mcp-server"
]
}
}
} {
"servers": {
"be-sure-consulting-riskrover-mcp": {
"command": "npx",
"args": [
"-y",
"riskrover-mcp-server"
]
}
}
} codex mcp add be-sure-consulting-riskrover-mcp -- npx -y riskrover-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"be-sure-consulting-riskrover-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"riskrover-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add be-sure-consulting-riskrover-mcp --command npx --arg -y --arg riskrover-mcp-server
mcp_servers:
be-sure-consulting-riskrover-mcp:
command: "npx"
args: ["-y", "riskrover-mcp-server"] {
"McpServers": {
"be-sure-consulting-riskrover-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"riskrover-mcp-server"
]
}
}
} assistant mcp add be-sure-consulting-riskrover-mcp -t stdio -c npx -a -y riskrover-mcp-server
{
"mcpServers": {
"be-sure-consulting-riskrover-mcp": {
"command": "npx",
"args": [
"-y",
"riskrover-mcp-server"
]
}
}
} 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.
- 11 Aug 26 0
- Package version: 0.4.1 → 0.4.4 functional
- Package version: 0.4.1 → 0.4.3 functional
- Package version: 0.4.1 → 0.4.2 functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 31
First indexed and scored.
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 23 Aug 2026 · Analysed npm/riskrover-mcp-server@0.4.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
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.
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the RiskRover MCP server?
RiskRover MCP is listed in the public MCP registry as io.github.Be-Sure-Consulting/riskrover-mcp. Draft RiskRover PBS structures and assess automated test evidence against product risks. This page covers its npm package (riskrover-mcp-server).
Is the RiskRover MCP server safe to use?
RiskRover MCP scores 31 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 August 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.
Is the RiskRover MCP server still maintained?
RiskRover MCP is still listed as active in the MCP registry. We last reached this channel on 23 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.