Compuute MCP Security Scanner MCP Server

Scan any public GitHub MCP-server repo for security issues. 37 MCP-specific L1 rules, 8 languages. The compuute mcp security scanner mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

POST a public GitHub repo URL → get a structured security report scored against 37 MCP-specific rules across 8 languages (TS/JS, Python, Go, Rust, C#, Java, Kotlin).

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• Feature — How
• Example — The Example tool exposed by this server

Configuration

You will need one environment variable: COMPUUTE_SCAN_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the compuute mcp security scanner mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Compuute MCP Security Scanner's toolset — Feature, Example — is a fair guide to whether it matches your workflow. It is maintained by Compuute; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.