# io.github.Ankit512/itsoc-mcp (pypi · itsoc-mcp)

Read-only MCP server over a local log-analysis backend; a client that computes no verdicts.

- Trust score: 76/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `itsoc-mcp`: 76/100 (this document), [markdown](https://verifymcp.io/servers/ankit512-itsoc-mcp/itsoc-mcp.md), [page](https://verifymcp.io/servers/ankit512-itsoc-mcp/itsoc-mcp)

## Channel facts

- Registry: `pypi`
- Package: `itsoc-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it.
  - 0 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 6/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 30 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 84/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 750 tokens (~107/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.Ankit512/itsoc-mcp server?

io.github.Ankit512/itsoc-mcp runs locally as a PyPI package, launched with uvx itsoc-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add ankit512-itsoc-mcp -- uvx itsoc-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ankit512-itsoc-mcp": {
      "command": "uvx",
      "args": [
        "itsoc-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ankit512-itsoc-mcp": {
      "command": "uvx",
      "args": [
        "itsoc-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ankit512-itsoc-mcp -- uvx itsoc-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ankit512-itsoc-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "itsoc-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ankit512-itsoc-mcp --command uvx --arg itsoc-mcp
```

### Hermes

```yaml
mcp_servers:
  ankit512-itsoc-mcp:
    command: "uvx"
    args: ["itsoc-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ankit512-itsoc-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "itsoc-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ankit512-itsoc-mcp -t stdio -c uvx -a itsoc-mcp
```

### Other

```json
{
  "mcpServers": {
    "ankit512-itsoc-mcp": {
      "command": "uvx",
      "args": [
        "itsoc-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 76, −2)

- [functional] Stability: pass → 0.80

### 2026-09-19 (score 78, 0)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 77, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 61, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-13 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 75, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-11 (score 60, −14)

- [security regression] Malware scan: pass → unverified

## MCP tools (7)

### `analyze_log` (~118 tokens)

Run the project's existing analysis over a local log file OR an http(s) URL and return a run summary (run_id, severity counts, lines parsed/unparsed, unrecognized flag, detector sha256). Verdicts are rule-owned by the frozen detector; this only relays them. An unrecognized format returns '0 lines parsed', never a fake all-clear.

Input parameters:

- `compare` (boolean): Also run the rules-vs-LLM comparison pass.
- `source` (string, required): A local file path or an http(s) URL to analyze.

### `list_runs` (~48 tokens)

List saved analysis runs from the backend's run history (read-only). Returns run_id, label, finding count, and the current run. Empty when there are no runs — never a fabricated entry.

### `get_findings` (~146 tokens)

Filtered findings for the ACTIVE run, with rule-owned severity, rule_id, and derived MITRE tags. Filter by severity/rule/host and limit. Host/title are redacted by default (entity-bearing text). A non-current run_id is an honest error — this server does not switch the active run.

Input parameters:

- `host` (string): host substring filter.
- `limit` (integer): max findings (default 50).
- `rule` (string): rule_id substring filter.
- `run_id` (string): Optional; must be the active run. Omit to use it.
- `severity` (string): CRITICAL|HIGH|MEDIUM|LOW filter (exact).

### `get_evidence` (~105 tokens)

Real evidence lines + rule predicate + timeline for ONE finding in the active run. Raw log lines and timeline labels pass through the console/redact.py egress choke point and are REDACTED by default; set ITSOC_MCP_TRUSTED_LOCAL=1 for raw text. Evidence is verbatim source (masked), never fabricated.

Input parameters:

- `finding_id` (string, required): Finding id from get_findings.
- `run_id` (string): Optional; must be the active run.

### `explain_finding` (~98 tokens)

Advisory LLM explanation for ONE finding via the existing /api/explain endpoint. The explanation is ADVISORY only — it never changes, suppresses, or escalates the rule verdict. Prose is redacted by default. An unreachable model is an honest error, never a made-up explanation.

Input parameters:

- `finding_id` (string, required): Finding id from get_findings.
- `run_id` (string): Optional; must be the active run.

### `export_run` (~106 tokens)

Export the ACTIVE run via /api/export (csv|html|xml|json|md). When idle the backend returns 409 and this relays it honestly — never an empty file. The export carries raw log text, so content is withheld by default (size + sha256 returned); set ITSOC_MCP_TRUSTED_LOCAL=1 to receive it inline.

Input parameters:

- `format` (string): Export format.
- `run_id` (string): Optional; must be the active run.

### `threat_intel_lookup` (~129 tokens)

OFFLINE STIX->MITRE lookup for one IPv4 address, reusing the project's existing offline threat-intel code (no network egress). Match + severity come from threat_intel/threat_detector.py; MITRE tags are derived. No bundle configured -> honest n/a; no match -> honest 'no match', never a fake all-clear. Bundle path via arg or ITSOC_STIX_BUNDLE.

Input parameters:

- `bundle_path` (string): Optional local STIX bundle path (overrides ITSOC_STIX_BUNDLE).
- `ip` (string, required): IPv4 address to look up.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/ankit512-itsoc-mcp/itsoc-mcp#diagnostics

## Score history

- 2026-09-20: 76
- 2026-09-19: 78
- 2026-09-18: 78
- 2026-09-17: 77
- 2026-09-16: 77
- 2026-09-15: 77
- 2026-09-14: 61
- 2026-09-13: 76
- 2026-09-12: 75
- 2026-09-11: 60
- 2026-09-10: 74
- 2026-09-09: 74
- 2026-09-08: 73
- 2026-09-07: 73
- 2026-09-06: 72
- 2026-09-05: 72
- 2026-09-04: 71
- 2026-09-03: 71
- 2026-09-02: 70
- 2026-09-01: 70
- 2026-08-31: 75
- 2026-08-30: 74
- 2026-08-29: 74
- 2026-08-28: 73
- 2026-08-27: 73
- 2026-08-26: 70
- 2026-08-25: 68
- 2026-08-24: 68
- 2026-08-23: 68
- 2026-08-22: 68

## Common questions

### What is the io.github.Ankit512/itsoc-mcp server?

io.github.Ankit512/itsoc-mcp is listed in the public MCP registry as io.github.Ankit512/itsoc-mcp. Read-only MCP server over a local log-analysis backend; a client that computes no verdicts. This page covers its PyPI package (itsoc-mcp).

### Is the io.github.Ankit512/itsoc-mcp server safe to use?

io.github.Ankit512/itsoc-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.Ankit512/itsoc-mcp server expose?

io.github.Ankit512/itsoc-mcp exposes 7 tools: analyze_log, list_runs, get_findings, get_evidence, explain_finding, and 2 more. Their descriptions and schemas cost roughly 750 tokens of context every time the server is loaded.

### Is the io.github.Ankit512/itsoc-mcp server still maintained?

io.github.Ankit512/itsoc-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/itsoc-mcp/
- Socket report: https://socket.dev/pypi/package/itsoc-mcp
- Changelog RSS feed: https://verifymcp.io/servers/ankit512-itsoc-mcp/itsoc-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ankit512-itsoc-mcp/itsoc-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ankit512-itsoc-mcp/itsoc-mcp