RiskRover MCP

io.github.Be-Sure-ConsultingPublished by GitHub account Be-Sure-Consultingv0.9.0Updated Oct 27, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

Local MCP server that connects an assistant to RiskRover to draft risk-based test plans and assess automated test coverage against product risks.

What you can do
  • Draft risk-based test plans in RiskRover
  • Assess automated test coverage against product risks
  • Work within a chosen RiskRover project, set by default or per request
  • Submit reviewed results when the API token has read-and-write scope
When to use it
Useful when a team already uses RiskRover and wants an assistant to help draft risk-based test plans or evaluate how well automated tests cover identified product risks, without leaving the chat.
Requirements
Runs as a local process over stdio, installed from the npm package riskrover-mcp-server (Node.js). Needs a RiskRover API token in the RISKROVER_API_TOKEN environment variable; read-only scope suffices for assessment and drafting, read-and-write scope is needed for reviewed submissions. An optional default project can be set with RISKROVER_PROJECT_ID or passed per request. Network access to RiskRover is required.
Before you install
The API token is a secret stored in an environment variable; a read-and-write token allows the assistant to submit reviewed data to RiskRover, so prefer read-only scope unless submissions are intended. Test plans and coverage assessments are sent to RiskRover's service.

Installation

In SourceWeft

  1. Open RiskRover MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.9.0LatestSep 30, 2026
  2. v0.8.0Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.