onsecurity-mcp-server

onsecurity/onsecurity-mcp-server

3.2

If you are the rightful owner of onsecurity-mcp-server and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

The OnSecurity MCP server is designed to integrate with the OnSecurity API, enabling seamless interaction with security assessment data through Claude.

Tools

  1. get-rounds

    Retrieve information about security assessment rounds.

  2. get-findings

    Access detailed findings from security assessments.

  3. get-blocks

    Get information on any blocks or issues in assessments.

  4. get-notifications

    Receive notifications related to security assessments.

  5. get-prerequisites

    Check prerequisites for upcoming security assessments.

MseeP.ai Security Assessment Badge

OnSecurity MCP

A Model Context Protocol (MCP) server for the OnSecurity API that allows Claude to query rounds, findings, prerequisites and notifications.

Installation

Installing via Smithery

To install the server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @onsecurity/onsecurity-mcp-server --client claude

Manual Installation

cd onsecurity-mcp-server
npm run build

Add the following to your Claude Desktop configuration file (adjust the paths as needed) and choose UAT or Prod:

{
  "mcpServers": {
    "onsec-mcp": {
      "command": "node",
      "args": [
        "/path/to/onsecurity-mcp-server/build/index.js"
      ],
      "env": {
        "ONSECURITY_API_TOKEN": "your_api_token",
        "ONSECURITY_API_BASE": "https://app.onsecurity.io/api/v2"
      }
    }
  }
}

After adding this configuration, restart Claude Desktop, and you'll be able to access the OnSecurity tools through Claude.

Usage

Once configured, Claude will have access to the following tools:

  • get-rounds
  • get-findings
  • get-blocks
  • get-notifications
  • get-prerequisites
Example Questions
  • Give me a summary of my most recent pentest/scan.
  • Show me trends across my pentests as a graph.
  • What can I address to make the most impact most quickly on my most recent pentest?
  • I would like summaries for different types of stakeholders on the state of our recent pentest engagemenets - eg high level, technical, managerial etc
  • Do I need to action anything to prevent test getting held up?
  • Are there any new findings?
  • What are the top 10 most common findings across pentests and scans.

Note: It is useful sometimes to configure Claude to "Extended thinking" for some questions.