starshield-forensics
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Deterministic, strictly offline, read-only digital forensics & container provenance server. Default masked mode applies ephemeral HMAC-SHA256 pseudonymization so raw PII, filenames, and file hashes never enter LLM context.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| starshield_demoB | Execute StarShield's 5 deterministic offline triage engines on embedded 100% synthetic specification vectors (LevelDB 32KiB CRC32C WAL carving, PNG/JPEG ICC & 8BIM container inspection, Luhn/IBAN Mod-97/SWIFT validation, and UTC timestamp corroboration). |
| starshield_precheck_leveldbA | Perform a read-only millisecond diagnostic and GO/PARTIAL/NO_GO feasibility check on a local Chromium browser or Electron desktop app (VS Code, Slack, Microsoft Teams, Discord, WhatsApp Desktop) IndexedDB/LevelDB directory or .log/.ldb file without leaking raw content. |
| starshield_inspect_image_tamperA | Deterministically verify RFC 2083 PNG chunk CRC32 integrity (IHDR/IDAT/IEND/iCCP) and ISO 10918 JPEG APP2 ICC_PROFILE / APP13 Photoshop 8BIM resource blocks for FinTech reimbursement, e-commerce receipt, and disputed screenshot pre-screening. |
| starshield_validate_financial_iocsA | Scan text offline in <1ms to extract and mathematically verify ISO/IEC 7812 Luhn card numbers, 89-country ISO 13616 IBAN Mod-97 accounts, 250-territory ISO 9362 SWIFT/BIC codes, and intra-message UK Faster Payments Sort Code + 8-digit Account pairs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The three substantive tools target clearly distinct artifact types: LevelDB feasibility, image integrity, and financial IOC validation. The demo tool overlaps conceptually by exercising the same engines, but its explicit synthetic-vector-only scope keeps it mostly distinct; an agent could still mistakenly reach for demo instead of a specific analysis tool.
All tools share a consistent starshield_ snake_case prefix. Three names follow a clear verb_noun pattern, while starshield_demo is a bare noun rather than an action, which is a minor deviation but remains readable and predictable.
Four tools is well-scoped for a narrow forensic triage server. Each tool corresponds to a distinct capability area: demo evaluation, LevelDB precheck, image tamper inspection, and financial IOC validation.
The surface covers precheck, image inspection, financial validation, and a synthetic demo, but lacks a real-data LevelDB carving/extraction tool and a standalone UTC timestamp corroboration operation. These are notable gaps for a full forensic workflow, since some advertised engines appear only inside the synthetic demo.