mcp-skylos
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyzeA | Find dead code: unused functions, classes, imports, variables, parameters and files. Use this to list cleanup candidates in a project. Returns JSON with a
summary and per-category findings (file, line, name, confidence) plus
Defect and Review records remain complete. Advice is grouped by default; expand_advice=True includes every Advice record. Read _result_uri for the complete saved result without rescanning. Works without SKYLOS_API_KEY (5 calls/day); higher limits with a key. |
| security_scanA | Scan source code for security issues such as SQL and command injection, SSRF, path traversal, eval/exec and unsafe deserialization. Returns JSON with findings (rule ID, severity, file, line, message) and
Defect and Review records remain complete. Advice is grouped by default; expand_advice=True includes every Advice record. Read _result_uri for the complete saved result without rescanning. Requires SKYLOS_API_KEY: this tool returns an authentication error unless the MCP server is started with SKYLOS_API_KEY set. Without a key only |
| quality_checkA | Report code-quality issues: high complexity, deep nesting, long functions, duplicate branches and similar maintainability findings. Returns JSON with findings (rule ID, file, line, message) and
Defect and Review records remain complete. Advice is grouped by default; expand_advice=True includes every Advice record. Read _result_uri for the complete saved result without rescanning. Requires SKYLOS_API_KEY: this tool returns an authentication error unless the MCP server is started with SKYLOS_API_KEY set. Without a key only |
| architecture_checkA | Report architecture findings for a project: module coupling, cohesion and circular dependencies. Returns JSON with the architecture findings and Defect and Review records remain complete. Advice is grouped by default; expand_advice=True includes every Advice record. Read _result_uri for the complete saved result without rescanning. Requires SKYLOS_API_KEY: this tool returns an authentication error unless the MCP server is started with SKYLOS_API_KEY set. Without a key only |
| health_scoreA | Assess a project through separate Risk, Maintainability and Dead code readouts. This tool retains its health_score name for compatibility but no longer creates a blended numeric grade. Gate policy remains independent. Returns assessment, coverage, finding counts and _run_id. Read-only and local. Advice is grouped by default; expand_advice=True includes every Advice record. Read _result_uri for the complete saved result. Requires SKYLOS_API_KEY: this tool returns an authentication error unless the MCP server is started with SKYLOS_API_KEY set. Without a key only |
| secrets_scanA | Find hard-coded secrets and credentials (API keys, tokens, private keys, passwords) in source and config files. Returns JSON with findings (provider, file, line) and Defect and Review records remain complete. Advice is grouped by default; expand_advice=True includes every Advice record. Read _result_uri for the complete saved result without rescanning. Requires SKYLOS_API_KEY: this tool returns an authentication error unless the MCP server is started with SKYLOS_API_KEY set. Without a key only |
| remediateA | Plan or apply LLM-generated fixes for Skylos findings in a project. With dry_run=True (default), static analysis returns a remediation
plan without calling a model or changing files. With dry_run=False,
it generates fixes and can edit files in place: this needs the
Requires SKYLOS_API_KEY: this tool returns an authentication error unless the MCP server is started with SKYLOS_API_KEY set. Without a key only |
| verify_dead_codeA | Ask an LLM to review selected unused function, class, import and variable candidates, with its reasoning. Use it after Requires SKYLOS_API_KEY: this tool returns an authentication error unless the MCP server is started with SKYLOS_API_KEY set. Without a key only |
| provenance_scanA | Report available evidence of AI-agent, bot and human contributions. Combines git signals since the base (agent bot accounts, Co-authored-by and AI declaration trailers, agent-named commit subjects) with recorded local attribution evidence. Returns JSON with per-file attribution, evidence and coverage status. Commit declarations do not establish line authorship; missing evidence remains unknown. Read-only and local. Requires SKYLOS_API_KEY: this tool returns an authentication error unless the MCP server is started with SKYLOS_API_KEY set. Without a key only |
| generate_fixA | Build a unified-diff patch that removes (or comments out) dead code found by static analysis, after grep verification drops findings that are still referenced. Returns the diff, patch summary, validation errors and applied status. With apply=False (default) it previews changes; with apply=True it edits files if patch validation succeeds. Refuses to run when the analysis or grep verification was incomplete. Review the diff and run trusted tests before keeping it. Requires SKYLOS_API_KEY: this tool returns an authentication error unless the MCP server is started with SKYLOS_API_KEY set. Without a key only |
| learn_triageA | Record whether a finding was accepted or dismissed so Writes the decision to the project's local Skylos state. Requires SKYLOS_API_KEY: this tool returns an authentication error unless the MCP server is started with SKYLOS_API_KEY set. Without a key only |
| get_triage_suggestionsA | Suggest accept or dismiss for current findings, based on decisions recorded with Returns JSON suggestions with finding fingerprints, suggested actions and confidence, plus the number of learned patterns. Read-only and local. Requires SKYLOS_API_KEY: this tool returns an authentication error unless the MCP server is started with SKYLOS_API_KEY set. Without a key only |
| validate_code_changeA | Validate a code diff for security regressions and issues before it lands. Takes a unified diff and checks for:
Returns pass/fail with findings. Requires SKYLOS_API_KEY: this tool returns an authentication error unless the MCP server is started with SKYLOS_API_KEY set. Without a key only |
| verify_changeA | Verify a changed file/range for AI-code defects and security bugs. Returns a narrow, versioned JSON verdict containing AI-code trust findings such as hallucinated references, unfinished generated code, stale references, disabled controls, and dependency hallucinations (checked by default; pass include_dependency_hallucinations=False to skip the registry lookups), plus high/critical security findings (category "security") and hard-coded secrets (category "secret", values redacted) in the selected file/range. Pass include_security_findings=False to skip the security and secret checks. Requires SKYLOS_API_KEY: this tool returns an authentication error unless the MCP server is started with SKYLOS_API_KEY set. Without a key only |
| verify_agentA | Statically verify an AI agent's guardrails before deployment. Deterministic, local pre-deployment agent verification: inventories LLM integrations, runs the defense checks (prompt-injection exposure, dangerous sinks, tool scope, output validation, PII filtering, cost controls), and returns scores, failed checks with remediation, OWASP LLM/Agentic coverage, and a reproducible attestation digest. No model is involved in the verdict and the analysis runs locally; source code is not sent to Skylos Cloud. Optional gate: set fail_on (severity) and/or min_score (0-100). Requires SKYLOS_API_KEY: this tool returns an authentication error unless the MCP server is started with SKYLOS_API_KEY set. Without a key only |
| get_security_contextA | Summarize a project's security setup: detected web frameworks, auth decorators and middleware, security headers, rate limiting, input validation and a supported Skylos YAML policy file. Use it before reviewing or writing security-sensitive code to learn the project's conventions. Returns JSON. Read-only and local. Requires SKYLOS_API_KEY: this tool returns an authentication error unless the MCP server is started with SKYLOS_API_KEY set. Without a key only |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_latest_result | Complete JSON result, including every Advice record; of the most recent stored Skylos tool run. |
| list_results | List stored tool runs with run_id, tool, path and timestamp. |
TDQS
Scored across 16 tools
Several tools have overlapping surfaces: security_scan, validate_code_change, and verify_change all report security findings (differing only in scope), and remediate, generate_fix, and verify_dead_code all touch dead-code fixing, while health_score re-aggregates analyze/quality_check/architecture_check outputs. The descriptions do a reasonable job of distinguishing scope and intent, so an agent can mostly disambiguate, but the boundaries are not crisp.
Two competing conventions coexist: verb_noun tools (verify_agent, get_security_context, generate_fix, verify_change) and noun_action scan/check tools (security_scan, secrets_scan, provenance_scan, quality_check, architecture_check), plus bare verbs (analyze, remediate) and a noun_score (health_score). It remains readable, but there is no single predictable pattern.
16 tools sits at the edge of the heavy range but is largely justified by the platform's breadth (verification, static analysis, security, quality, architecture, remediation, triage, provenance). A few tools feel redundant (two diff-verification tools, two fix-generation tools), so it is slightly over-scoped rather than egregiously so.
The surface covers a coherent lifecycle: context discovery (get_security_context), multiple scanners, dead-code analysis with LLM confirmation and patch generation, remediation, change validation, and a triage learn/suggest loop. Coverage is strong; only minor gaps (e.g. no explicit run/result retrieval or config tooling beyond the referenced resource) keep it from perfect.