Does SEAL (sealnet-mcp) work with ChatGPT (Codex)?

Yes. SEAL (sealnet-mcp) passed every step of our test in ChatGPT (Codex) on Oct 22, 2026: it installed, connected, its tools were visible, and an agent used it to finish a real task.

Result

ResultPassed
Date testedOct 22, 2026
Plan tested onChatGPT Plus
App versionCodex CLI 0.162.0-alpha.17.2
Server packagesealnet-mcp 0.10.0
Connect timeconnect time not recorded
Modelgpt-6-luna (reasoning low)

Steps

  1. install OK
  2. connect OK
  3. tools visible OK
  4. agent task: share manage OKfile sharing server that by design never shows the link to the agent (it goes to the user's clipboard or inbox): share a local file, see it in the server's own list, then revoke it. Opening the link needs a person's paired SEAL inbox, which this test can't do.

From our own harness run, not the maker’s claims. How we test.

Versions tested

Codex CLI 0.162.0-alpha.17.2 · sealnet-mcp 0.10.0 · connect time not recorded · tested Oct 22, 2026

Server package tested: sealnet-mcp 0.10.0 (npm, Node v20.19.2; resolved 2026-10-22)

Direct and key dependencies as resolved: @modelcontextprotocol/sdk 1.32.1 · argon2 0.44.0 · clipboardy 5.3.2 · commander 14.0.3 · express 5.3.0 · zod 4.6.7 · zod-to-json-schema 3.25.2

All 136 resolved dependencies
@epic-web/invariant==1.0.0
@hono/node-server==2.1.5
@modelcontextprotocol/sdk==1.32.1
@napi-rs/keyring==2.1.2
@napi-rs/keyring-linux-x64-gnu==2.1.2
@phc/format==1.0.0
@sec-ant/readable-stream==0.4.1
@sindresorhus/merge-streams==4.0.0
accepts==2.0.0
ajv==8.20.0
ajv-formats==3.0.1
argon2==0.44.0
body-parser==2.4.0
bytes==3.1.2
call-bind-apply-helpers==1.0.2
call-bound==1.0.4
clipboard-image==0.1.0
clipboardy==5.3.2
commander==14.0.3
content-disposition==2.0.1
content-type==1.0.5, 2.1.0
cookie==0.7.2
cookie-signature==1.2.2
cors==2.8.6
cross-env==10.1.0
cross-spawn==7.0.6
crypto-random-string==4.0.0
debug==4.4.3
depd==2.0.0
dunder-proto==1.0.1
ee-first==1.1.1
encodeurl==2.0.0
es-define-property==1.0.1
es-errors==1.3.0
es-object-atoms==1.1.2
escape-html==1.0.3
escape-string-regexp==5.0.0
etag==1.8.1
eventsource==3.0.7
eventsource-parser==3.1.1
execa==5.1.1, 9.6.1
express==5.3.0
express-rate-limit==8.7.1
fast-deep-equal==3.1.3
fast-uri==3.1.9
figures==6.1.0
finalhandler==2.1.1
forwarded==0.2.0
fresh==2.0.0
function-bind==1.1.2
get-intrinsic==1.3.0
get-proto==1.0.1
get-stream==6.0.1, 9.0.1
gopd==1.2.0
has-symbols==1.1.0
hasown==2.0.4
hono==4.13.13
http-errors==2.0.1
human-signals==2.1.0, 8.0.1
iconv-lite==0.7.3
inherits==2.0.4
ip-address==10.7.4
ipaddr.js==1.9.1
is-docker==3.0.0
is-inside-container==1.0.0
is-plain-obj==4.1.0
is-promise==4.0.0
is-stream==2.0.1, 4.0.1
is-unicode-supported==2.1.0
is-wayland==0.1.0
is-wsl==3.1.1
is64bit==2.0.0
isexe==2.0.0
jose==6.2.13
json-schema-traverse==1.0.0
json-schema-typed==8.0.2
macos-version==6.0.0
math-intrinsics==1.1.0
media-typer==1.1.1
merge-descriptors==2.0.0
merge-stream==2.0.0
mime-db==1.54.0
mime-types==3.0.2
mimic-fn==2.1.0
ms==2.1.3
negotiator==1.1.0
node-addon-api==8.9.2
node-gyp-build==4.8.4
npm-run-path==4.0.1, 6.0.0
object-assign==4.1.1
object-inspect==1.13.4
on-finished==2.4.2
once==1.4.0
onetime==5.1.2
parse-ms==4.0.0
parseurl==1.3.3
path-key==3.1.1, 4.0.0
path-to-regexp==8.4.2
pkce-challenge==5.0.1
powershell-utils==0.2.1
pretty-ms==9.3.1
proxy-addr==2.0.8
qs==6.16.1
range-parser==1.3.0
raw-body==3.0.2
require-from-string==2.0.2
router==2.2.0
run-jxa==3.0.0
safer-buffer==2.1.2
semver==7.8.5
send==1.2.1
serve-static==2.2.1
setprototypeof==1.2.0
shebang-command==2.0.0
shebang-regex==3.0.0
side-channel==1.1.1
side-channel-list==1.0.1
side-channel-map==1.0.1
side-channel-weakmap==1.0.2
signal-exit==3.0.7, 4.1.0
statuses==2.0.2
strip-final-newline==2.0.0, 4.0.0
subsume==4.0.0
system-architecture==0.1.0
toidentifier==1.0.1
type-fest==1.4.0, 2.19.0
type-is==2.1.0
unicorn-magic==0.3.0
unique-string==3.0.0
unpipe==1.0.0
vary==1.1.2
which==2.0.2
wrappy==1.0.2
yoctocolors==2.2.0
zod==4.6.7
zod-to-json-schema==3.25.2

Captured with: npm ls --all --json in the npx env.

What happened in this run

Install config we used

[mcp_servers.sealnet-mcp]
command = "npx"
args = ["-y", "sealnet-mcp@latest"]

Connection check

server answered tool calls during the task

Tools check

verified via task step: agent saw and called the server's tools

Agent task: share manage

  • Tool calls, in order: sealnet-mcp:seal_share, sealnet-mcp:seal_list, sealnet-mcp:seal_revoke

Raw details from our harness log for this run. Secrets redacted.

Set it up in ChatGPT (Codex)

Copy-paste config for every app is on the SEAL (sealnet-mcp) page. Not connecting? ChatGPT (Codex) MCP troubleshooting.

Other apps we tested it in: Claude Code (passed) · Cursor (passed).

All MCP servers tested in ChatGPT (Codex)

Sponsors