Schema | Offensive360 MCP Server

Offensive360 MCP Server

Official

Describes the environment variables required to run the server.

Name	Required	Description	Default
`O360_URL`	No	The URL of the Offensive360 instance. Defaults to https://sast.offensive360.com. Can point to your own on-premise or air-gapped instance.	https://sast.offensive360.com
`O360_TOKEN`	Yes	Your Offensive360 external scan token. Required for authentication.

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
o360_scan_pathA	Run an Offensive360 SAST scan on a local directory (60+ languages, taint/data-flow analysis). Uploads the directory as a zip, waits for the scan, and returns the findings with file/line, severity, and remediation guidance. Typical duration: 1–5 minutes.
o360_scan_statusA	Check the queue position of an Offensive360 scan started with o360_scan_path. Returns 0 when the scan is actively processing, a positive number for its queue position, and -1 when no scan is queued or running under that name (finished or unknown).

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/offensive360/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server