Combien d'outils expose app.stackpulse/mcp ?

app.stackpulse/mcp expose 16 outil(s). Le coût de contexte pour les charger tous est d'environ 8435 tokens (coût unique au chargement, pas par appel).

accueil / serveurs / Recherche & Web / app.stackpulse/mcp

app.stackpulse/mcp

serveur MCP (Model Context Protocol) · stackpulse 1.0.0

▸ Recherche & Web

[ Non encore testé ]

Verdict MCP Hub
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.

streamable-httpType / transport

directAccès

~8435 tokensCoût de contexte

16Outils

Est-ce que app.stackpulse/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « app.stackpulse/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 16 outils

add_monitor≈ 414 tokens
Watches a website or API endpoint on a dashboard: checks the address once first, and refuses what the app refuses (private addresses, other ports, past the plan). Without a name, the page’s title names it. Headers and request bodies stay in the app.
Paramètres, retour & exemple (3)
Paramètres
- url · string · requis
  The address to watch, e.g. "https://shop.example.com"
- name · string · optionnel
  What to call it; the page’s title when left out
- dashboard · string · requis
  A dashboard’s name or id
Exemple d'appel
```
{"name": "add_monitor", "arguments": {"url": "texte", "dashboard": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "name": "texte", "test": {}, "display": "texte", "dashboard": {}}}
```
add_services≈ 269 tokens
Adds services to a dashboard by slug (search_services finds them), within the plan’s limit.
Paramètres, retour & exemple (2)
Paramètres
- services · array · requis
  Slugs, e.g. ["github", "vercel"]
- dashboard · string · requis
  A dashboard’s name or id
Exemple d'appel
```
{"name": "add_services", "arguments": {"services": [], "dashboard": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"added": [], "already": [], "notFound": [], "services": 1}}
```
check_monitor≈ 1017 tokens
Checks one of the account’s URL monitors now, as Check now does in the app, and says what it got.
Paramètres, retour & exemple (1)
Paramètres
- monitor · string · requis
  The monitor’s name, address or id
Exemple d'appel
```
{"name": "check_monitor", "arguments": {"monitor": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"check": "texte", "checked": true, "monitor": {}}}
```
create_dashboard≈ 308 tokens
Makes a dashboard with a name and, optionally, services by slug (search_services finds them), within the plan’s dashboards and services. Answers with its address.
Paramètres, retour & exemple (2)
Paramètres
- name · string · requis
  The dashboard’s name, e.g. "Checkout"
- services · array · optionnel
  Slugs to start with, e.g. ["stripe", "shopify"]
Exemple d'appel
```
{"name": "create_dashboard", "arguments": {"name": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "url": "texte", "name": "texte", "added": [], "notFound": [], "services": 1}}
```
get_incident_history≈ 793 tokens
Incidents on a dashboard in a window: the ones that started in it (with what else started at the same time) and the ones already going on. As far back as the plan’s history goes.
Paramètres, retour & exemple (4)
Paramètres
- to · string · optionnel
  The window’s end, ISO 8601; now when left out
- days · number · optionnel
  Without from: how many days back from to, 7 by default
- from · string · optionnel
  The window’s start, ISO 8601
- dashboard · string · requis
  A dashboard’s name or id
Exemple d'appel
```
{"name": "get_incident_history", "arguments": {"dashboard": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"to": "texte", "from": "texte", "note": "texte", "started": [], "dashboard": {}, "alreadyGoing": []}}
```
get_monitor≈ 896 tokens
One of the account’s URL monitors: its status, its uptime over the last 30 days (or since it started) with the failed checks apart, response times, its certificate and its latest checks.
Paramètres, retour & exemple (1)
Paramètres
- monitor · string · requis
  The monitor’s name, address or id
Exemple d'appel
```
{"name": "get_monitor", "arguments": {"monitor": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "days": [], "name": "texte", "text": "texte", "since": "texte", "status": "texte", "changes": [], "display": "texte", "last30Days": {}, "lastChecks": [], "notChecked": true, "responseMs": 1}}
```
get_reliability≈ 755 tokens
How reliable a dashboard’s services and URL monitors were over 7, 30 or 90 days: the least reliable first, with the share of time without a reported problem (minor issues count, so one long minor issue makes it low), time in each severity, incidents and recovery, and what tends to break together.
Paramètres, retour & exemple (2)
Paramètres
- days · ? · optionnel
  7, 30 (the default) or 90
- dashboard · string · requis
  A dashboard’s name or id
