Skip to main content

Kaleidoscope MCP server

Protect your code and get a Scope-Score without leaving your AI coding tool.

This is a Model Context Protocol server that exposes Kaleidoscope as two tools:

  • scope_score — score how exposed a project is to AI-assisted reverse engineering (0–100), no output written.
  • protect_project — harden a project and write the protected build to a .zip, returning its Scope-Score.

It works in any MCP-capable client: Claude Code, the Claude desktop app, Cursor, Windsurf, VS Code (GitHub Copilot), Continue, Cline, and others. The protection runs server-side on your Kaleidoscope account — nothing proprietary is shipped to the client; only your source is uploaded for protection.

Prerequisites

Run it

Until it's published to PyPI, run from source:

cd integrations/mcp-server
uv run kaleidoscope-mcp      # or: pip install -e . && kaleidoscope-mcp

The server speaks over stdio; your client launches it for you using the config below. Set KALEIDOSCOPE_API_KEY in that config (and, if self-hosting, KALEIDOSCOPE_API_URL).

Client configuration

Claude Code

claude mcp add kaleidoscope \
  --env KALEIDOSCOPE_API_KEY=YOUR_KEY \
  -- uvx kaleidoscope-mcp

Cursor — .cursor/mcp.json

{
  "mcpServers": {
    "kaleidoscope": {
      "command": "uvx",
      "args": ["kaleidoscope-mcp"],
      "env": { "KALEIDOSCOPE_API_KEY": "YOUR_KEY" }
    }
  }
}

VS Code — .vscode/mcp.json

{
  "servers": {
    "kaleidoscope": {
      "command": "uvx",
      "args": ["kaleidoscope-mcp"],
      "env": { "KALEIDOSCOPE_API_KEY": "YOUR_KEY" }
    }
  }
}

Windsurf / Continue / Cline

Use the same shape as Cursor (an mcpServers entry with command, args, env) in that tool's MCP config file.

Running from source instead of a published package? Replace "command": "uvx", "args": ["kaleidoscope-mcp"] with "command": "uv", "args": ["--directory", "/path/to/integrations/mcp-server", "run", "kaleidoscope-mcp"].

Try it

In your coding tool, ask:

"What's the Scope-Score of this project?" → calls scope_score "Protect this project before I ship it." → calls protect_project

Metadata

Release files for kaleidoscope-mcp 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for kaleidoscope-mcp 0.1.0
File Size Uploaded Provenance Actions
kaleidoscope_mcp-0.1.0.tar.gz 4.9 kB Without provenance Details for kaleidoscope_mcp-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for kaleidoscope-mcp 0.1.0
File Interpreter ABI Platform Actions
kaleidoscope_mcp-0.1.0-py3-none-any.whl Python 3 none any Details for kaleidoscope_mcp-0.1.0-py3-none-any.whl

Total release size: 10.8 kB

Release files / kaleidoscope_mcp-0.1.0.tar.gz

Download URL kaleidoscope_mcp-0.1.0.tar.gz
Size 4.9 kB
Tags Source
SHA-256 checksum
How to use checksums
f448937e4fdbc086c8dba1aa148a65726e47a33c59d35c1b073fe7c0b19a2f95
BLAKE2b-256 checksum
How to use checksums
ca104a40d4cfd0f8e4e88676f12b2f0ac90e1b53e00831cff1932ec54bf7e76e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.13.8 {"installer":{"name":"uv","version":"0.13.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / kaleidoscope_mcp-0.1.0-py3-none-any.whl

Download URL kaleidoscope_mcp-0.1.0-py3-none-any.whl
Size 5.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
eced7b3669f2c0d888b0c5be276a0559cfa7662a6e4d6973b5c733f593e1372c
BLAKE2b-256 checksum
How to use checksums
fbc4e24ae30cc2d682c11300f1f2e6990ed6d244a3332414dc5d562b1f812d48
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.13.8 {"installer":{"name":"uv","version":"0.13.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for kaleidoscope-mcp 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page