Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Monitor websites, servers, domains and SSL with InfraNest, and ask your AI assistant what is down.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.infranest.io/mcpRun this in your terminal
claude mcp add --transport http infranest https://api.infranest.io/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"infranest": {
"url": "https://api.infranest.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"infranest": {
"type": "http",
"url": "https://api.infranest.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://api.infranest.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain infranest.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.1.1) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Safe Fetch
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
MCP server for fetching URLs, safe against SSRF, DNS rebinding, and redirect-to-internal attacks.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.