原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

Seahawk

✓ qompass.ai

作者:qompassai版本 1.0.3i★ 0i在你的电脑上运行官方网站 ↗
注册名称ai.qompass/seahawk

安装方法

能做什么

Broker for Unreal Engine's built-in MCP server: token auth, execute default-deny, op log. Lab-only.

作者提供的原文

  • 连接方式 在你的电脑上运行
  • 账号或密钥 无需密钥
  • 分类 开发者工具

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

rea

Reverse engineer anything with agents, from app behavior down to native binaries.

作者:morluto★ 468,7331 个 skill

Skill · 操作手册

andrej-karpathy-skills

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

作者:multica-ai★ 234,3321 个 skill

Skill · 操作手册未注明许可证

graphify

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

作者:Graphify-Labs★ 150,2871 个 skill

Skill · 操作手册

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分12/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

Claude 暂时无法连接 Seahawk

开发者尚未在 MCP 注册表中填写安装方式

ChatGPT 暂时无法连接 Seahawk

开发者尚未在 MCP 注册表中填写安装方式

你可以改用这些方式

B · 开发者工具 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 Seahawk

开发者尚未在 MCP 注册表中填写安装方式

Cursor 暂时无法连接 Seahawk

开发者尚未在 MCP 注册表中填写安装方式

VS Code 暂时无法连接 Seahawk

开发者尚未在 MCP 注册表中填写安装方式

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Seahawk 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
已验证域名
✓ qompass.ai
许可证i
Apache-2.0
连接方式
在你的电脑上运行
最新版本i
1.0.3
发布到注册中心i
2026年11月19日
代码最后更新i
2026年11月17日
作者
qompassai
软件包
cargo: seahawk
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

在你的电脑上运行,适用于

GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过域名 qompass.ai 验证(注册中心会核实域名所有权)

  • ✓ 通过

    仍在维护

    代码最后更新于3天前

  • ✓ 通过

    有许可证

    使用 Apache-2.0

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

已公开的漏洞(OSV.dev)

