Rocro
Easy-to-configure load testing tool that performs load tests in a cost-effective and scalable way. Sets up load test environment automatically. No capacity planning required. Ultra large capacity load testing is also possible.
https://rocro.com/Connect straight to this server’s public endpoint.
https://mcp.rocro.com/We add this server to your workspace, walk through sign-in once, then open Studio with tools ready to run.
Last probed Sep 14, 2026 · mcp.rocro.com
11tools discovered
Get Issues
Retrieve issues detected by Inspecode analysis for a specific job or the latest successful job on a branch. This tool returns Static Analysis Results Interchange Format (SARIF) compatible issue data including: - Code quality issues (errors, warnings, info) - Security vulnerabilities - License compliance issues - Maintainability metrics API Endpoint: GET /jobs/{domain}/{org}/{repo}/{jobId}/issues Requires: Read permission or above for the repository Input rules: - Specify exactly one of jobId
List Jobs
List analysis jobs for a repository with comprehensive filtering options. This tool is essential for finding specific jobs, especially when working with branch-based workflows. Use this tool to identify the latest job on a specific branch before retrieving issues. API Endpoint: GET /jobs/{domain}/{org}/{repo} Requires: Read permission or above for the repository Key Features: - Returns up to 40 most recent jobs per request - Supports pagination with 'before' parameter - Comprehensive filterin
Get Job Status
Get the current execution status of a specific Inspecode analysis job. API Endpoint: GET /jobs/{domain}/{org}/{repo}/{jobId}/status Requires: Read permission or above for the repository Returns detailed status information including: - Overall job status (pending, running, succeeded, failed, etc.) - Individual task and tool execution status - Progress indicators for long-running jobs Use the 'details=true' query parameter to get granular task/tool status breakdown. This is particularly useful
Get Log
Retrieve execution logs for an analysis tool or a custom task. The target is selected by exactly one of 'tool' or 'taskId': - When 'tool' is provided: fetch the analysis tool's log. API Endpoint: GET /jobs/{domain}/{org}/{repo}/{jobId}/tools/{tool}/{index}/log Tool logs contain execution output and errors, performance metrics and timing, configuration details and parameters, and exit codes. - When 'taskId' is provided: fetch the custom task's log. API Endpoint: GET /jobs/{domain}/{org}/
List Repositories
List all repositories registered with Inspecode for an organization. API Endpoint: GET /orgs/{domain}/{org}/repos Requires: Read permission or above for the target repositories Returns a list of repository names that: - Are registered with Inspecode - You have access permissions for - Belong to the specified organization Use this tool to discover available repositories before performing analysis operations.
List Branches
List all branches currently being watched for automatic analysis. API Endpoint: GET /orgs/{domain}/{org}/repos/{repo}/branches Requires: Read permission or above for the repository Returns an array of branch names that are configured for: - Automatic analysis on push events - Pull request analysis - Scheduled analysis jobs Use this tool to understand the current branch watching configuration before modifying it.
List Artifacts
List all artifacts (output files) generated during analysis job execution. API Endpoint: GET /jobs/{domain}/{org}/{repo}/{jobId}/artifacts Requires: Read permission or above for the repository Artifacts include: - Tool-generated reports (JSON, XML, HTML) - Code coverage reports - Security scan results - Custom task outputs - Build artifacts from Docker tasks Use download URLs to retrieve specific artifact files. Artifacts are organized by tool/task name and execution index for multi-configura
Get File Analysis
Retrieve comprehensive file-level metrics and analysis results. API Endpoint: GET /jobs/{domain}/{org}/{repo}/{jobId}/files Requires: Read permission or above for the repository Provides detailed metrics for each analyzed file: - Code quality grade (A-F rating) - Lines of code (logical and physical) - Cyclomatic complexity (total and maximum) - Method/function count - Issue count per file Filtering and sorting options: - Filter by programming language - Filter by quality grade - Filter by fil
Get Licenses
Retrieve Open Source Software (OSS) license analysis results. API Endpoint: GET /jobs/{domain}/{org}/{repo}/{jobId}/licenses Requires: Read permission or above for the repository Analyzes and reports: - Detected licenses in dependencies and source files - License compatibility and risk assessment - Copyleft license identification - SPDX license identifier mapping - Component-level and file-level license detection License risk levels: - Low: Permissive licenses (MIT, Apache, BSD) - Medium: Wea
List Secrets
List secrets available for analysis jobs. The scope is selected by the optional 'repo' argument: - When 'repo' is provided: list repository-level secrets. API Endpoint: GET /orgs/{domain}/{org}/repos/{repo}/secrets Requires: Read permission or above for the repository. Repository secrets are only available to jobs for that repository and override organization-level secrets with the same name. - When 'repo' is omitted: list organization-level secrets. API Endpoint: GET /orgs/{domain}/{
List Schedules
List all configured scheduled analysis jobs for a repository. API Endpoint: GET /orgs/{domain}/{org}/repos/{repo}/schedules Requires: Read permission or above for the repository Returns schedule configuration including: - Target branch for scheduled analysis - Schedule frequency (daily, weekly, monthly) - Execution time (hour, minute in UTC) - Day specification (day of month or day of week) - Timezone information Scheduled jobs are useful for: - Regular security scanning - Periodic code quali
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Directory coverage for brandsEasy-to-configure load testing tool that performs load tests in a cost-effective and scalable way. Sets up load test environment automatically. No capacity planning required. Ultra large capacity load testing is also possible.
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
Operate Rocro? Verify ownership to take over this directory entry.
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles probed 11 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
Rocro may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
MCPBundles is an independent platform built on the open Model Context Protocol standard. Not affiliated with Anthropic PBC or Claude.