InfraNest

Registre officiel IA et agents

Monitor websites, servers, domains and SSL with InfraNest, and ask your AI assistant what is down.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http infranest 'https://api.infranest.io/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "infranest": {
            "type": "http",
            "url": "https://api.infranest.io/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. infranest-mcp
  2. Connect
  3. Tools
  4. Prompts
  5. What is in this repository
  6. Links
  7. Licence

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.

Connect

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 — create an API token in InfraNest (My account → Developer) and send it as a bearer token:

{
  "mcpServers": {
    "infranest": {
      "url": "https://api.infranest.io/mcp",
      "headers": { "Authorization": "Bearer <your InfraNest API token>" }
    }
  }
}

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.

Tools

ToolWhat it answers
list_organizationsWhich organizations you can read
status_overviewIs everything up right now — monitors, servers, open incidents, running maintenance
status_across_organizationsIs anything down in any of your organizations, one line each
search, fetchFind anything by name, then read the one you mean in full
list_servers, get_serverYour cloud servers, filtered by state, provider or tag
server_attentionWhat needs attention on a server
server_metrics, server_metric_historyServers with their latest CPU, memory and disk figures, and one server's over time
list_monitors, get_monitorYour uptime monitors
monitor_stats, monitor_resultsUptime and response times of a monitor, and its recent check results
list_incidents, incident_timelineIncidents and what happened during each
list_deploys, deploy_changesDeploys to a monitor or server, and what each changed
list_dns_zones, list_dns_recordsDNS zones and their records
search_dns, check_dns_nameWhere a hostname points across all zones, and everything about one name, live DNS included
dns_zone_changes, dns_outside_changesRecent changes to a zone, in InfraNest and made directly at the DNS provider
list_domains, domain_findingsDomains with expiry and renewal state, and what is wrong with any of them, in one call
list_certificatesCertificates, with expiry
list_status_pagesYour public status pages
list_dynamic_ipsDynamic IPs and the records they keep up to date
list_maintenance_windowsPlanned maintenance
search_audit_logWho changed what, and when
uptime_reportMonthly uptime report
read_apiAny other read in the public API

On-call actions, only with write access to Monitoring:

ToolWhat it doesUndone by
acknowledge_incident, unacknowledge_incidentMarks an incident as yours, stopping repeat alerts and telling the teameach other
add_incident_noteLeaves the team a note on an incident—
silence_monitor, unsilence_monitorStops a monitor's alerts for a while; it keeps checkingeach other
run_monitor_checkChecks a monitor again now instead of waiting for its schedule—
start_maintenance, end_maintenanceOpens 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 showeach other

Prompts

Ready-made questions in your assistant's prompt menu:

PromptWhat 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

What is in this repository

The server itself is hosted by InfraNest; its source is not here. This repository holds what MCP clients and directories read about it:

FileRead by
server.jsonThe official MCP Registry, as io.infranest/infranest
gemini-extension.json, GEMINI.mdGemini CLI and its extension gallery
This READMEYou, 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.

Licence

The files in this repository are under the Apache License 2.0. Your use of InfraNest is governed by its Terms of Service.

Questions fréquentes

Qu'est-ce que InfraNest ?

Monitor websites, servers, domains and SSL with InfraNest, and ask your AI assistant what is down.

Comment installer InfraNest ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http infranest 'https://api.infranest.io/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour InfraNest ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

InfraNest est-il open source ?

Oui. Son code est sur GitHub sous licence Apache-2.0.

Qui maintient InfraNest ?

Il est publié par InfraNest-Infrastructure-Organized. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.