mcp-skylos

Overview Schema Source Related Servers Discussions Admin

Scan for security issues

security_scan

Read-only

Scan source code to detect SQL injection, command injection, SSRF, path traversal, eval/exec, and unsafe deserialization, returning JSON findings with file and line.

Instructions

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 _run_id. Read-only; the scan runs locally and does not upload code. Use secrets_scan for hard-coded credentials and validate_code_change to check a diff before it lands.

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 analyze works (5 calls/day). The local CLI needs no key: skylos verify <file> and skylos agent install-hooks.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	Yes	Directory or file to scan. A relative path resolves against the MCP server's working directory.
`confidence`	No	Minimum confidence (0-100) for dead-code findings. Higher values report fewer, surer candidates; 60 is the CLI default.
`expand_advice`	No	Include every Advice record instead of rule-group counts; complete results are always available through _result_uri.
`exclude_folders`	No	Folder names to skip, e.g. ["migrations", "scripts"]. When given, this list replaces the default excludes (node_modules, .venv, build, dist and similar); omit it to keep the defaults.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv4.49.0Oct 14, 2026

addedInput schema / properties / confidence / description

Added value: +"Minimum confidence (0-100) for dead-code findings. Higher values report fewer, surer candidates; 60 is the CLI default."

addedInput schema / properties / exclude_folders / description

Added value: +"Folder names to skip, e.g. [\"migrations\", \"scripts\"]. When given, this list replaces the default excludes (node_modules, .venv, build, dist and similar); omit it to keep the defaults."

addedInput schema / properties / expand_advice

Added value: +{
+  "default": false,
+  "description": "Include every Advice record instead of rule-group counts; complete results are always available through _result_uri.",
+  "title": "Expand Advice",
+  "type": "boolean"
+}

addedInput schema / properties / path / description

Added value: +"Directory or file to scan. A relative path resolves against the MCP server's working directory."

Addedv4.10.0May 2, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, non-destructive, non-open-world behavior, and the description adds substantial context: the scan runs locally and does not upload code, findings are returned with rule ID/severity/file/line/message, `_run_id` is returned, and `_result_uri` can retrieve complete saved results. It also discloses authentication requirements and the fallback behavior when no API key is present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and is generally efficient for a complex tool. However, the sentence 'Defect and Review records remain complete' appears without clear connection to a security scan and slightly disrupts the otherwise useful flow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema and rich annotations, the description still supplies the key operational context an agent needs: authentication requirements, local execution behavior, alternative tools, result retrieval via `_result_uri`, and default vs expanded advice handling. It is complete enough for correct selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents `path`, `confidence`, `expand_advice`, and `exclude_folders`. The description restates the `expand_advice` grouping behavior but does not add meaningful syntax or usage guidance beyond what the schema already provides for the other parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: scanning source code for security issues, with concrete example categories such as SQL/command injection, SSRF, path traversal, and unsafe deserialization. It also differentiates from siblings by naming `secrets_scan` for credentials and `validate_code_change` for diffs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to alternatives: `secrets_scan` for hard-coded credentials and `validate_code_change` to check a diff before it lands. It also states operational prerequisites, including that `SKYLOS_API_KEY` is required and that without it only `analyze` works at 5 calls/day.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server