Remote MCP · Endpoint
arifOS — Constitutional AI Kernel MCP server
No. arifOS — Constitutional AI Kernel answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://arifos.arif-fazil.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.ariffazil/arifos
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 785 ms
- Tools exposed
- 9 tools
- Uptime, last 30 days
- 55.6% from 18 checks
- Described by its publisher as
- Constitutional AI kernel with 13 MCP tools, 888_JUDGE verdict pipeline, and VAULT999 ledger.
- Repository
- https://github.com/ariffazil/arifOS
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 785 ms |
| 1 day ago | Handshake completed | 787 ms |
| 2 days ago | Handshake completed | 359 ms |
| 3 days ago | Handshake completed | 860 ms |
| 4 days ago | Handshake completed | 2.48 s |
| 5 days ago | Handshake completed | 794 ms |
| 6 days ago | Handshake completed | 858 ms |
| 9 days ago | Handshake completed | 805 ms |
| 11 days ago | Handshake completed | 769 ms |
| 14 days ago | Handshake completed | 780 ms |
| 16 days ago | Failed - the server rejected the MCP handshake | — |
| 18 days ago | Failed - the server rejected the MCP handshake | — |
| 20 days ago | Failed - the server rejected the MCP handshake | — |
| 22 days ago | Failed - the server rejected the MCP handshake | — |
| 24 days ago | Failed - the server rejected the MCP handshake | — |
| 26 days ago | Failed - the server rejected the MCP handshake | — |
| 27 days ago | Failed - the server rejected the MCP handshake | — |
| 28 days ago | Failed - the server rejected the MCP handshake | — |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with arifOS — Constitutional AI Kernel and makes no claim about it beyond what these checks measured.