官方说明7 个来源MCP 服务8 天前

boy-offi9-inc/hexforge-gateway

Self-hosted reverse-engineering workspace API — orchestrates jadx/apktool/adb/frida/APKiD via a job & workflow engine, exposed as native MCP tools for Claude. No cloud required.

在 GitHub 查看 ↗直链 · 无中转页

配置模板（请按你的客户端调整）

claude mcp add hexforge-gateway -- npx -y hexforge-gateway

这是根据仓库名生成的可粘贴骨架，命令行参数与包名请以该项目 README 为准。

★ 数取值: 8 ★ · boy-offi9-inc/hexforge-gateway · 取自 GitHub 搜索 API · （2026-10-16 20:00:20 核对）
来源明细: 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
收录与活跃: 收录于 2026-10-09 · 最近见到 2026-10-16 · 共见到 32 次 · 被 7 个来源列出
评分构成: 综合分 703 · 8 ★ · 7 个来源 · mcp

常见问题（答案都来自我们的记录）

怎么安装？

我们【没有】从该仓库取到安装命令（我们的 install 覆盖率只有约 4%）。请看它的 README 或 releases 页。

它适合谁 / 用来做什么？

我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。

谁维护它、还在更新吗？

仓库 boy-offi9-inc/hexforge-gateway；我们收录于 2026-10-09；最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。

第三方质量标记

HexForge Gateway

以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →

= 20">
AI-assisted APK reverse-engineering workspace API. Dispatches tasks to
MCP agents (jadx, apktool, adb, frida, filesystem, MT Manager's APK MCP,
AI providers) and streams updates over WebSocket. Runs entirely on-device
(Termux + MT Manager on Android) or on a normal PC - no cloud required.
Flow: Workspace -> Workflow -> Jobs -> Tasks -> MCP Agents, with modules
talking through an Event Bus. MIT licensed. Contributing: run
npm run typecheck && npm run build && ./scripts/smoke-test.sh before a
PR - see CONTRIBUTING.md.
Getting started
The Gateway starts on http://localhost:8080 and prints a banner with your
workspaces and copy-pasteable commands. GET / returns the same as JSON -
the quickest way to see what's here.
Core endpoints (request/response shapes are in the linked docs):
- GET / - live cheat sheet - GET /health - service + config status
- POST /workspaces / GET /workspaces[/:id] / PUT /workspaces/by-name/:name (idempotent get-or-create)
- POST /workspaces/:id/tasks - dispatch to an MCP agent, fire-and-forget; poll or watch /ws (AGENTS)
- POST /workspaces/:id/jobs / /workflows / /knowledge (ARCHITECTURE)
- GET /workspaces/:id/inbox - APKs dropped into APK_INBOX_DIR, if configured, and auto-claimed into this workspace (INBOX)
- POST|GET /workspaces/:id/chat (AI)
- GET /plugins (PLUGINS)
- GET /capabilities - what the Gateway can do and which agents provide it (AGENTS)
- GET /workspaces/:id/artifacts / GET /artifacts/:id - directories and files finished tasks produced, with the run that made them (ARCHITECTURE)
- POST/GET /workspaces/:id/findings (filter by status or a cited entityId), GET/PATCH /findings/:id, GET /findings/:id/verification - claims with evidence checked against real artifacts and graph entities, and re-checked against the cited files (ARCHITECTURE)
- POST/GET /workspaces/:id/graph/entities, GET /graph/entities/:id, POST/GET /workspaces/:id/graph/edges - typed entities and relationships observed about the target (ARCHITECTURE)
- WS /ws - real-time task:update, job:update, workflow:update, knowledge:entry_created, workspace:status_changed for every workspace
- WS /ws/workspaces/:id - same events, filtered to one workspace
Stack
Node.js 22+ / TypeScript, Fastify (+ @fastify/websocket), Zod. Storage is
local files by default; Supabase is opt-in (STORAGE_BACKEND=supabase). Auth
is an opt-in API key check, off by default (AUTH_ENABLED=false). npm test
runs the Vitest unit suite (retry/failure-path logic, no live instance
needed); scripts/smoke-test.sh covers end-to-end happy paths against a
running Gateway - see tests/README.md for the split.