A
licenseNot graded
qualityF
maintenanceConstitutional MCP server enforcing 13 Floors of governance for AI agents, providing tools for session anchoring, reasoning, safety critique, and audit logging.
AGPL 3.0
arifOS MCP Server
by ariffazil
Related Servers
Alternatives to arifOS MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceGovernance framework for LLM agents. Exposes seven mechanically-enforced rules plus tools for preflight file protection, audit-chain verification, session handoff and worklog templates, MCP config auditing, and an emergency kill switch.1236 npm4MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to reason about the ACF governance standard for autonomous AI agents, providing structured assessments, regulatory compliance checks, and doctrine-based tools via MCP.189 npmMIT
- AlicenseAqualityBmaintenanceUniversal governance layer for AI agents — MCP-native, fail-closed, LNN interpretability. Governed receipts, IPFS audit proofs, and rollback for any agent in any framework.339 npmApache 2.0
- AlicenseAqualityFmaintenanceProvides 14 MCP tools for AI agent infrastructure, enabling knowledge base queries, skill search, handoffs, blueprint validation, trust scoring, identity verification, SLA validation, and compliance checks.22MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with a Git-native organizational governance system, supporting proposal-validation workflows, decision-making, and audit trail management through 21 MCP tools over stdio transport.1MIT
TDQS
A3.6/5.0
Scored across 11 tools
Disambiguation5/5
Each tool has a distinct and clearly defined purpose within the kernel's lifecycle: from session initiation (arif_init) through observation, reasoning, ethical critique, judgment, sealing, composition, execution, and memory management. The only potential overlap between arif_route and arif_bridge_connect is explicitly resolved by preferring arif_route. All other tools are uniquely scoped with no ambiguity.
Naming Consistency4/5
All tools follow the 'arif_<verb>' pattern, with most verbs being single words (e.g., compose, judge, seal). The sole exception is 'arif_bridge_connect', which uses a compound verb. This minor inconsistency slightly detracts from the overall uniformity, but the pattern is otherwise consistent and predictable.
Tool Count5/5
With 11 tools, arifOS covers the full gamut of operations for a sophisticated governance kernel without being excessive. Each tool serves a clear and necessary role in the agent's workflow, from initialization to immutable sealing. The count feels well-scoped for the intended domain.
Completeness4/5
The tool set covers the major stages of the decision and execution pipeline: init, observe, think, critique, judge, seal, compose, forge, memory, route, and bridge. This provides a cohesive workflow. Missing are utility tools like listing or unsealing, but these are not central to the core lifecycle, so the gap is minor.
Maintenance
ActivityNo data
ResponsivenessWithin a week