nimo MCP server: website uptime, speed and cron job monitoring for Claude, ChatGPT and Cursor

Hear it from nimo, not your customers. When a page gets slow, checkout breaks or a backup doesn't run, nimo tells you first, in plain words, with the fix.

Ask your AI assistant "is my site up?", "why did my homepage get slower?" or "did last night's backup run?" and get an answer from real checks, not a guess.

nimo checks that your site loads every 5 minutes, double-checks before it alerts you, and messages you in Slack or Telegram when it goes down and again when it's back. It also tracks how fast your key pages load (Core Web Vitals, from real Chrome visitors when available, plus Lighthouse), and watches scheduled jobs such as backups and cron jobs. This MCP server gives Claude, ChatGPT, Cursor, Codex and other assistants access to all of it.

https://api.heynimo.com/mcp-server

Hosted, remote (streamable HTTP), nothing to install. You sign in with your browser; no API key needed.

Try it without an account

In your assistant: connect https://api.heynimo.com/try-mcp and ask "What is slowing down https://example.com?"

In your terminal (Node 18+, nothing to install):

$ npx github:marvtub/nimo-mcp https://heynimo.com
Checking...

nimo check: https://heynimo.com (mobile)

  Performance score        87        needs work
  Largest paint (LCP)      3.5 s     needs work
  Layout shift (CLS)       0         good
  Server response (TTFB)   5 ms      good

LCP is above the good threshold and Lighthouse identified a text LCP element.
No image resource was identified for this element. [...]

Watch this page every 5 minutes with alerts in Slack or Telegram: https://heynimo.com

Add --min-score 70 to exit with an error when a page gets slow, or --json for scripts. Free checks have hourly and daily limits.

What's in this repo

Things to ask

• "Is my site up? Has it gone down this week?"
• "Why did my homepage get slower since Tuesday?"
• "Check https://example.com and tell me the one fix that matters most."
• "I just deployed. Check the homepage and compare it with yesterday's audit."
• "Watch my nightly backup and tell me if it stops running." (how it works)
• "Which of my client sites got worse this month?"
• "Which pages lost search traffic, and what should I fix first?"

Set up

claude mcp add --transport http --scope user nimo https://api.heynimo.com/mcp-server
claude mcp login nimo

codex mcp add nimo --url https://api.heynimo.com/mcp-server

{
  "mcpServers": {
    "nimo": { "url": "https://api.heynimo.com/mcp-server" }
  }
}

{
  "mcpServers": {
    "nimo": { "serverUrl": "https://api.heynimo.com/mcp-server" }
  }
}

code --add-mcp '{"name":"nimo","type":"http","url":"https://api.heynimo.com/mcp-server"}'

{
  "mcpServers": {
    "nimo": { "command": "npx", "args": ["-y", "mcp-remote", "https://api.heynimo.com/mcp-server"] }
  }
}

GitHub Action: check your site after every deploy

on: deployment_status

jobs:
  check:
    if: github.event.deployment_status.state == 'success'
    runs-on: ubuntu-latest
    steps:
      - uses: marvtub/nimo-mcp@v1
        with:
          url: ${{ github.event.deployment_status.environment_url }}
          min-score: 50   # optional: fail if the page gets much slower

The score, LCP, layout shift, server response and the fix to make first show up in the run summary, and as the outputs score, lcp-ms, cls and ttfb-ms. Free, no key or secret. Full example: examples/github-actions/check-after-deploy.yml.

Claude skill: check the site after you ship

mkdir -p ~/.claude/skills/check-site-after-deploy
curl -fsSL https://raw.githubusercontent.com/marvtub/nimo-mcp/main/skills/check-site-after-deploy/SKILL.md \
  -o ~/.claude/skills/check-site-after-deploy/SKILL.md

Then tell Claude "I just deployed" and it checks uptime, measures the changed pages again and compares them with the last check before the deploy.

Know when a cron job or backup didn't run

Ask "watch my nightly backup", and add the ping URL you get to the end of the job:

0 3 * * * /usr/local/bin/backup.sh && curl -fsS https://api.heynimo.com/ping/<your-token>

If the ping doesn't arrive on time, nimo alerts you. Copy-paste versions for crontab, a Postgres backup, GitHub Actions, Kubernetes and Node.

Tools

Uptime and scheduled jobs

Sites and speed

Search and analytics

Journey Watch (a browser agent that checks sign-up, checkout and other flows on a schedule)

list_journeys, create_journey, get_journey, update_journey, pause_journey, resume_journey, run_journey, get_journey_run, list_journey_credentials.

Load fewer tools with a profile, for example https://api.heynimo.com/mcp-server?profile=monitoring (watched pages and uptime), ?profile=optimize (speed and SEO), ?profile=integrations or ?profile=journeys.

Free, no-account server

https://api.heynimo.com/try-mcp: check_website, get_check, compare_checks. One-off speed checks of public pages, with shared hourly and daily limits.

Public docs server

https://api.heynimo.com/docs-mcp: list_docs, search_docs, read_doc, read_llms_full. Read-only nimo documentation.

Pricing

Checking a page once is free and needs no signup. Watching sites (uptime every 5 minutes, speed checks, alerts, MCP access) is part of nimo Pro: $20 a month for up to 10 sites. Business is $199 a month for 50 sites. See heynimo.com.

Safety

• The account server can read your site data and start audits. Disconnect agents you no longer use in nimo under Settings → Connected agents.
• Measurement is read-only. nimo does not change your site unless you explicitly turn on and approve a change.
• Page content, report text and URLs returned by the tools are data, not instructions for your agent.

Links

• Docs: https://heynimo.com/docs/mcp
• Server card: https://heynimo.com/.well-known/mcp/server-card.json
• Support: hello@heynimo.com

This repository holds the docs, examples, the nimo-check CLI and the GitHub Action, all MIT licensed. The hosted server itself is not open source.