StarShield Forensics

MCP开发工具

提供方 未标注

开发工具 stdio · 本地进程 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

离线、零依赖的 Python CLI 和隐私掩码 stdio MCP 服务器,用于 Chromium LevelDB WAL 数据雕刻、截图 ICC 来源溯源和银行业 IOC 验证。 浏览适用于 Claude、Cursor、VS Code 等 AI 智能体的 StarShield Forensics MCP...

一句话选型结论

按资料字段整理

StarShield Forensics 属于开发工具类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权未标注 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

开发

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
uvx

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
StarShield Forensics当前 未标注 stdio · 本地进程 本地部署 有 2026-11-20
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

14.1 KB
来自项目仓库与上游目录的原文,未做删改

starshield-forensics (v0.3.8 — Clean-Room Deterministic DFIR & MCP Toolkit)

> English | 简体中文 (README.zh-CN.md)

> Deterministic Chromium & Electron IndexedDB / LevelDB .log Multi-Schema Record Carver, Structural PNG/JPEG Container Inspector, Financial Checksum Validator & Zero-Dependency MCP Server
>
> Author: Ziqi Xiao (@Ziqi) · PyPI: starshield-forensics 0.3.8 (PEP 740) · Homebrew: Ziqi/tap/starshield-forensics · Concept DOI: 10.5281/zenodo.24145804 (v0.3.7: 10.5281/zenodo.24156262) · SWHID: swh:1:snp:4ed5efec... · OpenSSF Best Practices: #16602 (SILVER — 226%) · Scorecard: 8.0 / 10 (Fuzzing 10/10 · 11/18 Perfect Checks) · Provenance: SLSA L3 & Sigstore /attestations · Method Validation: UK FSR Statutory Code (FSA – DIG 100) / ISO 17025 Summary · License: MIT (REUSE 3.3) · Runtime: Python >= 3.10 (stdlib only, zero network calls, zero LLM dependencies)


High-Frequency Use Cases (DFIR, FinTech Audit & Developer Diagnostics)

starshield-forensics is an offline, read-only binary inspection and evidence triage toolkit serving three primary audiences with zero third-party dependencies:

  1. FinTech, E-Commerce & Expense-Audit Screenshot Pre-Screening (starshield inspect-image): Millisecond structural verification of reimbursement receipts, payment screenshots, and disputed attachments—verifying RFC 2083 PNG chunk CRC32 integrity (IHDR/IDAT/IEND/iCCP), multi-segment ISO 10918 JPEG APP2 ICC_PROFILE color headers (acsp), and Photoshop APP13 (8BIM) resource blocks alongside offline ISO-7812 Luhn / 89-country ISO-13616 IBAN Mod-97 / ISO-9362 SWIFT validation.
  2. Developer & IT Offline Diagnostics for Corrupted Electron / Chrome Caches (starshield precheck & parse-leveldb-log): Read-only local health check and uncompacted .log write-ahead log recovery for corrupted Chromium browser (Chrome, Edge, Brave) and Electron desktop app (VS Code, Slack, Microsoft Teams, Discord, WhatsApp Desktop) IndexedDB / Local Storage caches using strict masked Castagnoli CRC32C (0xA282EAD8) verification.
  3. Legal & DFIR Pre-Action Evidentiary Triage (UK FSR FSA – DIG 100 / ISO 17025 Aligned): Byte-offset-cited carving of soft-deleted or edited web-messaging and B2B portal records with explicit four-tier epistemic tagging (OBSERVED / DERIVED / INFERRED / UNKNOWN) and ephemeral HMAC-SHA256 pseudonymization.

All bundled fixtures in samples/ and starshield/data/—plus the seeded 24-case evaluation suite in benchmark/benchmark_suite.py (StarShield-Bench-24)—are 100% clean-room specification test vectors modeled on a fictional 2025 UK supplier-invoice scenario (GBP 18,400.00, ISO-13616 example IBANs GB82WEST12345698765432 and NO9386011117947, Luhn test string 6200000000000005). Zero real incident data or PII is included.


Epistemic Tiers & Capability Boundary Matrix (v0.3.8)

