mcp server
Compuute MCP Security Scanner
Scan any public GitHub MCP-server repo for security issues. 37 MCP-specific L1 rules, 8 languages.
Description as published by the maintainer. Source
- version 0.3.0
- active
- security
active — Most recent push to the repository was 2026-07-03. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
1 function, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
scan_mcp_server(github_url)- 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're evaluating: github_url = "https://github.com/modelcontextprotocol/servers" → score: 0, summary: {critical: 1, high: 94, medium: 22} → top_findings include SSRF, eval, etc. → recommendation: "AVOID — 1 critical and 94 high finding(s)..." Example 2 — scan a clean reference implementation: github_url = "https://github.com/microsoft/azure-devops-mcp" → score: 90+, summary: {critical: 0, high: 1} → recommendation: "REVIEW — 1 high finding(s)..." Example 3 — scan your own dev MCP-server before publishing: github_url = "https://github.com/yourorg/your-mcp" → audit your own surface before others install it OUTPUT FIELDS (stable schema): - repo_url (str): canonical URL of the scanned repo. - score (int): 0-100, higher safer. Coarse summary, not a precision claim. - summary (object): {critical, high, medium, low, info, files_scanned}. - recommendation (str): action guidance derived from severity counts. - findings_count (int): total raw findings (may include false positives). - top_findings (list): up to 10 most severe, each with {id, title, severity, file, line, owasp, cwe}. - l0_discovery (object): MCP transport, tool count, dependency pinning. - performance (object): clone_seconds, scan_seconds, repo_size_bytes. - scanner (object): {name, version, layers_covered}. - _disclaimer (str): MANDATORY triage disclaimer. Read it. Args: github_url: Public GitHub HTTPS URL (e.g. https://github.com/org/repo). Must be public and < 200 MB. v1 is github.com only. Returns: Structured scan result. On error, returns {"error": code, "message": ...} with HTTP-style code (invalid_url, clone_failed, scan_timeout, etc.). Required: github_url.
Last successful function declaration observed on . Source: https://scan.compuute.se/mcp/. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://scan.compuute.se/mcp/.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-07-03 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 9 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.3.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-05-23 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-05-23 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 1 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | scan.compuute.se | |
| mcp endpoint status | ok | The server listed 1 function when asked. | as of probe | scan.compuute.se |
Where to get it
Related, by what their authors tagged them
-
TridentChain Security
— last commit 2026-07-29, shares cve, security, supply-chain
Local supply-chain CVE scanner via OSV/NVD. Scans deps and IDE extensions. No upload.
-
Bawbel Scanner
— last commit 2026-07-05, shares agent-security, owasp, vulnerability-scanner
Security scanner for MCP servers and skill files. Detects AVE vulnerabilities before production.
-
Bawbel Scanner
— last commit 2026-07-05, shares agent-security, owasp, vulnerability-scanner
Security scanner for MCP servers and skill files. Detects AVE vulnerabilities before production.
-
io.github.Gorgon-Cyber/gorgon-scout
— last commit 2026-08-07, shares owasp, security, vulnerability-scanner
Run AI-driven web-app and API security scans (DAST) from Claude or any MCP agent. Windows.
-
Bawbel Scanner
— last commit 2026-05-23, shares owasp, vulnerability-scanner
Scan MCP servers and skill files for AVE vulnerabilities. Conformance scoring and threat intel.
-
io.github.goklab/guardvibe
— last commit 2026-07-23, shares cve, owasp, security
Deterministic security layer your AI can't be. 462 rules, 39 tools, CLI + doctor + host audit.
-
io.github.CSOAI-ORG/sbom-cyclonedx-mcp
— last commit 2026-06-26, shares security, supply-chain
Software Bill of Materials generation + validation in CycloneDX 1.6 and SPDX 2.3 formats. Requir...
-
io.github.eliottreich/taskbounty-check
— last commit 2026-06-21, shares security, supply-chain
Local GitHub Actions/CI maintenance check (action pinning, token perms). Not a full security audit.
-
Closeread Verify
— last commit 2026-06-11, shares security, supply-chain
A verified dependency-audit verdict any AI agent can call over MCP, not a raw scan.
-
Wafergraph MCP
— last commit 2026-07-31, shares supply-chain
Read-only MCP server for wafergraph.com's semiconductor & AI supply-chain data: 30 tools, no auth.
These share tags the maintainers applied themselves, such as cve, security, supply-chain, vulnerability-scanner. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
Also from compuute
-
Lead Enrichment API
— repository gone
Curated EU AI/Sec/DevTools/Fintech B2B leads, Claude-scored. MCP+x402. Free 250/mo.
How the author describes it
Topics the maintainer set on GitHub: agent-security, cve, mcp, mcp-server, owasp, python, security, static-analysis, supply-chain, vulnerability-scanner.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json