Ephemora Cell MCP
Related Servers
Alternatives to Ephemora Cell MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceA local, evidence-driven MCP runtime and control plane for open-source maintainers that provides workspace-bounded tools including controlled file operations, command execution, validation primitives, durable execution records, and human review workflows via stdio and Streamable HTTP transports.33MIT
- AlicenseNot gradedqualityCmaintenanceProvides an MCP stdio interface for AI agents to propose tool calls that are validated against task policy, held for human approval when required, executed in a sandboxed Linux environment, and recorded in an audit log.MIT
- AlicenseAqualityAmaintenanceAn MCP server that exposes governance, trust-scoring, compliance, guardrail, cost, drift, and supply-chain scanning tools and resources to any MCP client over stdio, Streamable HTTP, or legacy HTTP+SSE. It lets agents route every tool call through a deterministic five-way decision (allow, redact, require approval, deny, or quarantine) with hash-chained evidence, human approval workflows, and in-agent trust gates for LangChain, LangGraph, and Google ADK.3044 PyPI2MIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted MCP gateway that applies deterministic, compiled policy to tool discovery, invocation, and outbound data flow, with no model in the enforcement path. Every decision emits a hash-chained receipt sealed with Ed25519 and verifiable using public keys only.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server that executes caller-supplied Python code in a network-isolated, locked-down sandbox and returns stdout/stderr/exit code. Supports stdio, HTTP, and SSE transports with optional auth.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables developers to wrap existing MCP servers with a deterministic policy enforcement gate that intercepts tool discovery and tools/call requests over stdio, allowing only authorized calls to reach the downstream server. It supports dynamic tool exposure or hiding, allow/deny/approval-required decisions, configurable error disclosure modes, and Ed25519-signed retry credentials for approved workflows.Apache 2.0
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: clock reports time, echo echos input, and get-policy returns sandbox configuration. There is no meaningful overlap or ambiguity between them.
All names are lowercase and readable, but they mix a noun command (clock), a bare verb command (echo), and a hyphenated verb-noun command (get-policy). A uniform verb_noun pattern would be more consistent.
Three tools is minimal but each one serves a distinct purpose in the apparent sandbox/contract demo scope. The set feels slightly thin but not unreasonably so.
For a focused introspection and contract-demonstration server, the core surfaces are covered: time, I/O behavior, and policy. There are minor gaps like no policy mutation or execution tool, but no obvious dead ends within the stated purpose.