未检查:只能检查标明版本的 npm 和 PyPI 包

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/qompass-seahawk.svg)](https://mcp.popnx.com/en/servers/qompass-seahawk)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“开发者工具”中的其他服务器比较i

  • 星标数多于此分类中其他 6202 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 6202 个服务器的 96% 更新
  • 基础检查结果等于或优于此分类中其他 6202 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Seahawk 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于3天前,最新版本(1.0.3)于昨天进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Rust。

有什么可以替代它?

同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

作者:ahmedkhaleel2004广泛使用★ 1.9万2个月前更新

在云端运行✓ 服务方 · gitdiagram.comPopNx 团队已实际试用

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

作者:Appllama广泛使用★ 52333个月前更新

在云端运行✓ 服务方 · appllama.io

Omnara

Deploy durable AI agents with Omnara, an open-source managed-agent platform.

作者:omnara-ai广泛使用★ 34232个月前更新

在云端运行✓ 服务方 · omnara.com

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

作者:repowise-dev广泛使用↓ 6506/周★ 8177 整个仓库的星标7天前更新

电脑或云端✓ 服务方 · repowise.dev
与相似项目对比
本项
Seahawk
GitDiagramAppllamaCloudflare MCPOmnaraRepowise
运行位置需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装云端或安装在电脑上都可以
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否是否否
基础检查3/34/44/44/44/45/5
许可证Apache-2.0MITMITApache-2.0Apache-2.0AGPL-3.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Seahawk

The estate's authenticated broker for Unreal Engine's built-in MCP server (Epic's ModelContextProtocol plugin in UE 5.8). Named for Rafael Sabatini's *The Sea Hawk* (Owner, D-171; renamed from conn).

Epic's editor MCP server is powerful and completely unauthenticated: any local process that can reach its loopback port gets the editor's full tool surface, including in-editor Python execution. Seahawk exists so agents never touch that raw server. It serves modern-era MCP (2026-07-28) over stdio to agents, and downstream it speaks to Epic's legacy-era server as a client, localhost only.

Controls

  • Era guard + sequencer (fleet template): legacy initialize is refused with the typed -32022; forwarded requests apply one settle at a time, in order, against the stateful editor session.
  • Agent authentication: every tools/call must carry the agent token in _meta["seahawk/agent_token"]. The guard verifies it (SHA-256 digests, constant-time compare), strips it from the frame, and logs refusals. Missing/wrong token: typed -32001.
  • Class curation: every downstream tool is classified read / write / execute from the verified S0 census of UE 5.8's surface (830 tools; see the build workspace's SURFACE.md). Unclassified tools are withheld from tools/list and refused on call.
  • Execute default-deny: execute-class tools (in-editor Python, arbitrary file write, Blueprint compilation, plugin loading, PIE, UI input injection, settings persistence, skill authoring, …) are listed with destructive annotations but refused unless the operator enables the specific tool in policy and the call carries a distinct operator token in _meta["seahawk/operator_token"].
  • Op log: every brokered call and guard refusal appends one JSON line — tool, class, SHA-256 of the canonical arguments, outcome, downstream latency. Raw argument values are never logged. This is the non-idempotency record: exactly what was applied, in order.
  • Policy as data: tokens, downstream URL (loopback enforced), execute enablements, and per-tool class overrides live in a TOML config — see seahawk.example.toml.

Computer use (S4)

Beyond the Unreal broker, Seahawk drives GUI applications on its own X11 display through a built-in provider. The class lattice is read < write < actuate < execute; classification follows reach, not mechanism (Epic's Slate UI-injection tools stay execute for exactly that reason).

  • Registration is policy data only: [[gui.apps]] entries in the config name an application and the window-match strings (WM_CLASS / instance equality, or title substring) that identify its windows. There is no agent-callable registration and no runtime re-registration; the config is read once at startup. The estate's media-GUI registrations ship in seahawk.example.toml: Blender, Unity (Editor + Hub), ComfyUI (browser-hosted; matched by window title), Aseprite.
  • Per app, two tools: gui. .observe (read class — screenshot, window list, focus state; screenshots return a PNG and are op-logged by digest + dimensions, never by content) and gui. .actuate (actuate class — focus, click, double-click, key chords, text entry, scroll, drag).
  • Actuate is default-deny with the execute two-key rule: the tool must be named in policy.actuate_enabled *and* each call must carry the operator token. Actuation is confined to the registered window's rectangle (coordinates are validated against it before anything is injected), and every actuation is bracketed by screenshots whose digests land in the op log alongside the target description — a click cannot be undone, so the record shows what the screen held on both sides of it.
  • Honest caution: input into an application that hosts scripting (Blender's Python console, Unity's editor, Aseprite scripts, ComfyUI custom nodes) can compose into code execution through the UI. The actuate class records the mechanism; the two-key gate prices the risk. Treat enabling gui. .actuate with the same gravity as enabling an execute-class tool for that application.

Vision grounding (S5, hardened by the 1.0 curative round)

Three broker-level tools give the broker eyes, gated by the same decide() lattice as everything else (grounding is perception only — it grants no permission):

  • `gui.observe` (read): a registered app's frame *with* display geometry, stored under its SHA-256; results carry the resolved window_id and a blank-frame content verdict (content | suspect_blank).
  • `gui.ground` (read): a natural-language target → the element's bbox plus the point derived as its centre, via a local Ollama-served vision model or the calling agent answering the broker's ticket. The centre is derived, never estimated — the curative fix for the S5 benchmark's trailing-edge aim bias.
  • `gui.act_verified` (actuate): act and verify against a fresh capture. The changed check can be anchored (changed_around) or full-frame (full_frame); point-less actions diff the full frame by default. Retries *change strategy* (refined description, then route/crop escalation) and stop early on an identical re-ground. Frames that stay suspect-blank through a bounded content poll refuse the act (seahawk_gui_suspect_blank), and a caller may pin window_id against silent retargeting (seahawk_gui_window_mismatch). Visual verdicts follow the frozen Visual Benchmark v1 (BENCH-VISUAL.md).

Code feedback (D-230 wiring)

`code.feedback` (read) closes the loop between brokered GUI work and the estate's language tooling: per file it returns LSP diagnostics (theodolite headless route; GDScript via periscope), lint verdicts and format changed flags (periscope running diver's own pipelines — Seahawk consumes the catalog live through periscope, never a second hardcoded list), file hashes, and the catalog provenance. Calls are bounded episodes (3 per workspace + file set per window; the 4th is refused with the last counts). A route that cannot serve a check answers seahawk_tooling_unavailable — feedback is never assumed clean, and it never writes: the tooling client's dispatch table contains no apply/write call at all. Wiring is opt-in policy data ([[tooling]] + [feedback] in seahawk.example.toml).

Honest limits

Seahawk cannot firewall Epic's port: a local process that bypasses Seahawk and speaks to the editor directly is outside its guarantees. The operating discipline is lab-only use — throwaway projects, editor up only during brokered sessions, nonstandard port. The full threat model is in SURFACE.md.

Status

1.0.0 — lab-only (Owner ruling, D-146/D-169). The safety charter is unchanged and binding: token auth, execute- and actuate-class default-deny via decide(), append-only op log, lab-only. Publication to crates.io / the MCP registry is held for the Owner's word (see CHANGELOG.md and the 1.0 gate report). Repository: https://github.com/qompassai/seahawk.