Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Compuute MCP Security Scanner

REMOTE · SCAN.COMPUUTE.SE · SCANNED SEP 20

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

Available components

remote · scan.compuute.se 77
0 this week 77 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Compuute MCP Security Scanner server?

Compuute MCP Security Scanner is a hosted endpoint at https://scan.compuute.se/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · scan.compuute.se

# add to Claude Code
claude mcp add --transport http compuute-compuute-scan-api 'https://scan.compuute.se/mcp/'
// .cursor/mcp.json
{
  "mcpServers": {
    "compuute-compuute-scan-api": {
      "url": "https://scan.compuute.se/mcp/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "compuute-compuute-scan-api": {
      "type": "http",
      "url": "https://scan.compuute.se/mcp/"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add compuute-compuute-scan-api --url 'https://scan.compuute.se/mcp/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  compuute-compuute-scan-api:
    url: "https://scan.compuute.se/mcp/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "compuute-compuute-scan-api": {
      "Transport": "http",
      "Url": "https://scan.compuute.se/mcp/"
    }
  }
}
# add to Vellum
assistant mcp add compuute-compuute-scan-api -t streamable-http -u 'https://scan.compuute.se/mcp/'
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Aug 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

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

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://scan.compuute.se/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=scan.compuute.se CN=YE2,O=Let's Encrypt,C=US 24 Jul 2026 22 Oct 2026 ECDSA 256 ECDSA-SHA384 601c76a5a8bdefab26bf9c794c3fbb17cb4
SANs: scan.compuute.se
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of scan.compuute.se. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
se. present 59407 8 Verified
compuute.se. present 51704 13 Verified
scan.compuute.se. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains
content-security-policy default-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=(), fullscreen=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://scan.compuute.se/mcp/ Verified 200
http (plaintext) http://scan.compuute.se/mcp/ HTTPS enforced 301 https://scan.compuute.se/mcp/
MCP tools · 1 exposed · ~969 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
scan_mcp_server ~969

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'…

NameTypeReqDescription
github_urlstringyes–

No output schema declared.

No examples provided.

Common questions

What is the Compuute MCP Security Scanner server?

Compuute MCP Security Scanner is listed in the public MCP registry as io.github.Compuute/compuute-scan-api. Scan any public GitHub MCP-server repo for security issues. 37 MCP-specific L1 rules, 8 languages. This page covers its hosted endpoint (https://scan.compuute.se/mcp/).

Is the Compuute MCP Security Scanner server safe to use?

Compuute MCP Security Scanner scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Compuute MCP Security Scanner server expose?

Compuute MCP Security Scanner exposes 1 tool: scan_mcp_server. Their descriptions and schemas cost roughly 969 tokens of context every time the server is loaded.

Does the Compuute MCP Security Scanner server require authentication?

No. We connected to Compuute MCP Security Scanner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Compuute MCP Security Scanner server still maintained?

Compuute MCP Security Scanner is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.