World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Hosted NeuroDock — stateless communication and planning tools over OAuth-secured Streamable HTTP.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 7/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 15/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 NeuroDock (hosted)。按照 https://mcp.popnx.com/i/tlennon-ie-neurodock-remote.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.neurodock.org) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
NeuroDock (hosted)https://mcp.neurodock.org/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsNeuroDock (hosted)
用 NeuroDock (hosted) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 NeuroDock (hosted),或回答中出现 NeuroDock (hosted) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
NeuroDock (hosted)https://mcp.neurodock.org/mcp开启新聊天,输入前先从插件列表中选择 NeuroDock (hosted)
用 NeuroDock (hosted) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 NeuroDock (hosted),或回答中出现 NeuroDock (hosted) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user neurodock-remote https://mcp.neurodock.org/mcp应能看到 NeuroDock (hosted) 在列表中并显示已连接
用 NeuroDock (hosted) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 NeuroDock (hosted),或回答中出现 NeuroDock (hosted) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 NeuroDock (hosted) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 NeuroDock (hosted),或回答中出现 NeuroDock (hosted) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 NeuroDock (hosted) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 NeuroDock (hosted),或回答中出现 NeuroDock (hosted) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.neurodock.org/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user neurodock-remote https://mcp.neurodock.org/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"neurodock-remote": {
"url": "https://mcp.neurodock.org/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"neurodock-remote": {
"type": "http",
"url": "https://mcp.neurodock.org/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月18日
注册名称已通过 GitHub 账户 tlennon-ie 验证,该账户拥有此仓库
代码最后更新于2个月前
使用 AGPL-3.0
在 225 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/tlennon-ie-neurodock-remote)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于2个月前,最新版本(0.1.0)于6个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 NeuroDock (hosted) | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | AGPL-3.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The combined remote MCP server for NeuroDock (ADR 0008 / ADR 0009, Phase 2).
It composes the three stateless NeuroDock servers into a single Streamable HTTP endpoint and exposes only the remote-safe tools:
| Source server | Tools exposed remotely |
|---|---|
mcp-translation | translate_incoming, check_tone, rewrite_outgoing, brief_meeting |
mcp-guardrail | check_rumination, check_hyperfocus, check_sycophancy |
mcp-task-fractionator | decompose only |
The four cognitive-graph tools (recall_entity, record_fact, recall_decisions, weekly_rollup) are also exposed, but gated: they require a signed-in account that has explicitly enabled storage. Two modes coexist; a user is in exactly one at a time:
| Tool | Mode | What it does | ||
|---|---|---|---|---|
enable_hosted_storage | hosted | NeuroDock provisions a private per-user Turso database and stores facts there. Returns the consent disclosure. | ||
connect_byos_storage | byos | You point at your own libSQL/Turso database; NeuroDock stores only the connection pointer. | ||
disable_and_erase_storage | → none | Hosted: destroys your Turso database. BYOS: clears the stored connection (your DB untouched). Either way the preference/consent is cleared. | ||
disconnect_storage | → none | BYOS-only alias: clears the connection + preference. (Use disable_and_erase_storage to erase hosted.) | ||
storage_status | — | Reports your mode (hosted \ | byos \ | none). |
The mode is selected per user from their recorded storage preference; a single combined resolver routes each cognitive-graph call to the hosted or BYOS backing. The privacy boundary is unchanged from Phase D: an anonymous / no-token caller gets STORAGE_NOT_AVAILABLE and nothing is stored, read, or provisioned; a signed-in but not-enabled caller gets STORAGE_NOT_CONNECTED.
Hosted requires a provisioned Turso org/group/token. Set
NEURODOCK_TURSO_PLATFORM_TOKEN+NEURODOCK_TURSO_ORG(+ optional
NEURODOCK_TURSO_GROUP, defaultdefault, which must already exist in the
org). Without them
enable_hosted_storageis refused and only BYOS is offered.
Encryption-key custody (honest limitation). Both the BYOS auth token and the
hosted Turso DB token are encrypted at rest with a single operator-wide
NEURODOCK_STATE_MASTER_KEY. That means NeuroDock can _technically_ decrypt a
stored token. This is the documented ADR 0010 open question; per-user / envelope
keys (so the operator cannot unilaterally read a user's DB token) are a tracked
follow-up. The on-disk format is unchanged either way, so a future scheme can
re-wrap without a data migration.
Chronometric session state, the user profile (neurotype data), and task-fractionator's next_one (reads the local graph) are never mounted. They hold local state and stay strictly on the local stdio install. The boundary is enforced in code and pinned by tests against REMOTE_TOOL_NAMES.
This is a deploy artifact, not a published package — it is not uploaded to
PyPI (the local install path via
@neurodock/cliis unchanged). Local-only
tools remain available exactly as before through the stdio servers.
The remote server exposes tools, not skills. Skills are markdown the client reads locally, so the remote endpoint never delivers them. Hosted/remote users get the per-neurotype skills the same way local users do: install the Claude Code marketplace plugin (which bundles them) or run neurodock install-skills from @neurodock/cli, which copies each skill into ~/.claude/skills/neurodock- /SKILL.md for Claude Code / Claude Desktop. See packages/skills/README.md for the delivery paths.
# from the repo root
uv run --package neurodock-remote neurodock-remote
Inspect it with the MCP Inspector pointed at http://127.0.0.1:8000/mcp.
| Env var | Default | Purpose | |||
|---|---|---|---|---|---|
NEURODOCK_HTTP_HOST | 127.0.0.1 | Bind host (0.0.0.0 in the container). | |||
NEURODOCK_HTTP_PORT | 8000 | Bind port. | |||
NEURODOCK_AUTH_PROVIDER | none | none \ | clerk \ | workos \ | jwt. The hosted deploy uses clerk. |
NEURODOCK_PUBLIC_URL | — | Public base URL, e.g. https://mcp.neurodock.org (required by clerk/workos/jwt). | |||
NEURODOCK_OAUTH_REQUIRED_SCOPES | — | Optional, comma-separated. | |||
NEURODOCK_CLERK_DOMAIN | — | clerk: your Clerk instance domain (e.g. your-app.clerk.accounts.dev). | |||
NEURODOCK_CLERK_CLIENT_ID | — | clerk: OAuth application client ID. | |||
NEURODOCK_CLERK_CLIENT_SECRET | — | clerk: OAuth client secret (set as a secret, not plaintext). | |||
NEURODOCK_CLERK_SECRET_KEY | — | Storage (ADR 0010 C/D): Clerk Backend API key; persists the per-user storage pointer. | |||
NEURODOCK_STATE_MASTER_KEY | — | Storage (ADR 0010 C/D): master key that encrypts the BYOS/hosted DB token at rest. | |||
NEURODOCK_TURSO_PLATFORM_TOKEN | — | Hosted (ADR 0010 C): Turso Platform API token; provisions/destroys per-user databases. | |||
NEURODOCK_TURSO_ORG | — | Hosted (ADR 0010 C): Turso organization slug the hosted databases are created in. | |||
NEURODOCK_TURSO_GROUP | default | Hosted (ADR 0010 C): Turso group the hosted databases are created in (must exist). | |||
NEURODOCK_GRAPH_DISABLE_EMBEDDINGS | 1 (image) | Storage: keeps the hosted graph lean (no fastembed). Set in the Dockerfile. | |||
NEURODOCK_AUTHKIT_DOMAIN | — | workos: your AuthKit domain. | |||
NEURODOCK_OAUTH_ISSUER / _JWKS_URI / _AUDIENCE | — | jwt: generic OIDC resource-server config. |
⚠️ Auth is required before public exposure. With
NEURODOCK_AUTH_PROVIDER
unset the server runs unauthenticated and logs a loud warning — that mode is
for localhost/integration testing only (ADR 0009 §3). The identity provider is a
configuration choice, not a code change; FastMCP ships first-class Clerk, WorkOS
AuthKit, and Auth0 providers plus the generic JWT verifier wired here.
# build from the repo root (the Dockerfile uses root-relative COPY paths)
docker build -f packages/remote/Dockerfile -t neurodock-remote . docker run --rm -p 8000:8000 \ -e NEURODOCK_AUTH_PROVIDER=clerk \ -e NEURODOCK_CLERK_DOMAIN=your-app.clerk.accounts.dev \ -e NEURODOCK_CLERK_CLIENT_ID=xxxx \ -e NEURODOCK_CLERK_CLIENT_SECRET=yyyy \ -e NEURODOCK_PUBLIC_URL=https://mcp.neurodock.org \ neurodock-remote
The chosen host (ADR 0009). The Python container runs on Cloudflare Containers, fronted by a thin Worker (worker/index.ts) that owns the mcp.neurodock.org custom domain. Config: wrangler.jsonc.
Requires a Workers _Paid_ plan — Containers are not on the free tier.
The Worker + container are deploy tooling only; this directory is intentionally
not a pnpm-workspace member, so install/deploy happen here directly.
vars in wrangler.jsonc (NEURODOCK_CLERK_DOMAIN, NEURODOCK_CLERK_CLIENT_ID) — these are non-secret.packages/remote/): npm install
npx wrangler secret put NEURODOCK_CLERK_CLIENT_SECRET # paste the secret
npx wrangler secret put NEURODOCK_CLERK_SECRET_KEY # Clerk Backend API key npx wrangler secret put NEURODOCK_STATE_MASTER_KEY # token-encryption master key
vars.npx wrangler secret put NEURODOCK_TURSO_PLATFORM_TOKEN # Turso Platform API token npx wrangler deploy # builds ../Dockerfile, pushes, deploys
wrangler deploy builds the image (context ../../ = repo root), provisions the mcp.neurodock.org DNS + TLS automatically (the custom_domain route), and starts the container behind the Worker.
https://mcp.neurodock.org/health → 200, then add https://mcp.neurodock.org/mcp as a custom connector in Claude and complete the Clerk OAuth round-trip.See ADR 0009 for the transport, scope, auth, and hosting decisions.
Status: this Cloudflare deploy config is a verified-by-docs scaffold; it has
not yet been run through
wrangler deploy. Treat the first deploy as the
validation step.