Hythe

Name: Hythe
Author: hythe-dev

제작자: hythe-dev버전 0.2.0i★ –i내 컴퓨터에서 실행

레지스트리 이름dev.hythe/hythe

설치

개요

제작자가 쓴 설명(영어 원문)

HYTHE — coordination bus + shared truth for AI agent fleets — self-hosted MCP server + stdio bridge.

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

사용자 의견i아직 리뷰가 없어요리뷰는 다음 단계에서 계정 기능과 함께 열려요
우리의 기본 점검i1개 중 1개 통과공개된 정보로 점검했으며, 코드는 아직 스캔하지 않았어요
사용 정도i아직 측정 안 함★ –

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

연결 방식: 내 컴퓨터에서 실행
전송 방식: stdio
카테고리: 기타
입력해야 할 값: HYTHE_AGENT_ID, API_KEY

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

기본 점검: 1개 중 1개 통과
내 컴퓨터에서 내 사용자 계정의 권한(파일, 네트워크, 앱)으로 실행돼요.
직접 입력할 값: HYTHE_AGENT_ID, HYTHE_AGENT_KEY_FILE, HYTHE_AGENT_AUTH_MODE, API_KEY, MCP_HOST, MCP_PORT

비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.

필요한 것

npmNode.js 설치(npx 명령어용)

어떤 앱을 쓰세요?

ClaudeClaude CodeCursorVS CodeChatGPT

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요

{
  "mcpServers": {
    "hythe": {
      "command": "npx",
      "args": [
        "-y",
        "@hythe/mcp"
      ],
      "env": {
        "HYTHE_AGENT_ID": "your-value",
        "HYTHE_AGENT_KEY_FILE": "your-value",
        "HYTHE_AGENT_AUTH_MODE": "your-value",
        "API_KEY": "your-value",
        "MCP_HOST": "your-value",
        "MCP_PORT": "your-value"
      }
    }
  }
}

터미널에서 이 명령어를 실행하세요

claude mcp add hythe --env HYTHE_AGENT_ID=your-value --env HYTHE_AGENT_KEY_FILE=your-value --env HYTHE_AGENT_AUTH_MODE=your-value --env API_KEY=your-value --env MCP_HOST=your-value --env MCP_PORT=your-value -- npx -y @hythe/mcp

실행하기 전에 빈 값을 채워 주세요.

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

