secmcp-server
Related Servers
Alternatives to secmcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides a policy-controlled MCP gateway that lets agents invoke tools with explicit policies, bounded execution, scoped visibility, and decision receipts.MIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP tool calls with strict schema validation and stdio isolation, while providing a security gateway for tool-level authorization, streaming PII redaction, and model failover routing.-
- AlicenseNot gradedqualityCmaintenanceEnables autonomous agents to securely access and manage virtual file systems, records, schemas, SQL and Mongo queries, and RAG search through scoped MCP tools, while supporting binary transfers via presigned S3 recipes.PolyForm Noncommercial 1.0.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and LLM clients to inspect sandboxed files, run read-only SQL queries, and fetch public web content through guarded MCP tools with deterministic path, SQL, SSRF, timeout, and PII protections.MIT
- AlicenseNot gradedqualityAmaintenanceEnables teams to govern agent tool access with function-level allow-lists, credential modes, and audited execution, while exposing permitted MCP tools through a unified endpoint with search and execute functions.MIT

evav-gatewayofficial
AlicenseNot gradedqualityDmaintenanceGoverned MCP gateway that lets AI agents call tools with policy enforcement, prompt-injection screening, a kill-switch, and tamper-evident signed audit logs.Apache 2.0
TDQS
Scored across 4 tools
search_docs and read_private_note both retrieve content but are separated by scope and side effect (the latter flags the session as having seen private data), which is a clear signal. send_report and http_post overlap in being egress operations, but the channel difference (email to whitelist vs HTTP POST to whitelist) is explicit enough for an agent to choose correctly.
Three of four names follow a clean verb_noun pattern (search_docs, read_private_note, send_report). http_post deviates by leading with a protocol noun rather than an action verb, a minor inconsistency but not confusing.
Four tools is on the lean side but each maps to a distinct capability (search, privileged read, email egress, HTTP egress) with no filler. The scope feels deliberately small for a policy-guarded server rather than arbitrarily truncated.
The surface covers read plus two controlled egress paths, but has notable gaps: no way to fetch a document by id (only search), no listing of available docs or notes, no http_get counterpart, and no write/update operations. Agents can work around some of this via search_docs, but dead ends exist for direct retrieval and inbound HTTP.