World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Is an AI tool, agent or MCP server alive, and since when? Checks from the outside, with proof.
作者提供的原文
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-16 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 4/4 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 AgentViva。按照 https://mcp.popnx.com/i/agentviva.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/4 项检查 · 你的提问会经过开发者的服务器(agentviva.dev) · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
AgentVivahttps://agentviva.dev/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsAgentViva
用 AgentViva 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 AgentViva,或回答中出现 AgentViva 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
AgentVivahttps://agentviva.dev/mcp开启新聊天,输入前先从插件列表中选择 AgentViva
用 AgentViva 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 AgentViva,或回答中出现 AgentViva 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user agentviva https://agentviva.dev/mcp应能看到 AgentViva 在列表中并显示已连接
用 AgentViva 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 AgentViva,或回答中出现 AgentViva 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 AgentViva 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 AgentViva,或回答中出现 AgentViva 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 AgentViva 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 AgentViva,或回答中出现 AgentViva 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://agentviva.dev/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user agentviva https://agentviva.dev/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"agentviva": {
"url": "https://agentviva.dev/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"agentviva": {
"type": "http",
"url": "https://agentviva.dev/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月20日
注册名称已通过域名 agentviva.dev 验证(注册中心会核实域名所有权)
代码最后更新于3天前
不适用:由 agentviva.dev 的所有者自己运行的云端服务器,你不会运行仓库里的代码
在 419 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/agentviva)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于3天前,最新版本(1.7.1)于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.
| 本项 AgentViva | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 4/4 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
AgentViva watches AI tools, agents and assistants from the outside and answers one question per target: is it alive, and since when.
This repository is the public reference. The service runs at agentviva.dev; its source is private.
New here? Start with [GETTING-STARTED.md](GETTING-STARTED.md) (also at https://agentviva.dev/docs): how to get access, add what to watch (dashboard, catalog, API or your AI agent), get alerts and show the status.
| File | What it is |
|---|---|
| GETTING-STARTED.md | How to connect and work with AgentViva, step by step |
| api.md | The API reference. The only document an integration should rely on |
| openapi.yaml | The same contract as OpenAPI 3.1, for tooling and generated clients |
| skills/agentviva | A Claude Code skill, so a coding agent knows when to call us |
| CHANGELOG.md | Every change to the public API, newest first |
| SECURITY.md | How to report a vulnerability |
v0.dev to v0.app) is still up, with the reason moved; a redirect to a different name (sold, closed) is degraded.A single failed probe changes nothing. The same verdict has to repeat, ten minutes apart, before AgentViva writes it down or wakes anybody up — and the record says how many probes agreed.
If a target simply refuses us, that is blocked, not down. A tool does not get declared dead for disliking our user agent.
Every state comes with its proof: what our last check saw (the answer, where the redirects ended, the page title, the MCP tools) is on the status page and in the API as evidence.
States are unknown, up, degraded, down and blocked.
curl -X POST https://agentviva.dev/v1/monitors -H "Authorization: Bearer av_live_..." -H "content-type: application/json" -d '{"type":"page","name":"Notion","target":{"url":"https://www.notion.so"},"public":true,"public_slug":"notion"}'
curl "https://agentviva.dev/v1/changes?since=0" -H "Authorization: Bearer av_live_..."
curl https://agentviva.dev/v1/public/aigregator/notion.json
No agent to install, no SDK — one HTTP call per monitor.
A directory does not need to create thousands of monitors itself. Publish one JSON or CSV file with an id, a name and a URL for each tool, and connect its link once:
curl -X PUT https://agentviva.dev/v1/catalog -H "Authorization: Bearer av_live_..." -H "content-type: application/json" -d '{"url":"https://example.com/tools.json"}'
AgentViva reads the list every day. A new tool gets a monitor, a renamed or moved tool is updated, and a tool that left the list is paused, with its history kept. Then ask which ones stopped working: GET /v1/monitors?state=down&source=catalog. See Catalog in the API reference.
A tool that has not worked for 7 days (you choose the number) shows on Needs a decision: in the dashboard, at GET /v1/decisions, and in MCP (list_decisions). For each one you answer keep watching, false alarm, stop watching, or remove from my site. AgentViva never changes your site: it sends your webhook a signed remove_requested message (and lists the tool under status=remove_requested), and your site hides the tool. Stop watching many tools at once with POST /v1/monitors/actions. See Needs a decision.
An AI agent can use AgentViva without writing REST calls. The MCP server at https://agentviva.dev/mcp has 14 tools: list and check monitors, create one, probe now, read recent changes, connect and sync a catalog, pause, resume or stop watching monitors, list the tools that need a decision and answer for them, and look up any tool AgentViva watches publicly. You sign in once in your browser and press Allow; there is no key to copy. In Claude Code:
claude mcp add --transport http agentviva https://agentviva.dev/mcp
Then type /mcp, choose agentviva, then Authenticate. In claude.ai: Settings → Connectors → Add custom connector, with the same address. A client that cannot open a browser can send the API key instead (--header "Authorization: Bearer av_live_..."). No account? https://agentviva.dev/mcp/public has only lookup_tool. See the MCP section of the API reference.
GET https://agentviva.dev/v1/public/<team>/<external_id>.json
GET https://agentviva.dev/badge/ / .svg 180x48 SVG, cached 5 minutes GET https://agentviva.dev/s/ / HTML status page, 90-day history, no JavaScript GET https://agentviva.dev/status the public list of tools, and which are not working now GET https://agentviva.dev/pricing.md plans and prices in Markdown, for agents GET https://agentviva.dev/v1/public/search?q=notion the public tools we already watch, by name or address GET https://agentviva.dev/v1/public/check?url=v0.dev one check of any public site or MCP server, right now POST https://agentviva.dev/v1/public/report {"query":"notion.so"}: tell us a watched tool does not work GET https://agentviva.dev/v1/public/tools.json every public tool and its state: the feed for directories GET https://agentviva.dev/research.json the state of AI tools in numbers (also as a page: /research)
The same check is a form on the home page and at agentviva.dev/check: paste an address, see what we saw. A report never changes a state by itself; it makes us check the tool again (at most once an hour).
A catalog tool's is its id from your list (lower case, with dashes, when the id is not a valid link), so one line in the template of your tool pages gives every tool its badge. The Catalog page in the dashboard shows it.
The badge has seven forms and three themes: add ?style=dot|word|pill|card|seal|strip|panel and &theme=dark|light|auto to the badge link. The default is the dark card.
Agents can find all of this without reading a page: llms.txt, OpenAPI, the ARD catalog and the MCP server card. The MCP server is dev.agentviva/agentviva in the MCP Registry (server.json). In the browser, the home page offers check_url, lookup_tool and report_problem as WebMCP tools.
Signup is not open yet. Email support@agentviva.dev with what you want to watch and we will tell you whether we can help. Keys are issued per team and shown once.
In Claude Code, the plugin brings the skill and the MCP connection.
claude plugin marketplace add AgentViva/docs
claude plugin install agentviva@agentviva
/mcp.Installed it before? Run claude plugin marketplace update agentviva and claude plugin update agentviva@agentviva, then restart Claude Code. All the steps are in GETTING-STARTED.md.
Or with skills.sh, which works with any agent that reads SKILL.md:
npx skills add AgentViva/docs
To read the skill once without installing it:
npx skills use AgentViva/docs@agentviva
AgentVivaBot fetches one page per monitored site at most once an hour (most sites are checked once a day), more often only while confirming a change, never more than 2 MB, and never posts data except to assistant endpoints whose owners configured a canary question. Every request is signed with Web Bot Auth; the keys are at https://agentviva.dev/.well-known/http-message-signatures-directory. Before a website check it reads robots.txt and follows the rules for AgentVivaBot (else *); a page it is asked not to open is blocked, never down. The policy, and how to opt out, is at agentviva.dev/bot.
Example code and the OpenAPI spec are MIT — see LICENSE. The prose documentation is CC BY 4.0. Attribute it to AgentViva with a link to this repository.