World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
When will it ship? A live what-if Gantt for small teams: realistic dates and deadline risk.
作者提供的原文
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 11/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 31/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 whenship。按照 https://mcp.popnx.com/i/hamedshams-whenship.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(whenship.app) · ✓ 命令已检查 2026年11月21日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
名称和地址已为你填好,核对后点击 Add · 如果没有登录,Claude 会先让你登录
在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
CustomizeConnectors
点击“Add” → “Custom” → “Web”,填写这 2 项
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
whenshiphttps://whenship.app/mcp+Connectorswhenship
用 whenship 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 whenship,或回答中出现 whenship 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
whenshiphttps://whenship.app/mcp开启新聊天,输入前先从插件列表中选择 whenship
用 whenship 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 whenship,或回答中出现 whenship 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user whenship https://whenship.app/mcp应能看到 whenship 在列表中并显示已连接
用 whenship 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 whenship,或回答中出现 whenship 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 whenship 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 whenship,或回答中出现 whenship 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 whenship 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 whenship,或回答中出现 whenship 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://whenship.app/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user whenship https://whenship.app/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"whenship": {
"url": "https://whenship.app/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"whenship": {
"type": "http",
"url": "https://whenship.app/mcp"
}
}
}Claude Code
claude mcp add --scope user whenship -- npx -y whenshipClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"whenship": {
"command": "npx",
"args": [
"-y",
"whenship"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"whenship": {
"command": "npx",
"args": [
"-y",
"whenship"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"whenship": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"whenship"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
工具名称和描述与服务器在 2026年11月21日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
show_planSchedules work for a small team and shows an interactive Gantt chart: finish dates per item, deadline risk (on time / tight / late, with a rough chance), what sets the end date, and the best options to meet more deadlines. Use for "when will this ship", "can we make these deadlin
what_ifCompares a plan before and after a change and reports which finish dates move and which deadlines are newly met or missed. The change is a list of simple `changes` (move an item to a position, change effort, set or clear a deadline or a can't-start-before date, change a lane's pe
find_optionsSearches realistic changes that would meet more deadlines or make the plan sturdier: reordering, deferring undated work, more availability, one more person, or negotiating a deadline. Every option is re-planned exactly, and returned with its effect and the changes that would appl
export_planReturns the plan as a file: json (the whenship save file, re-openable on the website and in Claude), csv (one row per item with dates), ics (calendar with finish dates and deadlines), markdown (the report), or link (a share link with the whole plan inside it). Spreadsheet (XLSX)
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月21日
注册名称已通过 GitHub 账户 HamedShams 验证,该账户拥有此仓库
代码最后更新于昨天
使用 BSD-3-Clause
在 202 毫秒内响应(HTTP 200)
无需登录
已读取 4 个工具描述,未发现针对 AI 的隐藏指令
OSV.dev 中没有 whenship@1.6.3 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月21日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/hamedshams-whenship)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于昨天,最新版本(1.6.3)于今天进入注册中心。
支持 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.
| 本项 whenship | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | BSD-3-Clause | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
When will it ship, honestly? A tiny planner for small teams. List the work, who does it and roughly how long it takes; whenship draws the timeline, tells you which deadlines will slip and why, and lets you drag things around until the plan works. It runs in the browser, offline, and inside Claude. It's open source: use the hosted copy at whenship.app, or run your own with one command, as an offline file or on your own server. Every copy works the same.
*The plan in the picture is docs/example.whenship.json: four people, eight items, a launch date. One promise is two days late, and the first option under the chart fixes it for free.*
| Where | How |
|---|---|
| Web | Open whenship.app, the hosted copy: pick an example, paste your list, open a file or start from scratch. Your plan stays in your browser, and the next visit opens straight on it (the logo goes back to the home page). |
| Your computer | npx whenship opens it in your browser. Nothing leaves your machine. |
| Offline file | Download whenship.html (from any running whenship, at /whenship.html) and double-click it. |
| Claude | Add the connector or the desktop extension (two ways) and ask: *"Sara has these five client deliverables… will she make the deadlines?"* |
| Your own server | One small Node service, no database, no Docker. See Self-host. |
npx whenship runs the npm package. From a clone it is the same thing: npm ci && npm run build, then node dist/cli.js (add --stdio for the MCP server).
Bring your plan in any shape: paste a list (Grant draft for Acme, 5d, due 7 Oct), spreadsheet rows, CSV, a Markdown table, or open a saved plan file.
Take it out again: a plan file (JSON), Excel with a Gantt sheet, CSV, a PNG of the chart, a Markdown summary, or a link with the whole plan inside it. Links keep the view too (the forecast lens and the zoom), and the website remembers both between visits.
whenship is an MCP App: Claude calls its engine for the dates and shows the interactive chart right in the conversation. Edit the chart and Claude sees your changes automatically, with no "send" button. Then ask something like: *"Sara has these five client deliverables… will she make the deadlines?"*
There are two ways to add it. Both show the same chart.
Works in claude.ai, Claude Desktop and the mobile apps.
whenship and enter the address https://whenship.app/mcp (or your own server's address followed by /mcp, see Self-host).On a Team or Enterprise plan, an owner adds it once for everyone under Organization settings → Connectors.
Nothing leaves your machine: the engine runs locally with Claude Desktop's built-in Node.
whenship.mcpb from the latest release.To update, install the newer file over the old one. To build the file yourself: npm run build && npm run build:mcpb (set WHENSHIP_PUBLIC_URL to choose where "Open in browser" and share links go).
Claude Code
claude mcp add whenship -- npx -y whenship --stdio
Cursor, VS Code and other MCP clients (local)
{ "mcpServers": { "whenship": { "command": "npx", "args": ["-y", "whenship", "--stdio"] } } }
It teaches Claude to always use the engine instead of estimating dates itself, and how to turn the results into advice:
claude plugin marketplace add HamedShams/whenship
claude plugin install whenship@whenship
The skills are plain Markdown: plugin/skills/whenship (workflow and plan format) and plugin/skills/whenship-insights (recommendations, with worked examples for consultancies, product squads, solo founders, agencies, teams with a Sunday–Thursday week, and teams working with AI agents). The plugin holds skills only; the chart comes from the connector or the extension.
Tools: show_plan (schedule and chart), what_if (compare a list of changes, or a whole alternative version of the plan), find_options (changes that meet more deadlines), export_plan (JSON, CSV, iCalendar, Markdown, link). All are read-only.
In the chart, Ask Claude for better options (a button above the options) posts a request to the chat. Claude tries what the built-in suggestions can't (moving work between people, splitting or cutting items, combinations), checks each idea with what_if, and sends its best one or two back through show_plan: they appear in the chart as options with their exact effects, in place of the lowest-ranked built-in ones, so the chart never shows more than three. An option of Claude's that you apply leaves the list (undo brings it back), and one that brings in someone who is already in the plan uses that person instead of adding a second one. Claude's reply stays short, and nothing leaves the chart: it exports itself.
By default you see your own estimates (*As planned*). whenship never stretches them. The lens switch shows the same plan if work runs long the way it usually does:
| Lens | Multiplier | Meaning |
|---|---|---|
| As planned | 1× | Exactly what you entered: if everything goes to plan. |
| Likely | 1.6× | How it usually goes: about half of projects are done by here. |
| Safe bet | 3.1× | A date you can promise: about 9 in 10 projects are done by here. |
The badges use the same scale: *safe* means on time even at 3.1×, *likely* means on time at 1.6×, *tight* means on time only if nothing slips, and *late* means late even as planned. With another lens on, every deadline that lens's dates miss shows as *late*.
Where the numbers come from. People underestimate, so the lenses show the plan when work runs long the way it usually does. The multipliers (P50 1.6×: about half of projects are done by then; P90 3.1×: about 9 in 10) come from a blended outside-view heuristic: Todd Little's 2006 lognormal model of software estimation error, combined with Flyvbjerg et al.'s 2022 power-law findings on IT project overruns, sanity-checked by simple/geometric averaging and a 50/50 Monte Carlo mixture. They are practical, generic rules of thumb, not a formal industry standard. Your own track record beats them.
The "~x% chance" on each deadline reads the same scale: a smooth (lognormal) curve through those two points (P80 ≈ 2.5×, P95 ≈ 3.7×; about 1 plan in 5 finishes as estimated). It assumes the whole plan runs long or short together, so it is a rough guide for one deadline, not a combined probability for several.
The chart's lens guide (the ⓘ next to the lenses) carries a two-sentence version of this; this section is the full one.
The list on the left has one row per item, in priority order: # · Item · Effort · Expected delivery · Deadline. The expected delivery is what whenship works out from the effort, so it sits right beside it; the deadline is what you set, and comes last as the yardstick.
| Mark | Meaning |
|---|---|
| Bar | When someone works on the item, one colour per person or team. An item with several people has one thin bar each. |
| ◆ Diamond | The item's deadline (the usual Gantt milestone mark). Green: on time. Amber: tight. Red: late. |
| Hatched stripes | The part of the work that runs past the deadline. |
| Vertical line | Today. |
| Thin grey line under a bar | Only with *Likely* or *Safe bet* on: your own estimate (the *As planned* dates), while the bar shows the stretched ones. Gantt tools call this the baseline. |
| "ends 9 Dec" beside a bar | The finish date, shown for the row under the pointer, the selected row, and any row whose date is changing. |
A small key under the chart repeats this, and hovering any mark gives its dates. A line under every third row runs across the list and the chart, so a row can be followed to its bar.
| To | Do this |
|---|---|
| Add an item | Type in the empty row at the bottom. Its settings open as you name it; Enter closes them and moves down a row. |
| Reprioritise | Drag a row by its ⠿ handle, or drag its bar up or down. Every date updates before you drop, and the page scrolls with you on a long list. |
| Change the effort | With one person in the plan, type the days into the row. With several people or a team, click the Effort cell: who does how many days, and who starts after whom. Or drag a bar's right edge. |
| Set or move a deadline | Click the Deadline cell: a small calendar opens under the row (you can also type a date, "7 Dec"). Or drag the ◆ on the chart. |
| See why a date is what it is | Click the date under Expected delivery: a short note lists the reasons in plain words (who it waits for, what it starts after, how far it is from its deadline). |
| Open an item's settings | Click its name: *can't start before*, *starts after*, a note (up to 120 characters), and Mark as done (a finished item takes no more time, and whatever waited for it can start). Names and notes are only words: editing them never re-plans anything. |
| Try an option | The dock under the chart holds up to three options, each an exact re-plan. Hover one to see it on the chart as dashed bars, Apply to keep it, ⌘/Ctrl Z to take it back. |
| Change the scale | The chart fits the whole plan to the width it has. The Zoom menu offers fixed day, week and month scales. |
| See what sets the end date | Click *what sets the end date?* next to the headline: the chain of work behind the last finish lights up. |
What a row opens (its settings, who works on it, why its date, the deadline calendar) is docked right under that row and stays there: it scrolls with the page and lies over the options dock, which never moves. One is open at a time, and it closes by itself when its row scrolls out of sight behind the dock.
Undo is ⌘/Ctrl Z, redo ⇧⌘Z (Ctrl Y). Export gives the plan file, Excel, CSV, an image of the chart (with the same columns and key) and a Markdown summary.
If dragging ever misbehaves in your browser, add #debug to the address. Every row then carries a small tag at the place the page has measured it to be, and each