Every analytical output carries an explicit machine-readable epistemic tier so investigators and solicitors never conflate raw bytes with interpretive leads:

  • OBSERVED: Directly present in raw input bytes, chunk headers, or JSON fields (bound to physical WAL frame offsets or chunk offsets).
  • DERIVED: Deterministically computed from raw input via standardized algorithms (Castagnoli CRC32C, ISO/IEC 7812 Luhn, ISO-13616 Mod-97, UTC delta arithmetic).
  • INFERRED: Contextual triage lead requiring external corroboration (e.g., server-side bank logs or subpoenaed ISP records); never asserted as standalone proof.
  • UNKNOWN: Explicitly outside the evidentiary boundary of local client artifacts (e.g., records compacted prior to acquisition).

Module · Capability in v0.3.8 · Epistemic Boundary & Known Limitations
Zero-PII Storage Feasibility Gate (precheck) · Scans Chromium & Electron IndexedDB / Local Storage folders or .log/.ldb files offline, checks LevelDB SSTable footer magic (0xdb4775248b80fb57), .blob directories, and Blink 0xFF headers, emitting a deterministic GO / PARTIAL / NO_GO_COMPACTED_OR_UNSUPPORTED manifest with zero plaintext leakage. · Pre-screens compaction status prior to triage; does not decompress .ldb blocks.
Chromium & Electron LevelDB .log Carver (leveldb_log.py) · Parses 32 KiB physical blocks, verifies masked Castagnoli CRC32C (0xA282EAD8), reassembles cross-block FULL/FIRST/MIDDLE/LAST WriteBatch frames, and extracts UTF-8 & Blink UTF-16LE JSON records across Chromium browsers and Electron desktop apps (chatsvc for Microsoft Teams/Skype, Slack, WhatsApp Web/Desktop, Discord, VS Code, and B2B invoice portals via --schema auto\ · chatsvc\ · generic-json). · Does not decompress Snappy .ldb SSTables or decode non-JSON Blink StructuredClone primitives (roadmap: v0.4).
Exported Message & Portal JSON Triage (triage-json) · Enumerates soft-deleted (deletetime / deleted_ts / is_deleted) and edited (edittime / edited.ts) JSON records across messaging & portal exports, extracting validated IOCs strictly per record. · Cannot quantify records already compacted or evicted prior to acquisition.
Financial Checksum Validation (ioc_validators.py) · Validates payment cards via ISO/IEC 7812 Luhn, IBANs via all 89 SWIFT IBAN Registry country lengths (15–34 chars) + Mod-97, SWIFT/BICs via all 249 ISO 3166-1 alpha-2 country codes + XK (250 total codes) + stopword filtering, and pairs UK Sort Codes within a 120-char intra-message window. · Does not bundle proprietary Pay.UK Vocalink sort-code modulus weight tables.
RFC 2083 PNG & ISO 10918 JPEG Container Inspection (image_containers.py) · Enforces PNG IHDR + IDAT + IEND completeness and per-chunk CRC32, bounded-decompresses iCCP chunks (acsp), and reassembles multi-chunk JPEG APP2 ICC_PROFILE + APP13 (8BIM) segments through SOS/EOI (0xFFD9). · Emits neutral container observations + benign screenshot/OS-resave caveats; never declares standalone "proof of forgery".
Zero-Dependency MCP Server (mcp_server.py / starshield mcp) · Exposes 4 read-only deterministic tools (starshield_demo, starshield_precheck_leveldb, starshield_inspect_image_tamper, starshield_validate_financial_iocs) over JSON-RPC 2.0 stdio (newline & Content-Length framed) for Claude Desktop, Cursor, Google Antigravity, and Windsurf. · Enforces HMAC-SHA256 masked mode by default so cloud LLMs never receive raw PII, filenames, or raw SHA-256 hashes.
Keyed Pseudonymization & Cryptographic Agility (cli.py) · Default masked mode applies ephemeral per-run HMAC-SHA256 tokens (configurable via --hmac-digest {sha256,sha384,blake2b} and external 32-byte salt --hmac-key-file PATH) and suppresses raw file SHA-256 hashes, exact byte lengths, source filenames, PNG tEXt/iTXt previews, custom ICC names, exact UTC dates, and failure-path stderr filenames/byte counts/snippets. · Provides keyed pseudonymization for casual screen/log hygiene—NOT formal legal anonymization under UK GDPR / GDPR. Pass --unredacted only inside authorized offline environments.


