io.github.Ankit512/itsoc-mcp
PYPI · ITSOC-MCP · SCANNED SEP 13
Read-only MCP server over a local log-analysis backend; a client that computes no verdicts.
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 → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency6
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 23 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 750 tokens (~107/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
pypi · itsoc-mcp
claude mcp add ankit512-itsoc-mcp -- uvx itsoc-mcp
{
"mcpServers": {
"ankit512-itsoc-mcp": {
"command": "uvx",
"args": [
"itsoc-mcp"
]
}
}
} {
"servers": {
"ankit512-itsoc-mcp": {
"command": "uvx",
"args": [
"itsoc-mcp"
]
}
}
} codex mcp add ankit512-itsoc-mcp -- uvx itsoc-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ankit512-itsoc-mcp": {
"type": "local",
"command": [
"uvx",
"itsoc-mcp"
],
"enabled": true
}
}
} openclaw mcp add ankit512-itsoc-mcp --command uvx --arg itsoc-mcp
mcp_servers:
ankit512-itsoc-mcp:
command: "uvx"
args: ["itsoc-mcp"] {
"McpServers": {
"ankit512-itsoc-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"itsoc-mcp"
]
}
}
} assistant mcp add ankit512-itsoc-mcp -t stdio -c uvx -a itsoc-mcp
{
"mcpServers": {
"ankit512-itsoc-mcp": {
"command": "uvx",
"args": [
"itsoc-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.
- 13 Sept 26 +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.
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 10 Sept 26 0
- Source repository: Repository check failed: the declared repository URL redirects; it must resolve directly. security
- Security disclosure: unverified → fail ▼ functional
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 4 Sept 26 0
- Source repository: Repository check failed: the declared repository URL returned HTTP 404. security
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 13 Sept 2026 · Analysed pypi/itsoc-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_log ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| compare | boolean | – | Also run the rules-vs-LLM comparison pass. |
| source | string | yes | A local file path or an http(s) URL to analyze. |
No output schema declared.
No examples provided.
explain_finding ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | Finding id from get_findings. |
| run_id | string | – | Optional; must be the active run. |
No output schema declared.
No examples provided.
export_run ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Export format. |
| run_id | string | – | Optional; must be the active run. |
No output schema declared.
No examples provided.
get_evidence ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | Finding id from get_findings. |
| run_id | string | – | Optional; must be the active run. |
No output schema declared.
No examples provided.
get_findings ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
list_runs ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
threat_intel_lookup ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_path | string | – | Optional local STIX bundle path (overrides ITSOC_STIX_BUNDLE). |
| ip | string | yes | IPv4 address to look up. |
No output schema declared.
No examples provided.
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 13 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 13 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.