@shuliak-corp/sip1-mcp
Related Servers
Alternatives to @shuliak-corp/sip1-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables agents to encrypt and sanitize sensitive data such as credentials, credit card numbers, and addresses locally before dispatching prompts to cloud LLMs, then rehydrate the masked values client-side. It runs deterministically with zero external dependencies over MCP JSON-RPC stdio, so no plaintext PII leaves the user's machine.-
- AlicenseNot gradedqualityCmaintenanceA security MCP proxy that monitors and blocks data exfiltration between AI agents and their tools by detecting toxic flows (untrusted → sensitive → egress) deterministically with zero LLM calls in the decision path.1MIT
- AlicenseAqualityBmaintenanceEnables sub-millisecond pre-execution safety filtering for AI agent tool calls, blocking destructive shell commands, dangerous SQL mutations, credential access, SSRF, and scope-creep or prompt-injection patterns before they execute, with optional fail-closed transparent proxy wrapping for any MCP server.658 npm12Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP servers and local AI agents to safely interact with host environments by blocking indirect prompt injections, directory traversal, and malicious shell commands.MIT

Rohan Shieldofficial
AlicenseAqualityBmaintenanceAn in-memory security MCP server for AI agents and coding copilots that prevents sensitive tool parameters and API keys from leaking into LLM context windows. Isolates execution arguments in local RAM using ephemeral cryptographic commitments and deterministic memory zeroization.48MIT- AlicenseNot gradedqualityDmaintenanceAdaptive security for AI agents: assess inputs for prompt injection, scan outputs for credential/PII leaks, teach new attack patterns to semantic memory, harden prompts, and monitor metrics. Runs locally via MCP stdio.129 PyPIApache 2.0
TDQS
Scored across 5 tools
Each tool targets a distinct operation: audit (vulnerability inspection), scrub (redaction/pseudonymization), rehydrate (inverse restoration), generate_aibom (attestation), and license_status (licensing). The scrub/rehydrate inverse pair and audit/scrub both touching payloads create mild potential for confusion, but the descriptions make the boundary between inspection vs. redaction clear.
All tools share a consistent sip1_ prefix, and four follow a clear verb_noun pattern (audit_jsonrpc, generate_aibom, rehydrate_response, scrub_payload). sip1_license_status deviates by being a noun-status form rather than a verb, a minor inconsistency.
Five tools is well-scoped for a security/compliance utility surface, with each tool earning a distinct place in the scrub/audit/attest/license workflow. No redundant or filler tools.
The surface covers the core lifecycle: scrubbing, rehydration of twins, payload auditing, compliance artifact generation, and license management. Minor gaps exist (e.g., no explicit tool to verify a generated AIBOM signature or configure scrubbing policy), but core workflows are covered.