Serveur MCP Pingstack
Commit 10 nov. 2026Permet à un client IA de surveiller les tâches cron, les sites web, le DNS, les certificats SSL et l'expiration des domaines, tout en gérant les tableaux de bord et les alertes.
Aussi connu sous atomicvan/pingstack-mcp, pingstack-mcp
- Étoiles
- 0
- Outils
- 33
- Téléchargements, 30 jours
- —
- Dernière version
- 1.2.0
- Dernier commit
- 10 nov. 2026
- Licence
- MIT
Qu'est-ce que Pingstack MCP ?
Pingstack est un serveur MCP. Permet à un client IA de surveiller les tâches cron, les sites web, le DNS, les certificats SSL et l'expiration des domaines, tout en gérant les tableaux de bord et les alertes. Il expose 33 outils, comme get_account_capabilities, list_checks, get_check.
Résumé généré à partir du README du projet
À propos du MCP server Pingstack
Pingstack fournit un MCP server distant qui permet aux agents de codage de gérer des tâches de surveillance complètes. Les développeurs peuvent l'utiliser pour superviser des tâches cron via des contrôles de type heartbeat, surveiller la disponibilité des sites web, vérifier les ports TCP et suivre les enregistrements DNS, les certificats SSL ainsi que l'expiration des domaines. Le serveur est hébergé chez Pingstack, ce qui signifie qu'aucune installation locale n'est requise, et il se connecte via streamable HTTP en utilisant OAuth dans un navigateur ou une clé API.
Les utilisateurs peuvent interagir avec 35 outils différents pour gérer les incidents, les groupes de notification et les tableaux de bord. Le système permet de créer des tableaux de bord privés ou de les publier en tant que pages de statut publiques. Bien que le service soit gratuit jusqu'à 15 vérifications, il s'intègre à divers clients comme Claude Code, Cursor et GitHub Copilot CLI. Il propose également des Agent Skills spécialisées pour Claude Code et Cursor afin d'automatiser des workflows complexes, comme la mise en place de la surveillance de tâches cron ou la génération de rapports de disponibilité.
Ce que vous pouvez faire avec
- 1Automatiser la surveillance des tâches cronUn agent peut lire le calendrier d'une tâche et créer un contrôle heartbeat correspondant avec une période de grâce spécifique.
- 2Générer des pages de statut pour les clientsVous pouvez demander à une IA de construire un tableau de bord pour un client spécifique et de le publier en tant que page de statut publique.
- 3Analyser l'historique des incidentsLes développeurs peuvent demander des détails concernant les interruptions de service récentes, y compris leurs causes et leur durée.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer Pingstack MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller Pingstack MCP dans Claude Code
$ claude mcp add --transport http pingstack-mcp https://app.pingstack.io/mcpInstaller Pingstack MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"pingstack-mcp": {
"url": "https://app.pingstack.io/mcp"
}
}
}Installer Pingstack MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"pingstack-mcp": {
"type": "http",
"url": "https://app.pingstack.io/mcp"
}
}
}Installer Pingstack MCP dans VS Code CLI
$ code --add-mcp '{"name":"pingstack-mcp","type":"http","url":"https://app.pingstack.io/mcp"}'Installer Pingstack MCP dans Codex
$ codex mcp add pingstack-mcp --url https://app.pingstack.io/mcpInstaller Pingstack MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.pingstack-mcp] url = "https://app.pingstack.io/mcp"
Installer Pingstack MCP dans Gemini CLI
$ gemini mcp add -s user --transport http pingstack-mcp https://app.pingstack.io/mcpInstaller Pingstack MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"pingstack-mcp": {
"url": "https://app.pingstack.io/mcp",
"type": "http"
}
}
}Outils MCP Pingstack 33
Détectés depuis le READMEget_account_capabilitieslist_checksget_checkcreate_checkupdate_checkget_check_historylist_check_runsget_check_metricsget_check_uptimelist_incidentsget_incidentcreate_incident_update
| get_account_capabilities | — | |
| list_checks | — | |
| get_check | — | |
| create_check | — | |
| update_check | — | |
| get_check_history | — | |
| list_check_runs | — | |
| get_check_metrics | — | |
| get_check_uptime | — | |
| list_incidents | — | |
| get_incident | — | |
| create_incident_update | — |
Afficher les 33 outilsAfficher moins d'outils
list_notification_groupslist_account_memberslist_rosterscreate_notification_groupupdate_notification_groupassign_notification_grouplist_dashboardsget_dashboardcreate_dashboardupdate_dashboardattach_check_to_dashboarddetach_check_from_dashboardreorder_dashboard_checkscreate_dashboard_sectionupdate_dashboard_sectionpublish_dashboardget_check_ping_urlsdelete_checkdelete_dashboarddelete_notification_groupunpublish_dashboard
| list_notification_groups | — | |
| list_account_members | — | |
| list_rosters | — | |
| create_notification_group | — | |
| update_notification_group | — | |
| assign_notification_group | — | |
| list_dashboards | — | |
| get_dashboard | — | |
| create_dashboard | — | |
| update_dashboard | — | |
| attach_check_to_dashboard | — | |
| detach_check_from_dashboard | — | |
| reorder_dashboard_checks | — | |
| create_dashboard_section | — | |
| update_dashboard_section | — | |
| publish_dashboard | — | |
| get_check_ping_urls | — | |
| delete_check | — | |
| delete_dashboard | — | |
| delete_notification_group | — | |
| unpublish_dashboard | — |
Vérifications automatisées
Exécuté le 14 nov. 2026Rapport complet →Pas encore vérifié. Un serveur nécessite un score de 80, aucune faille sérieuse et suffisamment de données pour que nous puissions effectuer les vérifications. Fonctionnement des vérifications · Ce qu'il faut corriger pour gagner des points
- Dépôt source lié et accessibleatomicvan/pingstack-mcp is public and reachablegithub.com/atomicvan/pingstack-mcp ↗Réussi
- Le nom du package correspond au dépôt sourceNon vérifié
- Provenance du build (attestation Sigstore)Non vérifié
- Licence open source (OSI)MITspdx.org/licenses/MIT.html ↗Réussi
- Commit ou version publiée au cours de l'année écouléeLast commit or release 2026-11-10github.com/atomicvan/pingstack-mcp ↗Réussi
- OpenSSF ScorecardNon vérifié
- Nom du package non proche d'un package populaireNon vérifié
- Aucun avis critique dans le package ou ses dépendancesNon vérifié
- Aucune instruction cachée destinée au modèle33 tool descriptions and the README read; no override phrases, credential paths or hidden charactersRéussi
- Les outils destructifs sont étiquetésNon vérifié
- Le point de terminaison distant répond à la poignée de main MCPHTTPS endpoint answered 401 (sign-in required)Réussi
README
Voir sur GitHubPingstack MCP server
Pingstack monitors cron jobs and scheduled tasks with heartbeat checks, and checks websites, TCP ports, DNS records, SSL certificates and domain expiry. Its MCP server lets your coding agent set up that monitoring and read the results for you.
Ask your agent to add a heartbeat check for the backup job it just wrote, with the right cron schedule, time zone and grace period. Ask which checks had incidents last week, why, and how long they were down. Ask it to build a dashboard for a client, publish it as a status page and set up who gets alerted.
This repository holds the setup files and directory listings for the hosted server. The server itself runs at Pingstack, so there's nothing to install or run locally.
| Endpoint | https://app.pingstack.io/mcp |
| Transport | Streamable HTTP (stateless, JSON responses) |
| Sign-in | OAuth in your browser, or an API key |
| Price | Free for 15 checks. MCP is included on every plan |
| Docs | docs.pingstack.io/mcp |
Connect
You need a Pingstack account. Sign up free, then add the server to your client. Leave out any Authorization header: the client opens your browser, an Owner or Admin picks the Pingstack account, and you approve the connection. Clients register themselves, so there's no client ID or secret to copy.
Claude Code
claude mcp add --transport http pingstack https://app.pingstack.io/mcp
Then run /mcp, choose pingstack and sign in. Add --scope user to use it
in every project. You can also install it as a plugin, which adds the
skills below:
/plugin marketplace add atomicvan/pingstack-mcp
/plugin install pingstack@pingstack
Claude (claude.ai and Claude Desktop)
Go to Settings → Connectors, choose Add custom connector, name it
Pingstack and enter https://app.pingstack.io/mcp.
GitHub Copilot CLI
copilot mcp add --transport http pingstack https://app.pingstack.io/mcp
If /mcp shows needs-auth, run /mcp auth pingstack.
VS Code with Copilot
Run MCP: Add Server from the Command Palette, choose HTTP and enter
the URL. Or add it to .vscode/mcp.json:
{
"servers": {
"pingstack": {
"type": "http",
"url": "https://app.pingstack.io/mcp"
}
}
}
Cursor
Add this to ~/.cursor/mcp.json, then sign in from Cursor's MCP settings:
{
"mcpServers": {
"pingstack": {
"url": "https://app.pingstack.io/mcp"
}
}
}
OpenAI Codex
codex mcp add pingstack --url https://app.pingstack.io/mcp
codex mcp login pingstack
Google Antigravity
Install the plugin in the antigravity folder with the Antigravity CLI. The
app picks it up too. You sign in in the browser the first time it connects:
git clone https://github.com/atomicvan/pingstack-mcp
agy plugin install ./pingstack-mcp/antigravity
Or add this to ~/.gemini/config/mcp_config.json, then click Authenticate
next to pingstack under Agent settings → Customizations:
{
"mcpServers": {
"pingstack": {
"serverUrl": "https://app.pingstack.io/mcp"
}
}
}
Gemini CLI
Install it as an extension:
gemini extensions install https://github.com/atomicvan/pingstack-mcp
Then run /mcp auth pingstack.
The client setup guide covers each client in more detail, plus how to use an API key when your client can't sign in through a browser.
Tools
The server has 35 tools. Your client only sees the ones the connection has permission for.
Checks
| Tool | What it does |
|---|---|
get_account_capabilities |
Account, plan limits, usage, a count of checks by status, time zone and the fields each check type accepts |
list_checks |
List and filter checks, by one status or several |
get_check |
One check's settings, status, why it's down, last run and expiry date |
create_check |
Create a heartbeat, website, TCP, DNS, SSL certificate or domain check |
update_check |
Change a check's settings |
get_check_history |
Daily runs, latency and incidents for up to a year |
list_check_runs |
Individual runs for up to 90 days |
get_check_metrics |
Latency percentiles, by probe region or DNS resolver |
get_check_uptime |
Uptime over 7 days to a year |
Incidents
| Tool | What it does |
|---|---|
list_incidents |
Incidents with their cause, newest first, filtered by check and state |
get_incident |
One incident |
create_incident_update |
Post a status update on an incident |
Notification groups
| Tool | What it does |
|---|---|
list_notification_groups |
Alert groups, with their members and rosters |
list_account_members |
People on the account |
list_rosters |
On-call rosters |
create_notification_group |
Create a group from people and rosters already on the account |
update_notification_group |
Rename a group or change who it alerts |
assign_notification_group |
Add a group to many checks, or to every check on a dashboard |
Dashboards and status pages
| Tool | What it does |
|---|---|
list_dashboards |
Dashboards and status pages |
get_dashboard |
One dashboard, its sections and its checks |
create_dashboard |
Create a private dashboard, with checks already on it if you like |
update_dashboard |
Change a dashboard's name and display settings |
attach_check_to_dashboard |
Add one check or several to a dashboard |
detach_check_from_dashboard |
Remove a check from a dashboard |
reorder_dashboard_checks |
Reorder a dashboard's checks |
create_dashboard_section |
Add a section heading to a dashboard |
update_dashboard_section |
Rename a section or set which checks it holds |
publish_dashboard |
Make a dashboard a public status page (account Admins only) |
Off unless you turn them on
These permissions start unticked when you approve a connection, each with a Sensitive badge. Tick one only if your agent needs it.
| Tool | What it does |
|---|---|
get_check_ping_urls |
A heartbeat check's ping URLs, which work as credentials |
pause_check, resume_check |
Pause a check and resume it. A paused check sends no alerts |
delete_check |
Delete a check and its history for good |
delete_dashboard |
Delete a private dashboard. Its checks are kept |
delete_notification_group |
Delete an alert group |
unpublish_dashboard |
Take a status page offline |
A connection can delete 10 items a minute. A few minutes after it deletes anything, the account owner gets an email listing what was deleted.
History goes back as far as your plan keeps it. See the tool reference for every argument.
Skills
The Claude Code and Cursor plugins come with three skills. Each one walks your agent through a whole job, so you don't have to prompt every step.
| Skill | What it does |
|---|---|
monitor-cron-job |
Reads a job's schedule, creates a matching heartbeat check and adds the ping to the job |
client-dashboard |
Builds a dashboard for a client or team, organizes it into sections and sets up who gets alerted |
uptime-report |
Writes up uptime, incidents and their causes for a dashboard or the whole account |
In Claude Code, run one with /pingstack:monitor-cron-job, or describe what
you want and Claude picks the skill. The skills are plain Markdown in the
skills folder.
What it won't do
The server can't invite people, add notification channels such as email, Slack or SMS, edit rosters, change status page branding or domains, change a check's type or buy anything. Those stay in the Pingstack app. It never sends a test alert or runs a check on demand.
Every connection is limited to one account, to the permissions approved when it was connected, and to the approving person's current role. At a plan limit it tells your agent the limit and returns an upgrade link for a person to open.
Example prompts
- Add a daily heartbeat for the backup job with a 15 minute grace period and put it on the Infrastructure dashboard.
- Which checks had incidents in the last 7 days, what caused them, and how long were they down?
- Create a dashboard for the Northstar client with their checks in two sections, then a notification group with Alex and me in it, and alert that group for every check on the dashboard.
- Pause the staging checks while we migrate the database, and resume them when I say so.
- Create website and SSL certificate checks for every domain in this README.
- What's the p95 latency for the API check over the last 30 days?
- How many checks do I have left on my plan?
Support
- Docs: docs.pingstack.io
- Email: support@pingstack.io
- Privacy policy: pingstack.io/privacy-policy
- Terms: pingstack.io/terms-conditions
Please report security issues to support@pingstack.io rather than opening a public issue.
License
The files in this repository are under the MIT License. The Pingstack service is covered by its terms.
Questions sur Pingstack MCP
Comment ajouter Pingstack MCP à Claude Code ?
Exécutez claude mcp add --transport http pingstack-mcp https://app.pingstack.io/mcp dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter Pingstack MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Quels outils Pingstack MCP fournit-il ?
Il expose 33 outils, dont get_account_capabilities, list_checks, get_check, create_check, update_check.
Combien coûte l'utilisation du service ?
Le service est gratuit jusqu'à 15 vérifications, et le MCP est inclus dans tous les forfaits.
Dois-je installer quelque chose localement ?
Non, le serveur est hébergé chez Pingstack, il n'y a donc rien à installer ou à exécuter sur votre machine locale.
L'agent peut-il envoyer des alertes de test ou lancer des vérifications à la demande ?
Non, le serveur n'envoie pas d'alertes de test et ne lance pas de vérifications à la demande.