com.offensive360/o360-mcp
NPM · O360-MCP · SCANNED AUG 3
Run Offensive360 SAST scans (60+ languages) on local code; findings with file/line and fixes
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security89
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (167 of 172), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (167 of 172), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 213 tokens (~106/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · o360-mcp
claude mcp add com-offensive360-o360-mcp -- npx -y o360-mcp
codex mcp add com-offensive360-o360-mcp -- npx -y o360-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-offensive360-o360-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"o360-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-offensive360-o360-mcp --command npx --arg -y --arg o360-mcp
mcp_servers:
com-offensive360-o360-mcp:
command: "npx"
args: ["-y", "o360-mcp"] {
"mcpServers": {
"com-offensive360-o360-mcp": {
"command": "npx",
"args": [
"-y",
"o360-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 167 packages
167 packages in the resolved dependency tree · 124 deprecated · 56 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
o360_scan_path ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude | array | — | Extra directory names to exclude from the upload |
| path | string | yes | Absolute path of the directory to scan |
| project_name | string | — | Project name in the Offensive360 dashboard (default: directory name) |
| timeout_seconds | integer | — | Max seconds to wait (default 900) |
No output schema declared.
No examples provided.
o360_scan_status ~79
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).
| Name | Type | Req | Description |
|---|---|---|---|
| project_name | string | yes | The project name used when the scan was started |
No output schema declared.
No examples provided.