[{"data":1,"prerenderedAt":264},["ShallowReactive",2],{"seo-allowlist":3,"connector-instatus":73,"related-instatus":240},[4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72],"activecampaign","ahrefs","airtable","amplitude","asana","avalara","aweber","bamboohr","billcom","bitbucket","brevo-sendinblue","buffer","calendly","clickup","close","confluence","constant-contact","copper","datadog","dialpad","docusign","expensify","figma","freshsales","github","gitlab","gmail","google-adsense","google-calendar","google-drive","google-forms","google-maps","google-sheets","google-slides","greenhouse","hubspot","intercom","jira","jotform","linear","mailchimp","microsoft-teams","miro","mixpanel","mondaycom","notion","outlook","pandadoc","personio","pipedrive","quickbooks-online","recurly","salesforce","sendgrid","sentry","slack","square","stripe","tableau","todoist","trello","typeform","wix","workable","wrike","youtube","zendesk","zoho-crm","zoom",{"id":74,"name":75,"icon":76,"description":77,"provider":78,"authType":79,"availableAuthTypes":80,"apiDocsUrl":81,"authDocsUrl":81,"category":82,"pageCopy":83,"datasets":117},"instatus","Instatus","\u002Fconnectoricons\u002Finstatus.png","Instatus runs your status pages, incidents, monitors, maintenance and on-call. Its MCP server lets your AI app check component health, open an incident or schedule maintenance from a chat. Incident posts are public and can notify subscribers, so ContextGate lets you switch off posting tools, add a policy that warns first, and records every call from Claude, ChatGPT or Cursor.","vendor_mcp","oauth",[79],"https:\u002F\u002Finstatus.com\u002Fhelp\u002Fmcp","Analytics & BI",{"title":84,"description":85,"heading":86,"connect":87,"sections":102,"utmCampaign":116},"Instatus API and MCP for Claude & ChatGPT | ContextGate","Instatus API via MCP: let Claude or ChatGPT check component health and post incident updates. Switch off public posting tools; every call is recorded.","Instatus MCP: status pages and incidents from your AI app",{"heading":88,"steps":89},"Hook Instatus up to Claude, ChatGPT or Cursor",[90,92,94,100],{"text":91},"Click Connect Instatus free and sign in with your Instatus account.",{"text":93},"Reading status pages and incidents is harmless; creating incidents, posting updates and scheduling maintenance can go public and notify subscribers. Switch those off, or keep them on and add a policy that warns before each one.",{"text":95,"link":96,"after":99},"Add ContextGate to your AI app as a connector or MCP server. The steps for each app are on",{"label":97,"href":98},"the Works with page","\u002Fworks-with\u002F",".",{"text":101},"Ask your AI app which components on your status page are degraded right now, then open Activity to see the call.",[103,110],{"heading":104,"bullets":105},"Status and incident work from chat",[106,107,108,109],"List your status pages and check each component's current health.","Open an incident with its affected components, then post updates as it moves to resolved.","Schedule maintenance and post progress updates.","Review past incidents and maintenances with their update history.",{"heading":111,"bullets":112},"Nothing goes public by accident",[113,114,115],"Switch off incident and maintenance posting tools; they're hidden from your AI app and refused if called.","Add a policy that warns or blocks before any call that would notify subscribers.","Activity records every incident and update your AI app posts.","instatus-mcp",[118,128,136,144,152,160,168,176,184,192,200,208,216,224,232],{"name":119,"description":120,"recordCount":121,"type":122,"requiredParams":123,"optionalParams":124,"exampleEndpoint":121,"docsUrl":81,"sampleFields":125,"sampleData":126},"Add Incident Update","Post a public lifecycle update to an Instatus incident and change affected component states. This can send external notifications to page and affected-component subscribers when notify is true.","N\u002FA","tool",[],[],[],[127],{"endpoint":121,"docs":81},{"name":129,"description":130,"recordCount":121,"type":122,"requiredParams":131,"optionalParams":132,"exampleEndpoint":121,"docsUrl":81,"sampleFields":133,"sampleData":134},"Add Maintenance Update","Post a public progress update to an Instatus maintenance, optionally changing its lifecycle, timing, and affected component states. This can send external notifications to page and affected-component ",[],[],[],[135],{"endpoint":121,"docs":81},{"name":137,"description":138,"recordCount":121,"type":122,"requiredParams":139,"optionalParams":140,"exampleEndpoint":121,"docsUrl":81,"sampleFields":141,"sampleData":142},"Create Component","Create a component on an Instatus status page. This changes the page's component configuration and can make the new component and its initial health status publicly visible.",[],[],[],[143],{"endpoint":121,"docs":81},{"name":145,"description":146,"recordCount":121,"type":122,"requiredParams":147,"optionalParams":148,"exampleEndpoint":121,"docsUrl":81,"sampleFields":149,"sampleData":150},"Create Incident","Create an incident on an Instatus status page with optional affected component states. The incident is published publicly by default; notify=true can send notifications to page and affected-component ",[],[],[],[151],{"endpoint":121,"docs":81},{"name":153,"description":154,"recordCount":121,"type":122,"requiredParams":155,"optionalParams":156,"exampleEndpoint":121,"docsUrl":81,"sampleFields":157,"sampleData":158},"Create Maintenance","Schedule or start a maintenance on an Instatus status page. The required notification controls are side-effecting: notify can contact subscribers immediately, while notify_start, notify_end, and notif",[],[],[],[159],{"endpoint":121,"docs":81},{"name":161,"description":162,"recordCount":121,"type":122,"requiredParams":163,"optionalParams":164,"exampleEndpoint":121,"docsUrl":81,"sampleFields":165,"sampleData":166},"Get Component","Get the current health and configuration of one component on an Instatus status page.",[],[],[],[167],{"endpoint":121,"docs":81},{"name":169,"description":170,"recordCount":121,"type":122,"requiredParams":171,"optionalParams":172,"exampleEndpoint":121,"docsUrl":81,"sampleFields":173,"sampleData":174},"Get Incident","Get one Instatus incident with its affected components and update history.",[],[],[],[175],{"endpoint":121,"docs":81},{"name":177,"description":178,"recordCount":121,"type":122,"requiredParams":179,"optionalParams":180,"exampleEndpoint":121,"docsUrl":81,"sampleFields":181,"sampleData":182},"Get Maintenance","Get one Instatus maintenance with its schedule, affected components, automation settings, and update history.",[],[],[],[183],{"endpoint":121,"docs":81},{"name":185,"description":186,"recordCount":121,"type":122,"requiredParams":187,"optionalParams":188,"exampleEndpoint":121,"docsUrl":81,"sampleFields":189,"sampleData":190},"List Components","List components and their current health for one Instatus status page, including child components where present. Pass the response's next_cursor back unchanged to fetch another page.",[],[],[],[191],{"endpoint":121,"docs":81},{"name":193,"description":194,"recordCount":121,"type":122,"requiredParams":195,"optionalParams":196,"exampleEndpoint":121,"docsUrl":81,"sampleFields":197,"sampleData":198},"List Incidents","List incidents for an Instatus status page, optionally including or excluding lifecycle statuses.",[],[],[],[199],{"endpoint":121,"docs":81},{"name":201,"description":202,"recordCount":121,"type":122,"requiredParams":203,"optionalParams":204,"exampleEndpoint":121,"docsUrl":81,"sampleFields":205,"sampleData":206},"List Maintenances","List scheduled and historical maintenances for an Instatus status page.",[],[],[],[207],{"endpoint":121,"docs":81},{"name":209,"description":210,"recordCount":121,"type":122,"requiredParams":211,"optionalParams":212,"exampleEndpoint":121,"docsUrl":81,"sampleFields":213,"sampleData":214},"List Status Pages","List status pages available to the connected Instatus account so an agent can discover page IDs for component, incident, and maintenance operations.",[],[],[],[215],{"endpoint":121,"docs":81},{"name":217,"description":218,"recordCount":121,"type":122,"requiredParams":219,"optionalParams":220,"exampleEndpoint":121,"docsUrl":81,"sampleFields":221,"sampleData":222},"Update Component","Change a component's health or presentation on an Instatus status page.",[],[],[],[223],{"endpoint":121,"docs":81},{"name":225,"description":226,"recordCount":121,"type":122,"requiredParams":227,"optionalParams":228,"exampleEndpoint":121,"docsUrl":81,"sampleFields":229,"sampleData":230},"Update Incident","Edit an existing Instatus incident's name, timing, lifecycle status, affected components, or component states. Setting notify to true sends notifications to page and affected-component subscribers.",[],[],[],[231],{"endpoint":121,"docs":81},{"name":233,"description":234,"recordCount":121,"type":122,"requiredParams":235,"optionalParams":236,"exampleEndpoint":121,"docsUrl":81,"sampleFields":237,"sampleData":238},"Update Maintenance","Fully replace an Instatus maintenance's public message, schedule, lifecycle state, affected components and states, and automation settings. Call INSTATUS_GET_MAINTENANCE first and preserve unchanged v",[],[],[],[239],{"endpoint":121,"docs":81},[241,244,247,249,252,255,258,261],{"id":242,"name":243},"kochava","Kochava for Advertisers",{"id":245,"name":246},"mida","Mida",{"id":47,"name":248},"Mixpanel",{"id":250,"name":251},"nestjs","NestJS Observe",{"id":253,"name":254},"netdata","Netdata",{"id":256,"name":257},"new-relic","New Relic",{"id":259,"name":260},"oneuptime","OneUptime",{"id":262,"name":263},"parsely","Parse.ly",1793790226861]