@altirs/mcp-server
Related Servers
Alternatives to @altirs/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides prompt injection detection, PII/secrets redaction, and an audit trail for AI agents via MCP tools.4MIT
- AlicenseNot gradedqualityBmaintenanceLets MCP-compatible assistants vet inbound prompts and untrusted text for instruction-override manipulation, separator escapes, and concealed encodings before processing them. Additional inline controls cover spending limits, repetitive-plan interruption, unsafe host-action denial, and output sanitization without third-party libraries.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients and autonomous agents to screen incoming prompts for system overrides, delimiter breakouts, and encoded payload evasion, helping block prompt injection and jailbreak attempts before execution.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI agents to scan code for leaked secrets, copyleft licenses, unprotected routes, missing privacy policies, and risky card handling before committing or shipping.81 npmMIT
- AlicenseNot gradedqualityDmaintenanceRuntime safety guardrails for AI coding agents. Checks file access, validates shell commands, and scores your repo's AI safety — all via MCP.6 npm8MIT
- FlicenseNot gradedqualityBmaintenanceEnables autonomous AI agents and MCP-compliant clients to detect and block adversarial prompt injections, jailbreak attempts, system prompt exfiltration, and tool hijacking via a zero-dependency, sub-millisecond heuristic firewall.7-
TDQS
Scored across 5 tools
check_content is a composite that overlaps with detect_pii, scan_injection, and check_safety, but its description clearly positions it as the default all-in-one gate, while the individual tools are for targeted use. check_hallucination is distinct because it requires source context.
Most tools follow a verb_noun pattern (check_content, detect_pii, scan_injection, check_safety, check_hallucination). scan_injection deviates slightly from the check_* prefix used by the other three check tools, but the pattern is still readable and predictable.
Five tools is a well-scoped set for a content-safety server. Each tool covers a distinct safety engine, with check_content serving as the umbrella entry point and the others providing focused checks.
The server covers the main guardrail categories: safety, PII, injection, and hallucination. A minor gap is the lack of a dedicated tool for updating or managing guardrail configurations, but the core detection surface is complete for its stated purpose.