Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Monitor websites, servers, domains and SSL with InfraNest, and ask your AI assistant what is down.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://api.infranest.io/mcp在终端中运行这条命令
claude mcp add --transport http infranest https://api.infranest.io/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"infranest": {
"url": "https://api.infranest.io/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"infranest": {
"type": "http",
"url": "https://api.infranest.io/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://api.infranest.io/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 infranest.io 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.1.1)于4天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Apify MCP Server
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
infranest-mcp
Ask your AI assistant about your infrastructure.
What is down, where a hostname points, what expires soon, who changed what. Hosted, nothing to install.
InfraNest is one place for your servers, uptime monitors, incidents, DNS, domains and certificates, across the cloud and DNS providers you already use. This is its hosted Model Context Protocol server. Ask in plain language: what is down right now, which monitors failed last night, where a hostname points, which domains and certificates expire soon, which servers are running out of disk, and who changed what in the audit log.
https://api.infranest.io/mcp
It reads, and changes only what you allow. Every tool reads, except a small on-call set — acknowledge an incident, leave the team a note, silence a monitor, check a monitor again, start or end a maintenance window — which needs write access to Monitoring: an API token with Monitoring write, or Also let it act ticked when you connect. Each of those changes is undone by another, is recorded in your audit log, and your assistant asks before making it. Nothing else can be created, changed or deleted, and it never returns secrets such as domain transfer codes, private keys or tokens. Works on every InfraNest plan, including Free.
Assistants that support sign-in (OAuth) — Claude, ChatGPT, VS Code, Cursor and others: add a custom connector with the URL above, or use a button above. You sign in with your InfraNest account and choose the one organization it may use; it sees only what your role there allows. Remove it any time under My account → Authorized apps.
Assistants that take a header instead — on a plan that includes API tokens (Pro and up), create one in InfraNest (My account → Developer) and send it as a bearer token:
{
"mcpServers": { "infranest": { "url": "https://api.infranest.io/mcp", "headers": { "Authorization": "Bearer " } } } }
Gemini CLI — this repository is a Gemini CLI extension:
gemini extensions install https://github.com/InfraNest-Infrastructure-Organized/infranest-mcp
Gemini CLI opens the InfraNest sign-in the first time a tool is used.
No account yet? Sign up free at infranest.io. A sandbox with sample data lets you try every tool safely.
Step-by-step setup for each assistant: developers.infranest.io/ai-assistants.
| Tool | What it answers |
|---|---|
list_organizations | Which organizations you can read |
status_overview | Is everything up right now — monitors, servers, open incidents, running maintenance |
status_across_organizations | Is anything down in any of your organizations, one line each |
search, fetch | Find anything by name, then read the one you mean in full |
list_servers, get_server | Your servers, cloud and self-managed, filtered by state, provider or tag |
server_attention | What needs attention on a server |
server_metrics, server_metric_history | Servers with their latest CPU, memory and disk figures, and one server's over time |
list_monitors, get_monitor | Your uptime monitors |
monitor_stats, monitor_results | Uptime and response times of a monitor, and its recent check results |
list_incidents, incident_timeline | Incidents and what happened during each |
list_deploys, deploy_changes | Deploys to a monitor or server, and what each changed |
list_dns_zones, list_dns_records | DNS zones and their records |
search_dns, check_dns_name | Where a hostname points across all zones, and everything about one name, live DNS included |
dns_zone_changes, dns_outside_changes | Recent changes to a zone, in InfraNest and made directly at the DNS provider |
list_domains, domain_findings | Domains with expiry and renewal state, and what is wrong with any of them, in one call |
list_certificates | Certificates, with expiry |
list_status_pages | Your public status pages |
list_dynamic_ips | Dynamic IPs and the records they keep up to date |
list_maintenance_windows | Planned maintenance |
search_audit_log | Who changed what, and when |
uptime_report | Monthly uptime report |
read_api | Any other read in the public API |
On-call actions, only with write access to Monitoring:
| Tool | What it does | Undone by |
|---|---|---|
acknowledge_incident, unacknowledge_incident | Marks an incident as yours, stopping repeat alerts and telling the team | each other |
add_incident_note | Leaves the team a note on an incident | — |
create_incident_ticket | Files an incident in your connected Jira, Linear or GitHub and returns the issue's key and link; an incident that already has one keeps it | — |
silence_monitor, unsilence_monitor | Stops a monitor's alerts for a while; it keeps checking | each other |
run_monitor_check | Checks a monitor again now instead of waiting for its schedule | — |
start_maintenance, end_maintenance | Opens a maintenance window, so nobody is paged for planned work, and ends it. It is internal unless given a public notice, the text your status pages show | each other |
Ready-made questions in your assistant's prompt menu:
| Prompt | What you get |
|---|---|
Health check (health_check) | What is down now and what needs attention this month: incidents, servers, domains, certificates, DNS |
Investigate an incident (investigate_incident) | Why something is down: the incident, what it affects, what changed just before it, what to do next |
What changed recently (what_changed) | Everything that changed in a period: settings, deploys, DNS edits in InfraNest and at the provider |
Monthly uptime report (monthly_report) | A report fit to send a customer: uptime against target, each incident with its cause, planned maintenance |
The server itself is hosted by InfraNest; its source is not here. This repository holds what MCP clients and directories read about it:
| File | Read by |
|---|---|
server.json | The official MCP Registry, as io.infranest/infranest |
gemini-extension.json, GEMINI.md | Gemini CLI and its extension gallery |
| This README | You, and the MCP directories that list the server |
CI checks the files against the registry's schema and against each other on every change, and every week checks the tool table above against the tools the live server describes.
Found a problem? Open an issue, or write to support@infranest.io. For a security issue in InfraNest, see infranest.io/security.
The files in this repository are under the Apache License 2.0. Your use of InfraNest is governed by its Terms of Service.