10-Second Zero-Install Tryout (uvx) & Installation (pip PEP 740 / .pyz)```bash

Instant zero-install clean-room showcase (fetches PyPI wheel directly, zero repo clone needed):

uvx --from starshield-forensics starshield demo

Option A — Official PyPI package (with PEP 740 Sigstore digital attestations, zero dependencies):

pip install starshield-forensics
starshield demo

Option A2 — macOS / Linux Homebrew Tap (isolated virtualenv formula, zero dependencies):

brew install Ziqi/tap/starshield-forensics && starshield demo

Option B — Zero-install single-file zipapp (for air-gapped forensic VMs & law-firm IT):

python3 starshield.pyz demo
python3 starshield.pyz precheck /path/to/readonly_chromium_idb_copy

Option C — Clone & run all 26 unit/MCP tests, fuzzing harness & StarShield-Bench-24 (<1s, zero dependencies):

git clone https://github.com/Ziqi/starshield-forensics.git
cd starshield-forensics
PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=. python3 -m unittest discover -s tests -v
PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=. python3 -W error tests/fuzz_parsers.py --stdlib --iterations 2500
PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=. python3 benchmark/benchmark_suite.py
PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=. python3 scripts/verify_cross_tool_forensics.py
PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=. python3 -m starshield.cli demo


### Zero-Install AI Agent Integration (`starshield mcp` for Claude Desktop, Cursor, Antigravity &amp; Windsurf)

Mount StarShield&#x27;s 4 deterministic read-only binary inspection tools directly into any MCP client (privacy-masked by default via ephemeral `HMAC-SHA256` so cloud LLMs never see raw PII, filenames, or raw hashes):```json
{
  &quot;mcpServers&quot;: {
    &quot;starshield-forensics&quot;: {
      &quot;command&quot;: &quot;uvx&quot;,
      &quot;args&quot;: [&quot;--from&quot;, &quot;starshield-forensics&quot;, &quot;starshield&quot;, &quot;mcp&quot;]
    }
  }
}

Sample Deterministic Output (starshield demo, Default Masked Mode)```json

{
"epistemic_tier": "OBSERVED",
"schema_detected": "chatsvc",
"leveldb_batch_byte_offset": 397,
"leveldb_sequence_number": 1002,
"is_soft_deleted_in_ui": true,
"sender_mri": "[REDACTED_HMAC:1b71a34908e1]",
"cached_content": "[REDACTED_CONTENT — pass --unredacted to view]",
"extracted_iocs": {
"luhn_validated_cards": ["[REDACTED_HMAC:3ec5f5677098]"],
"mod97_validated_ibans": ["[REDACTED_HMAC:4dad6b1cc0be]", "[REDACTED_HMAC:f21864d3e75c]"]
}
}


### CLI Subcommands (`starshield [--unredacted] [--max-mb 64] [--hmac-digest {sha256,sha384,blake2b}] [--hmac-key-file PATH] `)

| Subcommand | Input Artifact | Output JSON Summary |
| :--- | :--- | :--- |
| `demo` | Built-in synthetic fixtures | Runs end-to-end clean-room WAL, JSON, container, and checksum showcase |
| `precheck  [--schema ...]` | Chromium folder or `.log`/`.ldb` | Zero-PII `GO` / `PARTIAL` / `NO_GO` feasibility &amp; compaction check |
| `parse-leveldb-log  [--schema ...]` | Chromium LevelDB `.log` WAL | Physical block CRC32C status, byte-offset-bound carved records, and validated IOCs |
| `triage-json  [--schema ...]` | Exported messaging/portal JSON | Soft-deleted &amp; edited records + per-record IOC schedule |
| `inspect-image ` | PNG or JPEG exhibit | Chunk/marker integrity, ICC profile (`acsp`) header fields, `8BIM`, and neutral caveats |
| `corroborate-timestamps ` | Timezone-aware UTC pairs | Monotonicity verification, clock-skew bounds, and edge-node frequency summary |
| `summarize-linguistics ` | Chat transcript JSON | Descriptive utterance-length &amp; punctuation distribution (`N &gt;= 30` guardrailed) |
| `mcp` | JSON-RPC 2.0 `stdio` stream | Read-only MCP server exposing `starshield_demo`, `starshield_precheck_leveldb`, `starshield_inspect_image_tamper`, and `starshield_validate_financial_iocs` |

---

## Deterministic Core vs. Human-Reviewed Triage

`starshield-forensics` intentionally contains **zero LLM or network code**. Byte-offset extraction, CRC32C verification, and banking check-digit math must be 100% deterministic and reproducible, ensuring embedded adversary messages cannot trigger indirect prompt injection during extraction. Any downstream bilingual indexing or legal schedule preparation belongs in a human-reviewed workflow where every statement cites an immutable underlying record hash.

---

## Cryptographic Release Verification &amp; Bit-for-Bit Reproducibility (`v0.3.8`)

Every official release (`starshield.pyz`, `.whl`, `.tar.gz`, and ISO/IEC 5962:2021 SPDX 2.3 SBOM `starshield-forensics-0.3.8.spdx.json`) is backed by **triple cryptographic verification**:
1. **GitHub OIDC + Sigstore (`Fulcio` X.509 + `Rekor` transparency log)** build provenance &amp; SPDX 2.3 SBOM attestations at `/attestations`;
2. **Isolated SLSA Build Level 3** provenance (`multiple.intoto.jsonl` via `slsa-framework/slsa-github-generator`);
3. **Air-gapped OpenSSH `Ed25519`** detached maintainer signature (`SHA256SUMS.sig`) verified against `KEYS.pub`.```bash
# 1. Verify Sigstore X.509 + Rekor build &amp; SBOM attestations via GitHub CLI:
gh attestation verify starshield.pyz -R Ziqi/starshield-forensics

