Skip to content

Security: SemClone/mcp-semclone

Security

SECURITY.md

Security Policy

Supported Versions

We release patches for security vulnerabilities. Which versions are eligible for receiving such patches depends on the CVSS v3.0 Rating:

CVSS v3.0 Supported Versions
9.0-10.0 Releases within the previous three months
4.0-8.9 Most recent release

Reporting a Vulnerability

Please report (suspected) security vulnerabilities to security@semcl.one. You will receive a response from us within 48 hours. If the issue is confirmed, we will release a patch as soon as possible depending on complexity but historically within a few days.

Please include the following information in your report:

  • Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
  • Full paths of source file(s) related to the manifestation of the issue
  • The location of the affected source code (tag/branch/commit or direct URL)
  • Any special configuration required to reproduce the issue
  • Step-by-step instructions to reproduce the issue
  • Proof-of-concept or exploit code (if possible)
  • Impact of the issue, including how an attacker might exploit the issue

This information will help us triage your report more quickly.

MCP-Specific Security Considerations

When reporting security issues related to mcp-semclone, please also include:

  • MCP client being used (desktop client, etc.)
  • Tool configurations and parameters
  • Input data that triggered the issue
  • Whether the issue affects tool integrations or the MCP protocol implementation

Preferred Languages

We prefer all communications to be in English.

Policy

We follow the principle of Coordinated Vulnerability Disclosure.

There aren’t any published security advisories