What it does
Broker for Unreal Engine's built-in MCP server: token auth, execute default-deny, op log. Lab-only.
- Connects Runs on your computer
- Account or key No key needed
- Category Developer tools
Use together with
Skills that teach the AI this kind of work; they work alongside this one
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Why it ranks here
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Install
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Claude cannot connect Seahawk yet
The maker has not listed install details in the MCP Registry yet
ChatGPT cannot connect Seahawk yet
The maker has not listed install details in the MCP Registry yet
What you can do instead
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Claude Code cannot connect Seahawk yet
The maker has not listed install details in the MCP Registry yet
Cursor cannot connect Seahawk yet
The maker has not listed install details in the MCP Registry yet
VS Code cannot connect Seahawk yet
The maker has not listed install details in the MCP Registry yet
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
At a glance
- Downloads per weeki
- Not on npm/PyPI
- Verified domain
- ✓ qompass.ai
- Connection
- Runs on your computer
- Latest versioni
- 1.0.3
- Categoryi
- Developer tools
- Published to registryi
- Nov 19, 2026
- Code last changedi
- Nov 17, 2026
- Maker
- qompassai
- Packages
cargo: seahawk- Website
- qompass.ai
- Registry status
- Active
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain qompass.ai (the registry checks domain ownership)
- ✓ Pass
Still maintained
Code last changed 3 days ago
- ✓ Pass
Has a licence
Uses Apache-2.0
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Published vulnerabilities (OSV.dev)
Not checked: only npm and PyPI packages with a version can be checked
Makers: ask for a re-check or report wrong info
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/qompass-seahawk)Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 0% of the other 6202 servers in this category
- Published to the registry more recently than 96% of the other 6202 servers in this category
- Basic checks equal to or better than 99% of the other 6202 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Seahawk safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed 3 days ago, and the latest version (1.0.3) reached the registry yesterday.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Rust on your computer.
What can I use instead?
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP
Cloudflare MCP servers
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one Seahawk | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | Apache-2.0 | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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
initializeis refused with the typed-32022; forwarded requests apply one settle at a time, in order, against the stateful editor session. - Agent authentication: every
tools/callmust 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 fromtools/listand 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 inseahawk.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) andgui. .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. .actuatewith 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_idand 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
changedcheck 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 pinwindow_idagainst 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.