# nimo [Health: Active]

**Category:** 📊 Monitoring  
**Repository:** https://github.com/marvtub/nimo-mcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/nimo

## Description
Website monitoring: uptime alerts, page speed and Core Web Vitals with the next fix, cron check-ins.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What nimo MCP server does

The nimo MCP server gives supported AI assistants access to website and job-monitoring data from nimo. It can retrieve the latest uptime result, response time, recent availability, and any active outage for a monitored site. For performance investigations, it exposes site records and current Core Web Vitals, including metrics such as Largest Contentful Paint, Cumulative Layout Shift, and server response time.

The server also handles scheduled-job check-ins. You can create a check-in for a cron job, backup, or similar recurring process, list existing check-ins, confirm whether the first signal arrived, and remove a check-in when it is no longer needed. nimo can notify users through Slack or Telegram when a monitored site goes down and when it recovers.

As a 📊 Monitoring service, it fits workflows that need an assistant to answer questions about availability, page regressions, or missed operational jobs using recorded checks rather than an unverified guess.

## How it works

Connect an MCP client to `https://api.heynimo.com/mcp-server`. The endpoint uses streamable HTTP and is hosted remotely, so the standard setup does not require a local process. Sign-in takes place through the browser. Clients that cannot complete browser authentication can use a nimo API key as a bearer token instead.

Site checks run every five minutes, with a second check before an alert is sent. Performance data comes from real Chrome visitors when available and from Lighthouse measurements. A scheduled job reports success by requesting a unique ping URL after it completes; if the expected ping does not arrive, nimo can alert you.

## Setup and configuration

Add the hosted URL in Claude, Cursor, Codex, Windsurf, or VS Code using the client’s MCP configuration. Claude Code supports the `claude mcp add` command, and Codex provides an equivalent `codex mcp add` command. Cursor and VS Code also provide install links in the repository instructions.

The nimo MCP server does not require an environment variable for its hosted configuration. If browser sign-in is unavailable, create an API key in nimo under Settings → API keys and send it as `Authorization: Bearer <key>`. Keep that credential in the client’s secret storage rather than committing it.

## Tools and capabilities

Documented tools include:

- `get_uptime_status` for the latest uptime, response time, availability windows, and ongoing outages.
- `list_sites` and `get_site` for monitored sites and their current metrics.
- `add_site` for saving a site for monitoring.
- `add_check_in`, `list_check_ins`, `get_check_in`, and `remove_check_in` for scheduled jobs.

The repository also includes a command-line speed check, a GitHub Action for checking a deployed site, and examples for cron, PostgreSQL backups, GitHub Actions, Kubernetes CronJobs, and Node jobs.

## Limitations and notes

Free checks have hourly and daily limits. The repository documents a CLI minimum-score option that can fail automation when performance drops, plus JSON output for scripts. Clients limited to local stdio servers need a bridge such as `mcp-remote` to reach the hosted endpoint. Performance results may combine real-user Chrome data with Lighthouse data, so the available measurement source can vary by site.

_Full upstream README: https://allmcps.com/mcp/nimo/readme_