World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Ryan Lindsey's professional corpus, exposed as MCP tools.
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-09-21 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 4/4 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Ryan Lindsey。按照 https://mcp.popnx.com/i/me-ryanlindsey-ryanlindsey-me.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/4 项检查 · 你的提问会经过开发者的服务器(mcp.ryanlindsey.me) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Ryan Lindseyhttps://mcp.ryanlindsey.me/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsRyan Lindsey
用 Ryan Lindsey 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Ryan Lindsey,或回答中出现 Ryan Lindsey 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Ryan Lindseyhttps://mcp.ryanlindsey.me/mcp开启新聊天,输入前先从插件列表中选择 Ryan Lindsey
用 Ryan Lindsey 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Ryan Lindsey,或回答中出现 Ryan Lindsey 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user ryanlindsey-me https://mcp.ryanlindsey.me/mcp应能看到 Ryan Lindsey 在列表中并显示已连接
用 Ryan Lindsey 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Ryan Lindsey,或回答中出现 Ryan Lindsey 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Ryan Lindsey 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Ryan Lindsey,或回答中出现 Ryan Lindsey 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Ryan Lindsey 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Ryan Lindsey,或回答中出现 Ryan Lindsey 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.ryanlindsey.me/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user ryanlindsey-me https://mcp.ryanlindsey.me/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"ryanlindsey-me": {
"url": "https://mcp.ryanlindsey.me/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"ryanlindsey-me": {
"type": "http",
"url": "https://mcp.ryanlindsey.me/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月14日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
get_contactHow to reach Ryan Lindsey, and his working timezone.
get_resumeRyan Lindsey's résumé: JSON Resume data, the published markdown document, or a short prose summary.
list_case_studiesPublished case studies with their metadata and citation URLs.
get_case_studyThe full markdown of one published case study, by slug.
list_writingPublished posts with their descriptions and citation URLs.
get_postThe full markdown of one published post, by slug.
search_writingSemantic search across the published posts, case studies and résumé. Each result is a passage, the URL it is published at, and an "exact" flag saying whether the excerpt is the passage that matched.
request_private_accessExplains the private access tier and how to request a scoped token.
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过域名 ryanlindsey.me 验证(注册中心会核实域名所有权)
代码最后更新于3天前
不适用:由 ryanlindsey.me 的所有者自己运行的云端服务器,你不会运行仓库里的代码
在 206 毫秒内响应(HTTP 200)
无需登录
已读取 8 个工具描述,未发现针对 AI 的隐藏指令
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/me-ryanlindsey-ryanlindsey-me)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于3天前,最新版本(1.36.0)于2个月前进入注册中心。
支持 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.
| 本项 Ryan Lindsey | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 4/4 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | – | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The code behind ryanlindsey.me: an Astro site on the Cloudflare developer platform, plus a second Worker serving a remote MCP server at mcp.ryanlindsey.me. One repository, two deployed Workers, one shared set of D1, KV, R2, Queues and Analytics Engine resources.
The site is built so that a person and an agent read the same corpus through different doors.
Source-visible so you can read how it is built. There is no LICENSE file, and the absence is deliberate rather than an oversight: no license means all rights reserved, so nothing here is licensed for reuse.
Deploys run on Workers Builds from main, and CI has no deploy step. CLAUDE.md carries the working notes, including the commands, the traps worth knowing before editing, and the reasoning behind the parts that look strange.
Four entrypoints, stable by contract:
| Entrypoint | What it is |
|---|---|
/llms.txt | The curated index, and the place to start |
/.well-known/ard.json | The ARD manifest, also served as ai-catalog.json |
/.well-known/mcp/server-card.json | The server card, served on both origins |
https://mcp.ryanlindsey.me/mcp | The protocol endpoint itself |
This file does not list the rest, and the omission is the part worth reading. Every endpoint this site advertises lives in one list, ADVERTISED_SURFACE in src/lib/discovery/surface.ts, published as both the API catalog and the ARD manifest and checked by tests/discovery-catalog.test.ts. A table here would be a second copy, living outside the test suite, and it would drift the first time an endpoint moved. Fetch the catalog rather than trusting this file.
One thing is missing from that list on purpose. /fit and everything beneath it are unlisted by requirement, and a catalog is a published list of the paths its author finds interesting, so listing one there would un-list it.
flowchart TB
person(["person"]) agent(["agent"])
subgraph site["site Worker (ryanlindsey.me)"] S["pages, posts, case studies, résumé markdown variants, llms.txt, feeds well-known catalogs chat page and the form surfaces"] end
subgraph mcpw["MCP Worker (mcp.ryanlindsey.me)"] G{"grant resolved here, and only here"} T["/mcp, the chat stream, the fit engine"] R[["rate limiter Durable Object"]] G --> T T -->|every tool call spends budget| R end
P[("R2_PRIVATE")]
person --> site agent --> site agent --> mcpw site -->|service binding| mcpw mcpw -->|reads published documents| site T -. "private-docs.ts, the only reader" .-> P
The split into two Workers is not cosmetic. An ai binding in the site's config makes astro build open a remote proxy session that credential-free CI cannot authenticate, so inference lives on the second Worker and the site reaches it over a service binding. Each Worker names the other, and the cycle is deliberate and legal, because a service binding resolves when it is called rather than when the Worker is defined.
The drawing is deliberately incomplete. It carries the structure and leaves out the rest: which storage each Worker touches, which models it calls, the queue consumer, the crons. The site publishes its own drawing of the deployed inventory on /ops, over the one description of this architecture the repository keeps, src/lib/architecture.ts. That page also reports what the system has done lately and what it cost, read at request time rather than asserted here.
Four claims, each paired with the file that proves it rather than with an assurance.
| Claim | Enforced by |
|---|---|
| The private tier is a partition rather than a filter. The public document layer's env interface does not name the private bucket at all. | tests/tier-private-docs.test.ts, at the type level |
An unauthenticated tools/list cannot enumerate a gated tool name, and calling one by name answers unknown-tool rather than a refusal confirming it. | tests/mcp-gated.test.ts, "invisibility without a grant" |
| No test reaches Workers AI, Vectorize, Browser Rendering or a real secret. No deployed config declares the override variables, and an unrecognized value throws. | tests/workers.ts sets them in one place, tests/mcp-env.test.ts keeps them out of both deployed configs, and an unrecognized value throws at the call site, as in src/lib/turnstile.ts |
| The MCP Worker's binding list cannot drift from its wrangler config, in either direction. | tests/mcp-env.test.ts |
Four files, in reading order. They explain the rest.
src/lib/discovery/surface.ts, every endpoint this site advertises, in one list, carrying the reason it is one list and not two.src/lib/tier/grant.ts, the only place a token is verified. The site Worker holds no copy: it treats the token as an opaque string and asks over the service binding, so the boundary has one implementation rather than two that agree.tests/workers.ts, why the suite boots real Workers inside workerd, and what it refuses to reach.src/components/ArchitectureDiagram.astro, for its header rather than its output. That header records that two claims in its own first draft were false, names them, and says what the mistake taught. It is a fair sample of how the rest of this repository is commented.release-please watches main and keeps a release pull request open with the next version and its changelog. Merging that pull request tags the release and publishes it.
Pull requests are squash-merged, so the pull request title is the commit subject release-please reads. A title without a recognized type(scope): summary prefix is skipped silently: no version bump, no changelog entry. feat is a minor bump, fix and perf are patches, and type!: or a BREAKING CHANGE: footer is a major. The full set of types lives in release-please-config.json under changelog-sections.