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 — Constitutional AI Governance
Server Details
Constitutional AI governance: 11 mega-tools, 13 floors, VAULT999 ledger. Human-in-loop by design.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- ariffazil/arifOS
- GitHub Stars
- 51
- Server Listing
- arifOS MCP Server
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
arif_mind_reason1 field changed- added
Input schema / properties / ctxAdded value: +{ + "default": null, + "title": "Ctx" +}
1 tool update
- Changed
arif_memory_recall3 fields changed- removed
Input schema / properties / areaRemoved value: -{ - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "default": null -} - removed
Input schema / properties / contentRemoved value: -{ - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "default": null -} - removed
Input schema / properties / project_idRemoved value: -{ - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "default": null -}
1 tool update
- Changed
arif_memory_recall3 fields changed- added
Input schema / properties / areaAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null +} - added
Input schema / properties / contentAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null +} - added
Input schema / properties / project_idAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null +}
5 tool updates
- Removed
command_center - Removed
get_constitutional_health - Removed
list_recent_verdicts - Removed
render_vault_seal - Removed
vault_seal_card
1 tool update
- Changed
command_center1 field changed- changed
Output schema / (root)Previous value: -{ - "properties": { - "result": { - "type": "null" - } - }, - "required": [ - "result" - ], - "type": "object", - "x-fastmcp-wrap-result": true -}New value: +null
5 tool updates
- Added
command_center - Added
get_constitutional_health - Added
list_recent_verdicts - Added
render_vault_seal - Added
vault_seal_card
1 tool update
- Changed
arif_session_init2 fields changed- added
Input schema / properties / actor_signatureAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null +} - added
Input schema / properties / nonceAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null +}
4 tool updates
- Changed
arif_heart_critique1 field changed- added
Input schema / properties / evidence_receiptAdded value: +{ + "anyOf": [ + { + "additionalProperties": true, + "type": "object" + }, + { + "type": "null" + } + ], + "default": null +}
- Changed
arif_judge_deliberate2 fields changed- added
Input schema / properties / claimed_evidence_levelAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null +} - added
Input schema / properties / evidence_receiptAdded value: +{ + "anyOf": [ + { + "additionalProperties": true, + "type": "object" + }, + { + "type": "null" + } + ], + "default": null +}
- Changed
arif_session_init1 field changed- added
Input schema / properties / declared_model_keyAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null +}
- Removed
command_center
1 tool update
- Added
command_center
1 tool update
- Changed
arif_memory_recall1 field changed- added
Input schema / properties / metadataAdded value: +{ + "anyOf": [ + { + "additionalProperties": true, + "type": "object" + }, + { + "type": "null" + } + ], + "default": null +}
1 tool update
- Changed
arif_session_init1 field changed- added
Input schema / properties / previous_session_hashAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null +}
7 tool updates
- Removed
forge_dry_run - Removed
gateway_handshake - Removed
judge_action - Removed
ops_vitals - Removed
session_status - Removed
vault_dry_seal - Removed
vault_list
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Constitutional AI kernel with 13 MCP tools, 888_JUDGE verdict pipeline, and VAULT999 ledger.
Runtime AI governance: decision gates, human approval, hash-chained audit, compliance mapping.
Six-gate governance for AI agents: PROCEED/PAUSE/HALT decisions with hash-chained audit trails.
Multi-agent governance: task orchestration, compliance, decision validation, and ML predictions.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables governance and orchestration of VaultMesh deployments through subsystem spawning, multi-chain anchoring, threat mitigation, constitutional amendments, and LAWCHAIN governance tracking. Provides auditable tools for managing decentralized infrastructure with cryptographic proofs and alchemical phase orchestration.-
- AlicenseNot gradedqualityBmaintenanceRuntime constitutional verification for AI answers — claim extraction with reasoning chains, Epistemic Confidence Score (ECS), 7-angle Glassbox Court red team, constitution compilation, Trust Card assembly, and deterministic SHA-256 audit logs.11Apache 2.0
- AlicenseAqualityCmaintenanceAI agent provenance, trust, and auditability layer. VERITAS multi-gate scoring, Cortex approval gates, S.E.A.L. hash-chain audit ledger, and semantic RAG with cryptographic provenance tracking for every decision an agent makes.275MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.3/5.0
Disambiguation5/5
Each tool targets a distinct core function (sensing, reasoning, memory, routing, critique, judging, forging, vaulting, etc.), with modes further differentiating operations. There is no meaningful overlap between tools; even 666_HEART and 666_GATEWAY serve clearly separate purposes.
Naming Consistency5/5
All tool names follow a strict arif_{verb}_{noun} pattern with consistent snake_case. The prefix 'arif_' is uniform, and verbs like sense, mind, memory, kernel, heart, judge, forge, vault clearly indicate the action.
Tool Count5/5
13 tools is appropriate for a comprehensive constitutional governance system. Each tool covers a necessary aspect of the lifecycle (init, sense, reason, route, remember, critique, judge, forge, vault, etc.) without being overwhelming or sparse.
Completeness5/5
The tool set provides complete coverage of the governance workflow: session bootstrap, observation, reasoning, orchestration, memory, ethical critique, final adjudication, immutable sealing, and execution. No obvious gaps for the stated purpose.