📡 MCP Radar

halofyai/halofy

Halofy is the open access and governance layer for AI agents across your organization. Identity, policy, provenance, audit, and signed erasure.

440 stars
14 forks
TypeScript
momentum ▲ 761.3
created 2026-08-22
on radar since 2026-08-25
star trend 6 → 440 since 2026-08-25
access-controlagent-governanceagent-memoryagent-visibilityai-agentsaudit-logcontext-engineeringdata-governancedata-provenanceidentity-managementknowledge-managementmodel-context-protocolmulti-agent-systemsmulti-tenantopen-sourceorganizational-contextpgvectorrbacscoped-accesstenant-isolation
View on GitHub ↗Homepage ↗

About halofy

The open access and governance layer for AI agents across your organization. Give every agent the right organizational context through one identity and policy model, with provenance, audit, and signed erasure.

As AI spreads across an organization, every agent needs access to shared context without becoming its own identity system, policy engine, or audit silo. Halofy sits between organizational knowledge and the agents that use it. It resolves identity, enforces access, governs change, records every outcome, and makes erasure independently verifiable.

Underneath that governance boundary, Halofy maintains durable context and keeps retrieval replaceable. The result is infrastructure you can inspect, self-host, run offline, and connect to any agent over MCP or HTTP.

Organization-wide access Governed context Open infrastructure --------- Agents, applications, and operators use the same server-resolved identity, namespace ACL, roles, and policy boundary over MCP or HTTP. Every change follows one auditable path with provenance, supersedence, append-only history, and signed erasure. Postgres remains the authority while retrieval engines plug in through an ACL-scoped, read-only driver interface.

- One governed access surface over MCP and HTTP: memwrite, memread, memsearch, memassemble, memfault, memstats, memforget, policy, sharing, pinning, export, and manifest operations. - Organization-wide identity and access control: credentials resolve actor, role, namespace, and source scope server-side before any read or write. - A governed context lifecycle: provenance, entity resoluti

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/halofyai--halofy.html)

Related MCP servers

herry2059/project-os-for-codex

Open-source control plane for Codex projects: Git-backed context, visible agent progress, scoped MCP access, resumable work, and safe handoffs.

⭐ 104TypeScript
nisargpatel1906/Aethos_Memory

Universal, cross-tool persistent memory bank for AI assistants (Claude Code, Cursor, Windsurf, OpenCode, Codex) powered by FastMCP, Gemini embeddings & Supabase pgvector.

⭐ 5TypeScript
docouno/notarium

File-first knowledge base for humans and AI agents — self-hosted Markdown notes with a web editor and a built-in MCP server.

⭐ 3TypeScript
risa-labs-inc/BossConsole

Open-source, multi-platform harness for AI agents — a native, multi-threaded operator's console (JVM, not Electron) to run Claude Code, Codex, Gemini or OpenCode with a real browser, terminal, editor,

⭐ 199Kotlin
ozankasikci/global-agent-memory

Local-first, project-aware memory MCP server for Claude Code, Codex, and other AI agents, with Obsidian and an owner dashboard.

⭐ 11Python
Haroon-jay/wctx

Cross-repository context for coding agents. A local-first MCP server that turns finished sessions into findings with commit provenance and staleness checks.

⭐ 7TypeScript

📬 Get the weekly radar in your inbox

The top new MCP servers of the week, every Monday. No spam, unsubscribe anytime.