Developer · Local MCP server

RiskRover MCP

Draft risk-based test plans and assess automated test coverage against product risks with RiskRover.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.Be-Sure-Consulting/riskrover-mcp
Version
0.9.0
Status
Active
Category
developer
Transport
stdio (local process)
Package
npm
Published
2026-09-30
Updated
2026-09-30
Publisher
Be-Sure-Consulting (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/Be-Sure-Consulting) · how
Repository
github.com/Be-Sure-Consulting/riskrover-mcp
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
npmriskrover-mcp-server0.9.0stdioRISKROVER_API_TOKEN (required, secret), RISKROVER_PROJECT_ID

How to connect RiskRover MCP

RiskRover MCP runs locally from a Node.js package published to the npm registry: riskrover-mcp-server version 0.9.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y riskrover-mcp-server@0.9.0. It reads these environment variables: RISKROVER_API_TOKEN (required, secret) and RISKROVER_PROJECT_ID; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "riskrover-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "riskrover-mcp-server@0.9.0"
      ],
      "env": {
        "RISKROVER_API_TOKEN": "<secret>",
        "RISKROVER_PROJECT_ID": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
RideDesk Developer DocsDeveloper docs for building on RideDesk: booking API, widgets, per-account booking MCP. No auth.Remote · HTTPLive check: ✓ handshakeridedesk.app
Rigor MCPVerified statistical inference for AI agents: hypothesis tests, sequential testing, power.Local · stdioPyPI: rigor-mcp
RigourQuality gates for AI agents. Lint, test, build checks with memory persistence.Local · stdionpm: @rigour-labs/mcp
RIPE AtlasRIPE Atlas network measurements - ping, traceroute, DNS, TLS, HTTP, NTP, and probes.Local · stdionpm: ripe-atlas-mcp-server
RivetManage Rivet Cloud namespaces and actors, run Code Mode, and open the Rivet Actor Inspector.Remote & Local · HTTP, stdioLive check: sign-in requiredmcp.rivet.dev
rlayShared channels where agents from different vendors collaborate over a relayed message log.Remote · HTTPLive check: sign-in requiredrlay.dev
Rlg MCPMCP server exposing rlg log streams to LLM agents via JSON-RPC 2.0 over stdio.Local · stdioOCI image (Docker): ghcr.io/sebastienrousseau/rlg-mcp:0.0.14
RLM ToolsPersistent Python sandbox for token-efficient codebase exploration in MCP clients.Local · stdioPyPI: rlm-tools