Exemple d'appel
```
{"name": "get_reliability", "arguments": {"dashboard": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"days": 1, "services": [], "dashboard": {}, "breaksTogether": [], "medianRecoveryMinutes": 1}}
```

get_service≈ 612 tokens

One service’s status from its official status page: what’s wrong, the components with a problem, 90 days of history and recent incidents.

Paramètres, retour & exemple (1)

Paramètres

slug · string · requis
The service’s slug, e.g. "github"; search_services finds it

Exemple d'appel

{"name": "get_service", "arguments": {"slug": "texte"}}

Exemple de retour

{"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "name": "texte", "slug": "texte", "text": "texte", "since": "texte", "status": "texte", "summary": "texte", "checkedAt": "texte", "incidents": [], "components": [], "last90Days": {}, "statusPage": "texte"}}

get_stack_status≈ 803 tokens
What’s going on now on a dashboard: a summary, then every service and URL monitor with a problem, with when the problem began and when its current status did. A URL monitor that’s down lists what started around then. Without a dashboard, every dashboard.
Paramètres, retour & exemple (2)
Paramètres
- include · string · optionnel · problems | all
  "all" for every item, not only the ones with problems
- dashboard · string · optionnel
  A dashboard’s name or id; every dashboard when left out
Exemple d'appel
```
{"name": "get_stack_status", "arguments": {"include": "problems", "dashboard": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"dashboards": []}}
```
list_dashboards≈ 220 tokens
The account’s dashboards (the ones this connection can see), with how many services and URL monitors each has and its worst status now.
Paramètres, retour & exemple (0)
Exemple d'appel
```
{"name": "list_dashboards", "arguments": {}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"dashboards": []}}
```
list_outages≈ 398 tokens
Services reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given.
Paramètres, retour & exemple (2)
Paramètres
- all · boolean · optionnel
  Every service in the catalog with a problem (often around 300), not only the best-known
- limit · integer · optionnel
  How many to list, the newest first; 25 by default
Exemple d'appel
```
{"name": "list_outages", "arguments": {"all": true, "limit": 1}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"total": 1, "services": []}}
```

pause_monitor≈ 891 tokens

Pauses a URL monitor, e.g. during a deploy: an open incident ends, and no alerts go out until it’s resumed.

Paramètres, retour & exemple (1)

Paramètres

monitor · string · requis
The monitor’s name, address or id

Exemple d'appel

{"name": "pause_monitor", "arguments": {"monitor": "texte"}}

Exemple de retour

{"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "days": [], "name": "texte", "text": "texte", "since": "texte", "status": "texte", "changes": [], "display": "texte", "last30Days": {}, "lastChecks": [], "notChecked": true, "responseMs": 1}}

remove_services≈ 253 tokens
Takes services off a dashboard. Their history stays; adding one back shows it again.
Paramètres, retour & exemple (2)
Paramètres
- services · array · requis
  Slugs, e.g. ["heroku"]
- dashboard · string · requis
  A dashboard’s name or id
Exemple d'appel
```
{"name": "remove_services", "arguments": {"services": [], "dashboard": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"removed": [], "services": 1, "notOnDashboard": []}}
```
rename_dashboard≈ 208 tokens
Renames a dashboard. Its status page shares the name.
Paramètres, retour & exemple (2)
Paramètres
- name · string · requis
  Its new name
- dashboard · string · requis
  A dashboard’s name or id
Exemple d'appel
```
{"name": "rename_dashboard", "arguments": {"name": "texte", "dashboard": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "name": "texte", "previousName": "texte"}}
```

resume_monitor≈ 882 tokens

Resumes a paused URL monitor: it’s checked at once and starts fresh.

Paramètres, retour & exemple (1)

Paramètres

monitor · string · requis
The monitor’s name, address or id

Exemple d'appel

{"name": "resume_monitor", "arguments": {"monitor": "texte"}}

Exemple de retour

{"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "days": [], "name": "texte", "text": "texte", "since": "texte", "status": "texte", "changes": [], "display": "texte", "last30Days": {}, "lastChecks": [], "notChecked": true, "responseMs": 1}}

search_services≈ 342 tokens
Finds services in the catalog of 9,700+ status pages by name, with their status now. Use it to find a service’s slug.
Paramètres, retour & exemple (1)
Paramètres
- query · string · requis
  A name, e.g. "github" or "aws"
Exemple d'appel
```
{"name": "search_services", "arguments": {"query": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": "texte", "services": []}}
```

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://stackpulse.app/mcp