{
  "mcpServers": {
    "hythe": {
      "command": "npx",
      "args": [
        "-y",
        "@hythe/mcp"
      ],
      "env": {
        "HYTHE_AGENT_ID": "your-value",
        "HYTHE_AGENT_KEY_FILE": "your-value",
        "HYTHE_AGENT_AUTH_MODE": "your-value",
        "API_KEY": "your-value",
        "MCP_HOST": "your-value",
        "MCP_PORT": "your-value"
      }
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

{
  "servers": {
    "hythe": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@hythe/mcp"
      ],
      "env": {
        "HYTHE_AGENT_ID": "your-value",
        "HYTHE_AGENT_KEY_FILE": "your-value",
        "HYTHE_AGENT_AUTH_MODE": "your-value",
        "API_KEY": "your-value",
        "MCP_HOST": "your-value",
        "MCP_PORT": "your-value"
      }
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

HYTHE_AGENT_ID 필수 env
Stable exact agent identity for this client lane; required so restarts and compaction cannot adopt another principal
HYTHE_AGENT_KEY_FILE env
Optional path to one protected per-agent credential file: regular, non-symlink, owned by the client user, mode 0400 or 0600, containing one hya1 token. Never place the token itself in an environment…
HYTHE_AGENT_AUTH_MODE env
Client authorization expectation: observe, mixed, or required (default observe). Move to mixed and then required only after this exact lane has a credential and passes /agent/whoami.
API_KEY 비밀 필수 env
Shared API key authenticating the bridge to your self-hosted HYTHE server (create a protected .env with: npx -y @hythe/mcp@0.2.0 init --write-env --agent-id )
MCP_HOST env
HYTHE server host (default 127.0.0.1)
MCP_PORT env
HYTHE server port (default 6174)

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검

✓ 통과
제작자와 저장소 일치
레지스트리 이름이 도메인 hythe.dev 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
… 아직 점검 안 함
계속 관리되고 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
… 아직 점검 안 함
라이선스 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
– 해당 없음
엔드포인트 응답
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
– 해당 없음
OAuth로 로그인
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
… 아직 점검 안 함
도구 설명에 숨겨진 지시 없음
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요

기타 카테고리의 다른 서버와 비교i

이 카테고리의 다른 서버 32398개 중 0%보다 스타가 많아요
이 카테고리의 다른 서버 32398개 중 33%보다 최근에 레지스트리에 공개됐어요
기본 점검 결과가 이 카테고리의 다른 서버 32398개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

Hythe, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

입력해야 할 값: HYTHE_AGENT_ID, API_KEY

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.2.0)은 2개월 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, AI Deprecations

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Spec Driven Development

제작자: formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

내 컴퓨터에서 실행★ 440MIT14개월 전 업데이트

설치

Remote Desktop Commander

제작자: desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

클라우드에서 실행★ 211어제 업데이트

설치

AI Deprecations

제작자: aideprecations.com

AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.

클라우드에서 실행오늘 업데이트

설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

HYTHE

A coordination bus + shared truth for your agent fleet. Self-hosted, two-component setup: a dockerized server plus a thin stdio bridge for your MCP clients.

HYTHE is an MCP server that lets multiple AI coding agents — Claude Code, Codex, Cursor, custom harnesses — share state, preserve context across sessions, and coordinate with each other. It is not another memory store. Its differentiators:

Supersession + current-state resolution: observations supersede each other (replace-current), and get_current_observation resolves the chain server-side — so readers get the newest non-superseded state. Conflict handling is implemented: checkpoint is branch-preserving CAS — concurrent writers branch rather than overwrite, and conflicts surface as heads, never silently resolved (contract-tested; see the evidence ledger).
Agent messaging with a tracked delivery lifecycle: direct and capability-based sends, message supersession, read-state as a shared signal, atomic ack+archive. (Described as *tracked lifecycle*, not guaranteed delivery — the states are honest about what the server knows.)
The Adaptive Coordination Protocol (ACP): the ETA-driven coordination discipline that co-evolved with the server — published as docs/SPEC.md with a real two-harness worked tutorial.

Documentation

Doc	What it covers
Quickstart	Clean machine → two coordinating agents in ~15 minutes
Concepts	One current truth, messaging lifecycle, resume/checkpoint, honest security model
Checkpoint / resume v3	Current-head pointer, reconciliation, record / patch, the v3 read model, and the one-time adoption step for scopes written before v3
ACP SPEC	The coordination protocol, versioned (1.0.0)
Tutorial	Annotated transcript of a real Claude Code ↔ Codex review loop from the original Engram deployment
Tool compatibility map	The 20-tool v1 surface; every retired tool and its exact replacement
Backup & restore	Tested SQLite backup/restore/compaction runbook
Agent credential operator	Offline issuance, attestation, promotion, rotation, and revocation
Private-residue adjudication	Hash-bound, owner-approved disposition of ambiguous historical rows
SQLite physical sanitation	Verified offline VACUUM and no-clobber promotion after logical cleanup
Pavilion production	Pinned deployment, readiness, shutdown, canary, and rollback contract

Status

Version 0.2.0. This source tree and package define the reviewed 0.2.0 release. Version 0.2.0 preserves 0.1.7's dual-proof agent authorization, exact-mailbox/private-payload containment, bounded related-context discovery, latency-SLO recovery and the offline adjudicator, and adds checkpoint / resume resultVersion: 3: an explicit current-head pointer per scope, a reconcile operation that folds live heads into one survivor and resolves divergent values causally, append-only verified fact/loop versions, a read model that only promotes values proven on the accepted lineage, and record / patch operations on the pointed head. Every v1 / v2 request and result shape is frozen; v3 is opt-in per call, so a 0.1.7 client keeps working against a 0.2.0 server. The dependency tree moved to Express 5, clearing two moderate qs advisories. This release runs on the reference production host since 2026-09-05. All 0.2.0 rollout configurations pin @hythe/mcp@0.2.0; verify that the registry returns that exact version before production use. The predecessor @tomcat65/engram-mcp and io.github.tomcat65/engram remain available as compatibility history and are never unpublished. See CHANGELOG.md and the v3 guide.

House rule: every claim in these docs must trace to a test or a measurement (see the evidence ledger below). Claims that don't are bugs.

Evidence ledger

Claim	Evidence	Source	Date
Tree green, full gates	Source and clean installed-package gates cover 49 Vitest files (530 passed, 2 skipped, 6 explicit todos), 107 migration checks, 43 release-tree checks, 31 agent-kit checks, zero production npm audit findings, registry validation, and an isolated Docker start/readiness/MCP/WebSocket/graceful-shutdown canary.	`.github/workflows/ci.yml`, `tests/`, `src/migrations/`, `clients/agent-kit/tests/test-setup.sh`, `scripts/verify-hythe-release-tree.test.mjs`, `scripts/verify-packed-consumer.mjs`	2026-08-14
Compaction identity fails closed	Startup and post-compaction hooks reject missing, conflicting, or invalid identity; the bridge binds acting tools and message-resource recipients to the configured exact lane before any HTTP request.	`clients/agent-kit/tests/test-setup.sh`, `tests/contract-bridge-identity.test.ts`	2026-08-13
Exact mailboxes stay isolated	Houston/Hythe, case variants, display metadata, legacy identity history, cross-tenant poisoning, suffix handles, lifecycle changes, supersession, HTTP, and ENG-4 authorship have negative isolation coverage.	`tests/contract-message-identity-isolation.test.ts`, `tests/contract-eng4-p0.test.ts`	2026-08-13
Private message bodies stay out of shared graph surfaces	Historical, oversized, malformed, alias-linked, relation-linked, imported, exported, searched, graphed, logged, and restored payload paths are covered; hidden children do not leak through counts.	`tests/contract-message-payload-isolation.test.ts`, `tests/contract-data-payload-isolation.test.ts`, `tests/contract-log-confidentiality.test.ts`	2026-08-13
Cleanup is offline and fail-closed	Migration 007, owner-approved adjudication, and physical sanitation are dry-run/plan-first, bind execution to reviewed database and decision evidence, require verified no-clobber artifacts, refuse unresolved custody, and preserve rollback state.	`src/migrations/007-private-message-residue.mjs`, `src/migrations/private-message-residue-adjudication.mjs`, `src/migrations/vacuum-sanitized-database.mjs`, `docs/`	2026-08-14
Per-agent authority is server-derived	The base key proves deployment/tenant access; a separate protected-file `hya1` credential proves the exact agent. Required mode rejects stripped proof, mismatched identity, insufficient scope, revoked credentials, and stale WebSocket sessions.	`src/agent-auth/`, `tests/contract-agent-auth-foundation.test.ts`, `tests/contract-agent-auth-server.test.ts`, `tests/contract-agent-key-client.test.ts`	2026-08-14
Install and discovery surfaces agree	CLI and registry surfaces require an exact lane identity and expose only a protected per-agent key-file path plus an explicit authorization mode; tools and resource templates served through HTTP match the stdio bridge path.	`tests/contract-cli.test.ts`, `tests/contract-agent-key-client.test.ts`, `tests/contract-mcp-resources-http.test.ts`, `scripts/verify-hythe-release-tree.test.mjs`	2026-08-14
Current head is explicit, never guessed	The pointer advances only from the pointed head; stale parents branch without becoming current; a pointer at a non-live snapshot fails closed; snapshot rows are immutable by trigger. 33 contract tests.	`tests/contract-eng4-h1-head-pointer.test.ts`	2026-09-03
Versions and coverage are exact and verified	Every ledger tuple gets exactly one disposition; the startup backfill is all-or-nothing and idempotent; a bidirectional parity verifier fails closed on any missing, extra or mismatched row. 32 contract tests.	`tests/contract-eng4-h2-version-foundation.test.ts`	2026-09-03
Reconciliation is CAS-bound and causal	Exact live-head set and pointer are compare-and-set; every non-survivor head is retired (never deleted); divergent values resolve only by bound accept, reject or lineage reject; the record is payload-bound and re-verified on replay and read. 34 contract tests.	`tests/contract-eng4-h3-reconcile.test.ts`	2026-09-04
The v3 read model promotes only proven values	`currentFacts` / `openLoops` come only from verified versions on the accepted lineage with provenance; everything else is accounted as divergent or legacy with closed coverage. 29 contract tests.	`tests/contract-eng4-h4-read-model.test.ts`	2026-09-04
record / patch cannot promote stale state	Only the pointed head is admitted (conflict otherwise); state is materialized from the hash-verified payload; each payload is read once per call; snapshot resources serve exactly the verified bytes. 21 contract tests, four review rounds.	`tests/contract-eng4-h5-record-patch.test.ts`	2026-09-04
Express 5 keeps the HTTP contract	A bodiless or wrong-content-type request is handled like an empty JSON body on every parsed route, never a framework 500; production audit reports zero findings.	`tests/contract-express5-body-contract.test.ts`, `.github/workflows/ci.yml` run 33878587010	2026-09-04
Production migration verified on a copy first	The v3 schema and backfill were exercised against a copy of the production database on the production host before cutover; the live cutover took 17 s with row counts identical to the verified cold backup.	`docs/PAVILION-PRODUCTION.md`; operator log `engram-prod/releases/hythe-74a324c-cutover-20260905T005551Z.log` on the host	2026-09-05

v1 surface (short)

Install (two-component setup): server via docker compose up, then the @hythe/mcp stdio bridge per MCP client; first-run wizard stores the API key in a protected .env and prints secret-free file-referencing config for Claude Code / Codex / Cursor / Claude Desktop; optional namespaced (demo-*) demo seed on an otherwise empty DB.
Knowledge graph: entities, observations, relations, supersession, current-state resolution, conflict surfacing.
Related-context discovery: exact scope anchoring plus automatic bounded vector retrieval and graph-path reranking, with currentness/evidence/provenance explanations and no implicit writes.
Agent messaging: direct, capability-based, superseding; tracked delivery lifecycle.
`resume` / `checkpoint`: budgeted one-call session rehydration with closed coverage accounting, and CAS-protected, branch-preserving structured state capture. With resultVersion: 3: an explicit current-head pointer, reconcile to fold heads and resolve divergent values, verified fact/loop versions with provenance, and record / patch on the pointed head — see the v3 guide.
ACP: the coordination protocol as a versioned spec + real worked example.

Embedding runtime contract

The published npm package does not install a transformer engine by default. Without one, HYTHE still provides deterministic 384-dimension token-hash vectors plus lexical ranking; it does not download a model or create a model cache. @xenova/transformers@2.17.2 is an optional peer for operators who deliberately provide it from their own audited dependency root.

The Docker image keeps semantic behavior stable through a separate, locked /opt/hythe-transformers runtime. Its startup preflight loads the configured Xenova/all-MiniLM-L6-v2 q8 model and requires one finite 384-dimension embedding before the server starts. When SQLITE_VEC_ALLOW_REMOTE_MODELS=false, the configured SQLITE_VEC_CACHE_DIR must already contain that model. Do not switch between transformer and hash embeddings on a populated vector index: retain the same provider/model/dimensions or rebuild the vector index first.

License

Apache-2.0

Hythe

개요

PopNx MCP의 세 기둥

할 수 있는 일

설치

설치하기 전에

직접 입력할 값

할 수 있는 일

기본 점검i

제작자와 저장소 일치

계속 관리되고 있음

라이선스 있음

엔드포인트 응답

OAuth로 로그인

도구 설명에 숨겨진 지시 없음

기타 카테고리의 다른 서버와 비교i

자주 묻는 질문

대안

Spec Driven Development

Remote Desktop Commander

AI Deprecations

제작자의 README

HYTHE

Documentation

Status

Evidence ledger

v1 surface (short)

Embedding runtime contract

License