jev-cognitive-mcp
Related Servers
Alternatives to jev-cognitive-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to make structured local decisions, choose bounded browser actions with approvals, and run coding workflows such as file relevance, context pruning, diff screening, and completion checks through MCP or CLI.Apache 2.0
- AlicenseAqualityBmaintenanceProvides advisory AI-governance checks for MCP hosts and coding agents, enabling policy verdicts, PII masking, and audit traces before executing tool calls.344 npmMIT
- AlicenseNot gradedqualityCmaintenanceA zero-trust security gateway for MCP tool calls, inspecting tool identity, arguments, execution decisions, and returned content before risk reaches your coding agent.Apache 2.0
- AlicenseAqualityBmaintenanceEnables coding agents to perform advisory runtime safety checks by inspecting proposed file paths and shell commands, tracking caller budgets, detecting repeated actions, and masking common credentials in output without executing commands or opening target files.4GPL 3.0
- AlicenseNot gradedqualityDmaintenanceRuntime safety guardrails for AI coding agents. Checks file access, validates shell commands, and scores your repo's AI safety — all via MCP.5 npm8MIT
- AlicenseNot gradedqualityBmaintenanceEnables secure MCP agent operations by enforcing fail-closed policies, blocking dangerous tool calls, scanning outputs for prompt injection, and recording every action in a tamper-evident audit log.2MIT
TDQS
Scored across 5 tools
Each tool has a distinct core action: risk screening (guard), complexity/tier routing (route), text ranking (rerank), evidence-gap review (verify), and layer arbitration (arbitrate). The only mild overlap is between route (model tier) and arbitrate (reasoning layer), which could be confused, but descriptions distinguish them adequately.
All tools follow a strict 'jev_' prefix plus a single verb pattern (guard, route, rerank, verify, arbitrate). Fully predictable and consistent throughout.
Five tools is well-scoped for a cognitive decision-support server, with each tool earning its place as a distinct cognitive operation. No redundancy or filler.
The surface covers the main cognitive advisory steps: screen, route, rank, verify, and arbitrate. Minor gaps exist (e.g., no explicit memory/state or feedback tool), but core workflows for a decision-support layer are covered.