Skylos MCP Server

Dead code, security, secrets detection and code quality for Python, TypeScript, Go.

Remote serverstreamable-httpPython

What is the Skylos MCP server?

Skylos MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Dead code, security, secrets detection and code quality for Python, TypeScript, Go.

What you get

Skylos is an open-source static analysis CLI for Python, TypeScript, JavaScript, Java, Go, Kotlin, PHP, Rust, Dart, C#, Shell, and deployment config. It runs locally by default and can also be used as a CI/CD PR gate.

What the assistant can call

Once Skylos is connected, these are the calls the assistant has available:

  • Attestation — ** JSON/md/SARIF reports carry a reproducible SHA-256 digest
  • CI-native — ** skylos cicd init --defend generates the workflow step, the
  • Agent-native — ** the verify_agent MCP tool lets coding agents verify the
  • Framework — aware dead code detection:** FastAPI, Django, Flask, pytest,
  • Local — first operation:** core static analysis does not require cloud upload
  • Agent — loop verification:** skylos verify and MCP verify_change return
  • Evidence — backed AI defects:** --ai-defects and full scans put strict
  • Verification — backed remediation:** security fixes are checked by re-running
  • Project — specific rules:** add local YAML rules and extend prompt, credential,
  • events.jsonl — chronological run, phase, and tool-call events
  • state.json — full observable state, including phases, tool calls, decisions,
  • summary.json — compact status, counts, budget, and artifact paths

Configuration and credentials

You will need 2 environment variables: RULE_ID, MY_AGENT_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

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

Choosing this one

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. Skylos's toolset — Attestation, CI-native, Agent-native and 11 more — is a fair guide to whether it matches your workflow. It is maintained by duriantaco; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Skylos's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Skylos.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the skylos mcp server does with a few real requests.

Available tools

ToolWhat it does
Attestation** JSON/md/SARIF reports carry a reproducible SHA-256 digest
CI-native** skylos cicd init --defend generates the workflow step, the
Agent-native** the verify_agent MCP tool lets coding agents verify the
Frameworkaware dead code detection:** FastAPI, Django, Flask, pytest,
Localfirst operation:** core static analysis does not require cloud upload
Agentloop verification:** skylos verify and MCP verify_change return
Evidencebacked AI defects:** --ai-defects and full scans put strict
Verificationbacked remediation:** security fixes are checked by re-running
Projectspecific rules:** add local YAML rules and extend prompt, credential,
events.jsonlchronological run, phase, and tool-call events.
state.jsonfull observable state, including phases, tool calls, decisions,
summary.jsoncompact status, counts, budget, and artifact paths.
behavior-results.jsonnormalized runtime assertions, provenance, coverage,
GoalCommand

How to install the Skylos MCP server

{
  "mcpServers": {
    "skylos": {
      "command": "uvx",
      "args": ["skylos"],
      "env": {
        "RULE_ID": "your-value",
        "MY_AGENT_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
RULE_IDConfiguration value read at startup.Optional
MY_AGENT_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Skylos to Attestation.
  • Use Skylos to CI-native.
  • Use Skylos to Agent-native.

Frequently asked questions

It connects Skylos to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Attestation, CI-native, Agent-native, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Skylos directly.