Nervous System
Related Servers
Alternatives to Nervous System
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceGoverned 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
Habenulaofficial
AlicenseNot gradedqualityCmaintenanceA personal agent control harness that governs AI agents by checking every consequential action against user-defined rules, logging all actions to a tamper-evident audit chain, and providing a global kill switch. It runs as an MCP server sidecar to coding agents or standalone, keeping users in charge of what their agents can do.4AGPL 3.0- AlicenseBqualityAmaintenanceA governance proxy for AI tools — every MCP/agent tool call is policy-gated, secret-redacted, and written to a hash-chained, offline-verifiable audit trail.13MIT
- AlicenseNot gradedqualityDmaintenanceQuantitative governance gate for AI agents. Six gates (risk, profit, novelty, complexity, quality, utility) return PROCEED/PAUSE/HALT/ESCALATE with confidence scores and hash-chained, tamper-evident audit trails. Generates NIST AI RMF and EU AI Act Annex IV artifacts. 10 MCP tools; local stdio and hosted Streamable HTTP with a free tier.MIT
- AlicenseNot gradedqualityFmaintenanceGovernance kernel for AI agents — policy enforcement, code safety verification, multi-model hallucination detection (CMVK), trust attestation (IATP), and immutable audit trails. Works with Claude Desktop, Cursor, and any MCP client.74MIT
- 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.301MIT
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose. The 'get_*' tools all retrieve different templates or info, and the action-oriented tools (audit, check, dispatch, kill, verify) are easily distinguishable from each other. There is no overlap or ambiguity.
Most tools follow a verb_noun pattern (e.g., audit_mcp_config, get_dispatch_template). However, a few exceptions like 'dispatch_to_llm' (includes preposition) and 'emergency_kill_switch' (adjective-noun) break the pattern slightly, making it mostly consistent with minor deviations.
With 12 tools, the set is well-scoped for a governance/agent management system. Each tool addresses a specific need: configuration auditing, file protection, agent dispatch/stop, template retrieval, system info, and audit verification. No tool seems unnecessary or overly niche.
The tool set covers core governance, auditing, and agent dispatching well. Notable minor gaps include the lack of a tool to list running agents or check agent status, which might be expected in a system that dispatches agents. However, the existing tools cover the primary workflows.