Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SHULIAK SIP-1 Zero-Egress AI & MCP Firewall

NPM · @SHULIAK-CORP/SIP1-MCP

On-device NIST SP 800-38G FF1 (9/9 CAVP) pseudonymization, OWASP MCP05/06 guard & EU AI Act AIBOM.

+16 this week 72 Trust /100

Last scanned (16 hours ago)

Scores higher than 44% of npm servers

Category Security

Trust breakdown (7 categories)

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
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
  • 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 (Apache-2.0).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 431 tokens (~71/item across 6 items; 5 tools + 1 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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

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.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 15 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: fail → pass ▲ functional
  • 14 Nov 26 +32
    • Injection markers: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
    • Package version: 2.6.1 → 2.6.3 functional
  • 13 Nov 26 24

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/@shuliak-corp/sip1-mcp@2.6.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~388 tokens

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 →

Tool Tokens
sip1_audit_jsonrpc ~77

Inspect MCP JSON-RPC 2.0 tool call payloads for OWASP MCP05/06 Path Traversal, Command Injection, Prototype Pollution, and covert Zero-Width Unicode smuggling.

NameTypeReqDescription
payloadstringyesRaw JSON-RPC 2.0 request or tool argument payload string to audit for security threats.

No output schema declared.

No examples provided.

sip1_generate_aibom ~87

Generate a cryptographically signed CycloneDX AI Bill of Materials (AIBOM) & SHA-256 Merkle attestation for EU AI Act, GDPR Art. 4(5), SOC 2, and NIST 800-171 compliance.

NameTypeReqDescription
organizationstringyesLegal entity or workspace identifier to bind into the signed CycloneDX AIBOM manifest.

No output schema declared.

No examples provided.

sip1_license_status ~73

Check active SHULIAK SIP-1 license tier, remaining free session quota, or verify and activate an offline Ed25519 license key.

NameTypeReqDescription
licenseKeystring–Optional Ed25519 signed license token (SIP1.TIER.YYYYMMDD.ORG.SIGNATURE) to verify offline.

No output schema declared.

No examples provided.

sip1_rehydrate_response ~58

Deterministically restore synthetic SIP-1 twins and session tokens back to original plaintext values in local memory.

NameTypeReqDescription
maskedTextstringyesInbound LLM or tool response string containing SIP-1 tokens or FF1 synthetic twins.

No output schema declared.

No examples provided.

sip1_scrub_payload ~93

Scrub sensitive PII, Luhn payment cards, ISO-7064 IBANs, and cloud API secrets from text or JSON using on-device NIST SP 800-38G FF1 pseudonymization.

NameTypeReqDescription
contourstring–Operational security contour threshold (default: CORPORATE).
textstringyesRaw prompt, code snippet, or JSON payload to sanitize locally before external transmission.

No output schema declared.

No examples provided.

Install

How do I install the SHULIAK SIP-1 Zero-Egress AI & MCP Firewall server?

SHULIAK SIP-1 Zero-Egress AI & MCP Firewall runs locally as an npm package, launched with npx -y @shuliak-corp/sip1-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @shuliak-corp/sip1-mcp

# add to Claude Code
claude mcp add shuliak11-sip1-mcp-firewall -- npx -y @shuliak-corp/sip1-mcp
Common questions

What is the SHULIAK SIP-1 Zero-Egress AI & MCP Firewall server?

SHULIAK SIP-1 Zero-Egress AI & MCP Firewall is listed in the public MCP registry as io.github.Shuliak11/sip1-mcp-firewall. On-device NIST SP 800-38G FF1 (9/9 CAVP) pseudonymization, OWASP MCP05/06 guard & EU AI Act AIBOM. This page covers its npm package (@shuliak-corp/sip1-mcp).

Is the SHULIAK SIP-1 Zero-Egress AI & MCP Firewall server safe to use?

SHULIAK SIP-1 Zero-Egress AI & MCP Firewall scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 SHULIAK SIP-1 Zero-Egress AI & MCP Firewall server expose?

SHULIAK SIP-1 Zero-Egress AI & MCP Firewall exposes 5 tools: sip1_scrub_payload, sip1_rehydrate_response, sip1_audit_jsonrpc, sip1_generate_aibom, sip1_license_status. Their descriptions and schemas cost roughly 388 tokens of context every time the server is loaded.

Is the SHULIAK SIP-1 Zero-Egress AI & MCP Firewall server still maintained?

SHULIAK SIP-1 Zero-Egress AI & MCP Firewall is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the SHULIAK SIP-1 Zero-Egress AI & MCP Firewall server under?

SHULIAK SIP-1 Zero-Egress AI & MCP Firewall declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the SHULIAK SIP-1 Zero-Egress AI & MCP Firewall server?

VerifyMCP ran 15 checks on SHULIAK SIP-1 Zero-Egress AI & MCP Firewall, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about SHULIAK SIP-1 Zero-Egress AI & MCP Firewall: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.