HallucC MCP Server
Related Servers
Alternatives to HallucC MCP Server
- AlicenseNot gradedqualityDmaintenanceEnables content moderation by checking user input against OpenAI's moderation API via Google ADK, with dual SSE/STDIO transport support and integration with local LLMs.4MIT
- AlicenseAqualityAmaintenanceMCP server exposing Verity's trust checks as tools (verify_fact, detect_injection, moderate_content, redact_pii, guard_action) that any MCP-capable agent can discover and call for fail-closed safety verification before spending or sending.822 PyPIMIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables secure interoperability between LLM agents and MCP tool servers by sanitizing requests and responses, masking sensitive tokens, detecting PII, and performing server reputation scans.MIT
- FlicenseNot gradedqualityCmaintenanceEnables safe use of any MCP server by proxying and live-scanning all tool requests and responses, blocking or redacting poison descriptions, indirect prompt injection, malicious arguments, and unauthorized destinations.-
- AlicenseNot gradedqualityAmaintenanceEnforces MCP security by proxying between AI agents and MCP servers, scanning tools and results for prompt injection, enforcing allow/deny policies, redacting sensitive arguments, and logging all traffic.MIT
- AlicenseNot gradedqualityCmaintenanceEnables secure, low-latency proxying of MCP tool calls by detecting and blocking malicious requests such as path traversals and command injections, while redacting leaked credentials.12 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to safely invoke enterprise MCP tools under an enforceable guard that applies allowlist policies, caller roles, parameter restrictions, human confirmation for destructive operations, and a correlated JSONL audit log.AGPL 3.0
- AlicenseNot gradedqualityFmaintenanceEnables transparent security for any MCP server by intercepting tool calls, blocking prompt injection attempts, masking PII in responses, and writing immutable audit logs.338 npmMIT
TDQS
Scored across 4 tools
The tools are mostly distinct, but verify_text, check_safety (with optional hallucination detection), and verify_agent all overlap on claim-level hallucination verification. check_cua_actions is clearly separate, but an agent could struggle to choose between the three text/agent verification tools without reading descriptions closely.
All tool names follow a clear lowercase snake_case verb_noun pattern with either check_ or verify_ prefixes. The naming is predictable, though the repeated verbs slightly undercut distinctiveness because verify_text and verify_agent share the same verb while having some overlapping functionality.
Four tools is a well-scoped surface for a safety/verification server. Each tool represents a distinct capability area: free-text verification, agent action safety, general prompt/output safety, and agent trajectory self-check.
The surface covers the core workflows: verifying claims, checking agent actions, scanning prompts/outputs for safety risks, and self-checking agent trajectories. Minor gaps exist—such as no dedicated quota/status tool or a more granular single-claim verification endpoint—but agents can work around these using the existing tools.