# Compuute MCP Security Scanner (remote · scan.compuute.se)

Scan any public GitHub MCP-server repo for security issues. 37 MCP-specific L1 rules, 8 languages.

- Trust score: 64/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `scan.compuute.se`: 64/100 (this document), [markdown](https://verifymcp.io/servers/compuute-compuute-scan-api/scan.md), [page](https://verifymcp.io/servers/compuute-compuute-scan-api/scan)

## Channel facts

- Endpoint: `https://scan.compuute.se/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1063 tokens (~1063/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http compuute-compuute-scan-api https://scan.compuute.se/mcp/
```

### Codex

```toml
[mcp_servers.compuute-compuute-scan-api]
url = "https://scan.compuute.se/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "compuute-compuute-scan-api": {
      "type": "remote",
      "url": "https://scan.compuute.se/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add compuute-compuute-scan-api --url https://scan.compuute.se/mcp/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  compuute-compuute-scan-api:
    url: "https://scan.compuute.se/mcp/"
```

### Other

```json
{
  "mcpServers": {
    "compuute-compuute-scan-api": {
      "type": "http",
      "url": "https://scan.compuute.se/mcp/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 62, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 59, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 57, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 56)

First indexed and scored.

## MCP tools (1)

### `scan_mcp_server` (~969 tokens)

Scan a public GitHub MCP-server repository for security issues.

    Clones the repo (shallow, <60s, <200 MB), runs compuute-scan v0.6.2 in
    static analysis mode (no code execution from the target), and returns a
    structured report with severity counts, a 0-100 score, and the 10 most
    severe findings.

    WHEN TO USE:
      - Before connecting to an unknown MCP server discovered via Anthropic
        Registry, Smithery, mcp.so, or a Discord recommendation.
      - Before installing a third-party MCP-server package into a production
        pipeline.
      - As part of an agent's pre-commit / pre-deploy due-diligence step
        when adding new dependencies.
      - As one input to a multi-source trust evaluation (combine with
        publisher reputation, package install count, last-update recency).

    WHEN NOT TO USE:
      - For private repos. Use the on-prem CLI instead:
          `npx compuute-scan ./path-to-private-repo`
      - For deep exploitability assessment of a specific code path. This is
        pattern matching, not dataflow analysis. Book a manual L2-L4 audit
        at https://compuute.se/audit for that depth.
      - For non-GitHub hosts (GitLab, Bitbucket, self-hosted). v1 supports
        github.com only.
      - For repos > 200 MB or clone time > 60s. The endpoint returns a 413
        or 504 in those cases — fall back to local CLI.

    EXPECTED RESPONSE TIME:
      - Median: ~1-2 seconds for small repos (<100 files).
      - p99: ~10 seconds for medium repos.
      - Hard timeout at clone=60s, scan=120s combined.

    EXPECTED COST:
      - Free tier in MVP. Future Pro tier may charge per-scan or per-month.

    DATA FRESHNESS:
      - Scanner version is reported in response.scanner.version.
      - L1 rule set freshness reflects compuute-scan releases — see
        github.com/Compuute/compuute-scan/CHANGELOG.md for the latest CVE
        and threat-intel response timeline.

    EXAMPLES:

      Example 1 — scan an MCP server you'…

Input parameters:

- `github_url` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/compuute-compuute-scan-api/scan#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 63
- 2026-08-01: 63
- 2026-07-31: 62
- 2026-07-30: 59
- 2026-07-29: 58
- 2026-07-28: 57
- 2026-07-27: 57
- 2026-07-26: 56

## Links

- Remote endpoint: https://scan.compuute.se/mcp/
- Repository: https://github.com/Compuute/compuute-scan-api
- Website: https://scan.compuute.se/
- Changelog RSS feed: https://verifymcp.io/servers/compuute-compuute-scan-api/scan/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/compuute-compuute-scan-api/scan/changelog.json
- HTML version of this page: https://verifymcp.io/servers/compuute-compuute-scan-api/scan