Arifos MCP Server

arifos PyPI v1!2026.8.2

Published by ariffazil — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

mcp-name: io.github.ariffazil/arifos | .ariffazil/arifos | arifOS v1!2026.7.26 — Constitutional AI Governance Kernel. 8 kernel ABI capabilities → 6 public tools (arif_verb_noun, generated from arifosmcp/abi/capability_registry.json), dynamic F1-F13 enforcement via ConstitutionKernel + FloorEvaluator, VAULT999 immutable ledger, streamable-http MCP transport. Kernel substrate for AGI/ASI federation.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 12

high Reads a sensitive credential path or dumps the environment (arifosmcp/core/ssh_proof.py)MTC-SRC-006

In the server's implementation (`arifosmcp/core/ssh_proof.py:16`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: EY: Local /root/.ssh/id_ed25519 → direct signing (VPS-local) - FALLBACK: None → OBSERVER (read-only, no soverei

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server arifosmcp/core/ssh_proof.py

high Shell/command execution in server code (arifosmcp/arifos_attestation/sbom_scan.py)MTC-SRC-002

In the server's implementation (`arifosmcp/arifos_attestation/sbom_scan.py:49`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: out = subprocess.run( ["pip", "list", "--format=json"], capture_output

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server arifosmcp/arifos_attestation/sbom_scan.py

high Shell/command execution in server code (arifosmcp/cli/common.py)MTC-SRC-002

In the server's implementation (`arifosmcp/cli/common.py:60`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: stderr).""" proc = subprocess.run( ["git", *args], cwd=cwd, capture_output=True, te

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server arifosmcp/cli/common.py

high Shell/command execution in server code (arifosmcp/core/aaa_bridge.py)MTC-SRC-002

In the server's implementation (`arifosmcp/core/aaa_bridge.py:186`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ). MXC equivalent: exec() """ payload = { "agent_id": agent_id, "tool_name": tool_name,

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server arifosmcp/core/aaa_bridge.py

high Shell/command execution in server code (arifosmcp/core/law.py)MTC-SRC-002

In the server's implementation (`arifosmcp/core/law.py:109`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: udo", "chmod", "eval", "exec(", "__import__"] if any(m in value for m in manipulation):

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server arifosmcp/core/law.py

high Shell/command execution in server code (arifosmcp/core/paradox/recursive_governance_locks.py)MTC-SRC-002

In the server's implementation (`arifosmcp/core/paradox/recursive_governance_locks.py:532`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: e" result = subprocess.run( ["gemini", "-p", prompt], capture_output=True,

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server arifosmcp/core/paradox/recursive_governance_locks.py

high Shell/command execution in server code (arifosmcp/core/ssh_proof.py)MTC-SRC-002

In the server's implementation (`arifosmcp/core/ssh_proof.py:121`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: result = subprocess.run( [SSH_KEYGEN_PATH, "-lf", tmp.name], capture_output=True, tex

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server arifosmcp/core/ssh_proof.py

high Shell/command execution in server code (arifosmcp/core/threat_engine.py)MTC-SRC-002

In the server's implementation (`arifosmcp/core/threat_engine.py:121`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ion select", "or 1=1", "exec(", "execute("] SHELL_INJECTION = [ "; rm", "&& rm", "| sh",

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server arifosmcp/core/threat_engine.py

high Shell/command execution in server code (arifosmcp/evals/deploy_gate.py)MTC-SRC-002

In the server's implementation (`arifosmcp/evals/deploy_gate.py:146`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: y: result = subprocess.run( ["git", "rev-parse", "HEAD"], capture_output=True, text=True, ti

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server arifosmcp/evals/deploy_gate.py

high Shell/command execution in server code (arifosmcp/evals/e2e_golden_paths.py)MTC-SRC-002

In the server's implementation (`arifosmcp/evals/e2e_golden_paths.py:80`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: s result = subprocess.run( ["git", "rev-parse", "HEAD"], capture_output=True, text=True, ti

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server arifosmcp/evals/e2e_golden_paths.py