# 2. Verify isolated SLSA Build Level 3 provenance (.intoto.jsonl):
slsa-verifier verify-artifact starshield.pyz \
  --provenance-path multiple.intoto.jsonl \
  --source-uri github.com/Ziqi/starshield-forensics

# 3. Offline air-gapped verification using standard OpenSSH (&gt;=8.2p1) &amp; SHA256SUMS:
ssh-keygen -Y verify -f KEYS.pub -I &quot;2196305+Ziqi@users.noreply.github.com&quot; -n file -s SHA256SUMS.sig &lt; SHA256SUMS
shasum -a 256 -c SHA256SUMS

# 4. Rebuild starshield.pyz &amp; SPDX 2.3 SBOM from source and verify bit-for-bit reproducibility:
python3 scripts/build_reproducible.py --verify
python3 scripts/generate_spdx_sbom.py --verify

Governance, Method Validation & Security Reporting

Verification / Archival Dimension Live Status & Permanent Identifier
Continuous Fuzzing (ClusterFuzzLite / Atheris)
Static Security (CodeQL SAST) & Deterministic CI
Supply-Chain Provenance & Licensing (REUSE 3.3)
Packaging (Homebrew Tap) & Scholarly / UNESCO Archival
  • Dual-Tool Forensic Method Validation (UK FSR Statutory Code FSA – DIG 100 [superseding FSR-C-107] & ISO/IEC 17025 Clause 7.2.2 Aligned): VALIDATION_REPORT_FSR_ISO17025.md (482 test vectors cross-validated against Google dfindexeddb 20260210 & Pillow 13.0.0; open-source validation aid for accredited laboratories, not a claim of laboratory accreditation)
  • OpenSSF Security Insights (v2.0.0), OSPS Baseline Level 3 (EU CRA Aligned) & REUSE 3.3: SECURITY-INSIGHTS.yml · SECURITY.md §5 · REUSE.toml · SWHID (v0.3.7): swh:1:rel:3fa912215b0bb2510f7a2cfdfbd51293e29980c4
  • Security Assurance Case & 12-Month Roadmap: SECURITY_ASSURANCE_CASE.md
  • Vulnerability Response Policy (48h Ack SLA): SECURITY.md · GitHub Private Vulnerability Reporting
  • Governance, Roles & Continuity Policy: GOVERNANCE.md
  • Contribution, DCO 1.1 & Testing Standards: CONTRIBUTING.md · CODE_OF_CONDUCT.md
  • Author: Ziqi Xiao (@Ziqi) — Documentation & Sample Workpaper · GitHub Issues

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
StarShield Forensics 怎么安装?

在客户端按下面的安装命令接入:uvx。装完在客户端配置里引用同一个包或端点。

StarShield Forensics 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

StarShield Forensics 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

StarShield Forensics 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

StarShield Forensics 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Windsurf、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

StarShield Forensics 能提供哪些能力?

资料显示能力标签包括 开发。具体工具清单以官方文档为准。

StarShield Forensics 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

StarShield Forensics 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。