Skip to content

arifOS MCP server

io.github.ariffazil/arifosariffazilstreamable-httpv1!2026.11.13.post1Scanned

Constitutional authority plane for AI agents — verifies identity and authority before execution.

9 tools: 3 can delete or cancel things and 6 change things.

Tools: 3 delete, 0 irreversible, 6 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • 8 findings

Tools listed without sign-in. Remote posture

Anlyon alternative

9 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the arifOS MCP server can do

The arifOS MCP server is published by the GitHub account ariffazil. It has 9 tools. It can delete or cancel things (3 tools: arif_memory, arif_forge and arif_seal) and create or change data (6 tools: arif_init, arif_observe, arif_think, arif_route and 2 more). None of its tools only reads.

1 tool brings in text other people can write (arif_observe); 1 tool can send data out of your system (arif_observe).

The fixed checks matched 8 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 13, 2026, version 1!2026.11.13.post1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Deletes or cancels 3Claude Code: deny
  • arif_forgeExecute an action arif_judge has already SEALed — nothing runs without seal_verdict_id and approved_action_hash matching the judged action.No findings

    Why it is in this group

    • The description's first verb is "execute": a word for a change.
    • The description says "Irreversible".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Execute an action arif_judge has already SEALed — nothing runs without seal_verdict_id and approved_action_hash matching the judged action. Modes: engineer (default; plan and apply — requires manifest), dry_run (preview, no side effects; manifest or query), query (read-only), write (write files), generate (generate code/content), commit (commit prepared work), recall (retrieve past forge artifacts). Irreversible judged actions additionally require ack_irreversible=true. On missing seal or hash mismatch the call returns REFUSED with no change made. Outputs: execution receipt (receipt_id, status, actor_id, timestamp).

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: 777 Forge · Execute Gate
  • arif_memoryPersistent institutional knowledge across sessions — store, recall, and curate lessons, decisions, and context so later sessions inherit them.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Persistent institutional knowledge across sessions — store, recall, and curate lessons, decisions, and context so later sessions inherit them. Modes: recall (semantic search, default), inspect (read one memory in full), attest (vouch for its accuracy), remember (store a self-contained lesson), promote (move up a tier), revise (replace its text), forget (remove — gated), audit (integrity scan), metabolize (compact and consolidate tiers). Use to carry knowledge forward between sessions; NOT for fresh external facts (arif_observe) and NOT for permanent audit receipts — those are arif_seal appends to the VAULT999 ledger, which can never be edited, whereas memory entries are revisable by design. Tiers L1 (hot working memory) → L6 (sealed canon). Behavior: reads (recall/inspect/audit) are side-effect-free; writes (remember/promote/revise/metabolize) mutate memory state; promote and forget refuse without human_approval=true — only the human owner may destroy memory. Requires a valid arif_init session. Outputs: scoped memory entries with tier and provenance.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Memory Governor · Kernel
  • arif_sealAppends a receipt to the VAULT999 immutable ledger.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The input schema at properties.session_token.description mentions "credential".

      Matched text

      inputSchema.properties.session_token.description: "Session Continuity Token (SCT) — the credential string arif_init returned alongside ses..."

      What this check looks for
    Description, as the server wrote it
    Appends a receipt to the VAULT999 immutable ledger. This is NOT a verdict and does not authorize anything — verdicts come only from arif_judge. Modes: seal (default; permanent append, requires payload and seal_purpose), verify (check one entry), ledger (read the ledger head), changelog (recent appends), audit (integrity check), session_close (close out a session into the ledger). Write modes require ack_irreversible=true. Outputs: immutable ledger entry receipt.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: 999 Seal · VAULT999