medium Dynamic module load from a non-literal (arifosmcp/federation/constitution_aggregator.py)MTC-SRC-005

In the server's implementation (`arifosmcp/federation/constitution_aggregator.py:146`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: organ_id] mod = __import__(cfg["health_module"], fromlist=[cfg["health_fn"]]) fn = getattr(mod, cfg["hea

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server arifosmcp/federation/constitution_aggregator.py

low Shell/command execution in packaging/dev tooling (arifosmcp/evals/mcp_inspector_test.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`arifosmcp/evals/mcp_inspector_test.py:141`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: y: result = subprocess.run( ["git", "rev-parse", "HEAD"], capture_output=True, text=True, ti

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server arifosmcp/evals/mcp_inspector_test.py

Tools 48

Each tool and what it can reach — statically extracted from the published source.

  • arif_cc_evidence_fetchingests untrusted input
  • arifos_oracle_worldingests untrusted input
  • arif_cc_forge_dry_runno sensitive capability
  • arif_cc_gateway_handshakeno sensitive capability
  • arif_cc_heart_critiqueno sensitive capability
  • arif_cc_judge_actionno sensitive capability
  • arif_cc_memory_recallno sensitive capability
  • arif_cc_mind_reasonno sensitive capability
  • arif_cc_ops_vitalsno sensitive capability
  • arif_cc_reply_composeno sensitive capability
Show 38 more tools ↓
  • arif_cc_sense_observeno sensitive capability
  • arif_cc_session_statusno sensitive capability
  • arif_cc_vault_dry_sealno sensitive capability
  • arif_cc_vault_listno sensitive capability
  • arif_claim_gateno sensitive capability
  • arif_judge_consoleno sensitive capability
  • arif_kernel_checkno sensitive capability
  • arif_kernel_healthno sensitive capability
  • arif_ops_dashboardno sensitive capability
  • arifos_compute_civilizationno sensitive capability
  • arifos_compute_financeno sensitive capability
  • arifos_compute_physicsno sensitive capability
  • arifos_verify_locationno sensitive capability
  • forge_dry_runno sensitive capability
  • G02_omega_statusno sensitive capability
  • G02_routeno sensitive capability
  • G02_validate_axis_callno sensitive capability
  • gateway_handshakeno sensitive capability
  • judge_actionno sensitive capability
  • mcp_health_checkno sensitive capability
  • metabolic_vitalsno sensitive capability
  • ops_vitalsno sensitive capability
  • session_statusno sensitive capability
  • vault_dry_sealno sensitive capability
  • vault_listno sensitive capability
  • wealth_boundary_governanceno sensitive capability
  • wealth_conservation_capitalno sensitive capability
  • wealth_energy_productivityno sensitive capability
  • wealth_entropy_riskno sensitive capability
  • wealth_field_macrono sensitive capability
  • wealth_flow_liquidityno sensitive capability
  • wealth_game_coordinationno sensitive capability
  • wealth_gradient_priceno sensitive capability
  • wealth_hysteresis_ledgerno sensitive capability
  • wealth_inertia_leverageno sensitive capability
  • wealth_signal_informationno sensitive capability
  • wealth_system_registry_statusno sensitive capability
  • wealth_time_discountno sensitive capability

What this scan could not see

Versions 4

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1!2026.8.2 latest A 93/100 12 1.13.0 2026-08-25
v1!2026.7.26 A 93/100 13 1.12.1 2026-07-27
v1!2026.7.24 A 93/100 13 1.10.0 2026-07-25
v1!2026.7.17.post4 A 93/100 13 1.9.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/arifos/badge.svg)](https://mcptrustchecker.com/registry/arifos)
HTML
<a href="https://mcptrustchecker.com/registry/arifos"><img src="https://mcptrustchecker.com/registry/arifos/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/arifos/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan arifos --online --registry pypi

Use the free API → How scoring works

More in Developer Tools