NoContext — Monitor de Uptime para Servidores MCP
kyleloving/nocontext
Monitore saúde de servidores MCP públicos com GitHub Actions e Pages
Ver no GitHubSistema de monitoramento de disponibilidade para servidores MCP públicos, executado automaticamente via GitHub Actions a cada 15 minutos. Valida a saúde dos servidores através do handshake MCP (JSON-RPC 2.0) e publica um painel de status em tempo real via GitHub Pages, sem dependência de serviços externos ou banco de dados.
Instalação
npx convez-ai kyleloving/nocontext1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Rastrear disponibilidade de servidores MCP em produção
- Detectar falhas de conectividade ou respostas malformadas em tempo real
- Manter histórico público de uptime/downtime de servidores MCP
Veredito

Ferramenta prática e minimalista para o ecossistema MCP. Usa bem os limites gratuitos do GitHub (Actions + Pages) sem overhead; bom para times que já hostam em GitHub e precisam validar saúde de servidores públicos.
README
A tradução para o português deste README ainda está na fila.
NoContext
Uptime monitoring for public MCP servers — because when your server is down, your AI has no context.
How it works
- GitHub Actions runs
scripts/check.pyevery 15 minutes. - The script sends an MCP
initializehandshake (JSON-RPC 2.0) to each server. - Results are written to
docs/data/status.jsonand committed back to the repo. - GitHub Pages serves
docs/index.html, which fetches the JSON at runtime.
No external services, no database — just git and GitHub Actions.
Adding a server
Edit config/servers.yml:
servers:
- name: "My MCP Server"
url: "https://my-mcp-server.example.com"
transport: http
tags: [custom]
Open a PR and it will be included in the next check run.
What counts as "up"?
The checker POSTs an MCP initialize request and expects a valid JSON-RPC 2.0 response (result or error at the top level). Servers that respond with HTTP 401/403 (auth required) are treated as up — they're reachable, just need credentials.
| Status | Meaning |
|---|---|
| 🟢 up | Valid MCP response received |
| 🟡 degraded | Reachable but response is malformed |
| 🔴 down | Timeout, connection refused, or HTTP error |
Local development
pip install requests pyyaml
python scripts/check.py
# opens docs/index.html in your browser to preview
Setup for your own fork
- Fork this repo.
- Go to Settings → Pages → set source to
docs/onmain. - Go to Settings → Actions → General → enable "Read and write permissions" for the Actions workflow.
- The first run will populate
docs/data/status.jsonand the status page will go live.
Contributing
PRs to add new public MCP servers are welcome. Please verify the server is publicly accessible before submitting.