Changes things 6Claude Code: ask
  • arif_initIgnite or resume a governed session.2 findings

    Why it is in this group

    • The name "arif_init" says "init": a word for a change.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...nue active session), validate (re-check credentials), canary (transport probe), triage (rea..."

      What this check looks for
    • Info

      The input schema at properties.mode.description mentions "credentials".

      Matched text

      inputSchema.properties.mode.description: "...ion in session_id; 'validate' re-checks credentials; 'canary' is a transport probe; 'triage..."

      What this check looks for
    Description, as the server wrote it
    Ignite or resume a governed session. Returns session_id and session_token required for subsequent operations. Modes: init (default new session), preflight (inspect existing session state), resume (continue active session), validate (re-check credentials), canary (transport probe), triage (read session state), epoch_open/epoch_seal (bracket a long working window), light (minimal session), opt_out (privacy opt-out). Outputs: session credentials and allowed next tools. To END a governed session, call arif_seal(mode=session_close) — session closure is a ledger event, not an init mode.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: 000 Init · Kernel Session
  • arif_judgeEvaluate proposed operations and claims against constitutional policy and safety constraints.2 findings

    Why it is in this group

    • The description's first verb is "evaluate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The input schema at properties.authority_token.description mentions "credential".

      Matched text

      inputSchema.properties.authority_token.description: "Authority credential CLAIMED for this proposal (payload fiel..."

      What this check looks for
    • Warn

      The server marks "arif_judge" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "evaluate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Evaluate proposed operations and claims against constitutional policy and safety constraints. Weighs blast radius, reversibility, and authority tier to render a binding verdict: SEAL (approved for forge execution), HOLD (blocked/escalate to sovereign human), SABAR (cooling/backoff), or VOID (permanently refused). Modes: judge (default; evaluate candidate against all 13 floors), intercept (pre-flight gate before action dispatch), validate (re-check a prior verdict), hold (place action into cooling period), escalate (refer decision to human owner). Use when you have formulated a candidate plan/action and need an authoritative verdict; a SEAL verdict_id is strictly required before calling arif_forge. NOT for executing actions (use arif_forge after SEAL), NOT for gathering facts (use arif_observe), NOT for open-ended reasoning (use arif_think). Read-only: evaluates without mutating workspace state. Requires candidate (the proposal under judgment) and an active session from arif_init. Outputs: binding verdict, floor compliance matrix, and authorization receipt.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: 888 Judge · Verdict
  • arif_observeSense reality into sourced evidence — gather external facts with provenance, the kernel's sensing verb.Reads text others writeCan send data out1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Info

      The input schema at properties.session_token.description mentions "credential".

      Matched text

      inputSchema.properties.session_token.description: "Session Continuity Token (SCT) — the credential string arif_init returned alongside ses..."

      What this check looks for
    Description, as the server wrote it
    Sense reality into sourced evidence — gather external facts with provenance, the kernel's sensing verb. Run it before arif_think or arif_judge so decisions rest on sourced facts. Modes: search (web/literature query, default), fetch (one URL with provenance), hybrid_discovery (combine sources), ingest (absorb a document), compass/atlas (guided navigation), entropy_dS (measure system change), vitals (kernel machine telemetry), resource_read (read a registered arifos:// resource), resource_search (list registered resources). Use for fresh external facts or live system state; NOT for stored institutional knowledge (arif_memory recall) or organ dispatch (arif_route). Read-only and idempotent — writes nothing; every result carries source attribution and an epistemic tag (OBS/DER/INT). Requires a valid arif_init session; unauthenticated calls are refused. Outputs: structured facts with provenance and uncertainty labels.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
    • title: 111 Observe · Sense Reality
  • arif_reportAGENT REPORT LANE · File or read reports between agents without involving the human.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    AGENT REPORT LANE · File or read reports between agents without involving the human. Use when your work is done, when you are blocked by another agent, or when you need to tell peers a fact. Modes: report (file), inbox (read peers), ack, flush, stats. kind=fyi|peer|done|claim stay in the peer lane; ONLY kind=decision or kind=blocked reach the sovereign, and only in one coalesced message. Reports are SELF_REPORTED — probe before relying on one. Not for constitutional verdicts, sealing, or mutations — use the canonical verbs (arif_init … arif_seal); this lane coordinates, it never governs. Behavior: filing appends to an agent-only store (never the VAULT999 ledger); reads are side-effect-free; dry_run=true validates without storing. Requires a session from arif_init. Outputs: the filed report record (mode=report), or the inbox/ack/flush/stats payload for the other modes.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Agent Report Lane · Peer Coordination
  • arif_routeClassify an intent and route it to the organ that owns it — GEOX (Earth science), WEALTH (capital markets), WELL (human vitality), A-FORGE (execution), or the arifOS kernel itself.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The input schema at properties.session_token.description mentions "credential".

      Matched text

      inputSchema.properties.session_token.description: "Session Continuity Token (SCT) — the credential string arif_init returned alongside ses..."

      What this check looks for
    Description, as the server wrote it
    Classify an intent and route it to the organ that owns it — GEOX (Earth science), WEALTH (capital markets), WELL (human vitality), A-FORGE (execution), or the arifOS kernel itself. Modes: route (default; classify and recommend), triage (rank a batch of intents), delegate (prepare an A2A handoff), status (organ state), kernel (kernel-level status), metabolize (feed routing outcomes to arifFlow). Use when a task belongs to a specialized organ and you need a dispatch envelope or organ health before acting; supply organ_tool + arguments to bridge one call through to the organ. Routing RECOMMENDS only — it never executes: for execution obtain an arif_judge SEAL, then call arif_forge. Not for general reasoning (arif_think). Read-only unless organ_tool is supplied. Requires a valid arif_init session. Outputs: organ dispatch envelope with recommended organ and tool.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: 444 Route · Intent→Organ
  • arif_thinkStructured reasoning and plan formulation — decomposes a question or claim into labeled derivations (OBS/DER/INT) before you act.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The input schema at properties.session_token.description mentions "credential".

      Matched text

      inputSchema.properties.session_token.description: "Session Continuity Token (SCT) — the credential string arif_init returned alongside ses..."

      What this check looks for
    Description, as the server wrote it
    Structured reasoning and plan formulation — decomposes a question or claim into labeled derivations (OBS/DER/INT) before you act. Modes: reason (inquiry breakdown, default), reflect (self-review of prior reasoning), verify (check a derivation), axioms (surface hidden assumptions), plan/plan_review/plan_approve/refactor_plan (execution-plan lifecycle), metabolize (consolidate past reasoning), simulate (what-if), wonder (open exploration), atlas (map the problem space). Use to prepare evidence chains and plans BEFORE arif_judge or arif_forge — pass the returned plan_id to arif_forge when executing an approved plan. NOT for gathering facts (arif_observe), dispatching to organs (arif_route), or issuing verdicts (arif_judge — think never issues them). Pure reasoning: mutates no state and calls no external systems; its output is a reasoning record, not ground truth. Requires a valid arif_init session. Outputs: structured reasoning record with epistemic labels.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: 333 Think · Mind

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:02 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
9
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.arif-fazil.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://mcp.arif-fazil.com
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 9 tools that change things (3 destructive, 6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.arif-fazil.com/mcp: tools/list returned 9 tools to an anonymous client, including arif_memory (destructive), arif_forge (destructive), arif_seal (destructive), arif_init (write), arif_observe (write) and 4 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn7 info
  • The server marks "arif_judge" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "evaluate": a word for a change.

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...nue active session), validate (re-check credentials), canary (transport probe), triage (rea..."

    What this check looks for
  • The input schema at properties.mode.description mentions "credentials".

    Matched text

    inputSchema.properties.mode.description: "...ion in session_id; 'validate' re-checks credentials; 'canary' is a transport probe; 'triage..."

    What this check looks for
  • The input schema at properties.session_token.description mentions "credential".

    Matched text

    inputSchema.properties.session_token.description: "Session Continuity Token (SCT) — the credential string arif_init returned alongside ses..."

    What this check looks for
  • The input schema at properties.session_token.description mentions "credential".

    Matched text

    inputSchema.properties.session_token.description: "Session Continuity Token (SCT) — the credential string arif_init returned alongside ses..."

    What this check looks for
  • The input schema at properties.session_token.description mentions "credential".

    Matched text

    inputSchema.properties.session_token.description: "Session Continuity Token (SCT) — the credential string arif_init returned alongside ses..."

    What this check looks for
Show 2 more findings
  • The input schema at properties.authority_token.description mentions "credential".

    Matched text

    inputSchema.properties.authority_token.description: "Authority credential CLAIMED for this proposal (payload fiel..."

    What this check looks for
  • The input schema at properties.session_token.description mentions "credential".

    Matched text

    inputSchema.properties.session_token.description: "Session Continuity Token (SCT) — the credential string arif_init returned alongside ses..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools9 changed.~9 changedView diff
    • Changed:arif_forgeDeletes or cancelsdescriptioninputSchema
    • Changed:arif_initChanges thingsdescriptioninputSchema
    • Changed:arif_judgeChanges thingstitledescriptioninputSchemaannotations
    • Changed:arif_memoryDeletes or cancelsdescriptioninputSchema
    • Changed:arif_observeChanges thingsdescription
    • Changed:arif_reportChanges thingstitledescriptioninputSchemaannotations
    • Changed:arif_routeChanges thingsdescriptioninputSchema
    • Changed:arif_sealDeletes or cancelsdescriptioninputSchema
    • Changed:arif_thinkChanges thingsdescriptioninputSchema
  2. Tools8 changed.~8 changedView diff

Install

Pinned to version 1!2026.11.13.post1. Values in angle brackets are yours to fill in.

claude mcp add --transport http arifos https://mcp.arif-fazil.com/mcp
claude mcp add --transport http arifos https://mcp.arif-fazil.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__arifos__arif_init",
      "mcp__arifos__arif_observe",
      "mcp__arifos__arif_think",
      "mcp__arifos__arif_route",
      "mcp__arifos__arif_judge",
      "mcp__arifos__arif_report"
    ],
    "deny": [
      "mcp__arifos__arif_memory",
      "mcp__arifos__arif_forge",
      "mcp__arifos__arif_seal"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as arifos. Review it before you use it.

Capability tags behind 1 rule
  • mcp__arifos__arif_observe untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ariffazil/arifos/verify?hash=f8f18ac16e8768974f36ce1e92f852e80c2e2564d82fac42408af347dd7eae3b" | jq -e '.changed == false'

Pinned hash f8f18ac16e87, from Nov 13, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.ariffazil/arifos/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.ariffazil/arifos
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.ariffazil/arifos.svg)](https://radar.anlyon.com/servers/io.github.ariffazil/arifos)

Source: MCP Registry · repository. Synced Nov 13, 2026, 13:17 UTC.

arifOS MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the arifOS MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 9 of which can change, send or delete something, and 8 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the arifOS MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: arif_memory, arif_forge and arif_seal.

Can the arifOS MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the arifOS MCP server have?

9 tools: 3 destructive, 6 write. arif_memory, arif_forge, arif_seal, arif_init, arif_observe, arif_think, arif_route, arif_judge and 1 more.

Does the arifOS MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the arifOS MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): arif_observe.

Has the arifOS MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.