MCP server
Connect your AI assistant.
Add detectdown as a remote MCP connector, then ask for current service status from the same place you already work.
Choose your client
Jump to the setup path that matches your app.
Copy the server URL.
https://detectdown.me/mcp
Add it to your AI client.
Choose custom connector, remote MCP server, or HTTP server, then paste the URL.
Verify and allow.
Sign in with your email in the browser window, click Allow, then confirm detectdown is enabled or available in your client.
After authorization
Ask one status question.
Return to your client, select or enable detectdown if needed, then paste this prompt to confirm the connector can read cached status.
A successful answer should clearly come from detectdown: it names GitHub's service status and includes last-known or freshness context.
If the client gives a generic assistant answer instead, enable, select, or trust detectdown in the client tools list and retry the same prompt.
- Check GitHub for me
Client setup guides
claude.ai and Claude DesktopConnectors
Prerequisite: individual Claude accounts add custom connectors from Customize > Connectors when the option is available. On Team or Enterprise, an owner adds the custom connector for the organization before members connect to it. Claude Free accounts can have one custom connector.
Source: Anthropic Support, remote MCP custom connectors; reviewed July 2026.
- For an individual account, open Customize, then Connectors.
- Click the + button, choose Add custom connector, and paste exactly
https://detectdown.me/mcpas the server URL. - For Team or Enterprise, an owner adds the custom connector for the organization first; members then connect to that owner-configured connector.
- Claude reaches remote connectors from Anthropic cloud infrastructure, not from your local machine.
- Click Connect or Authorize. A browser sign-in should open for detectdown OAuth and email verification.
- Verify your email and click Allow. In the current Claude conversation, open the plus button or Search and tools menu, choose Connectors, enable or select detectdown, then ask the verification prompt below to confirm Claude can read cached status.
- Check GitHub for me
Claude CodeTerminal
Prerequisite: use a current Claude Code CLI with remote HTTP MCP support. If the browser sign-in never opens, update Claude Code and rerun the command from a terminal that can launch your browser.
Source: Claude Code Docs, connect to MCP servers; reviewed July 2026.
- Remote HTTP is the intended transport. Run this command in your project terminal:
claude mcp add --transport http detectdown https://detectdown.me/mcp - Follow the browser sign-in, verify your email, and click Allow.
- Run
claude mcp list.✓ Connectedmeans detectdown is ready;! Needs authenticationmeans open/mcpin Claude Code and choose Authenticate;! Connected · tools fetch failedmeans runclaude mcp get detectdownfor the error detail. - Return to Claude Code and ask the verification prompt below.
- Check GitHub for me
ChatGPTApps
Prerequisite: use ChatGPT on the web. OpenAI documents Apps, developer mode, and full MCP support for Business and Enterprise/Edu workspaces. Business admins or owners enable developer mode and create apps; Enterprise/Edu admins or owners can also use RBAC to authorize developers. OpenAI also notes Pro users can connect MCPs with read/fetch permissions in developer mode, while full MCP support remains Business and Enterprise/Edu.
Source: OpenAI Help Center, Developer mode and MCP apps in ChatGPT; reviewed July 2026.
- For Business, an admin or owner enables developer mode and creates the app from Workspace Settings > Apps > Create.
- For Enterprise/Edu, an admin or owner can grant developer mode access with RBAC; authorized developers then enable it from Settings > Apps > Advanced Settings and create the app from Settings > Apps > Create.
- Enter app name
detectdown, descriptionChecks current monitored service status from cached detectdown verdicts., and MCP server URLhttps://detectdown.me/mcp. - Pick the authentication mechanism, click Scan Tools, complete the detectdown OAuth email sign-in if ChatGPT prompts for it, then wait for the tool scan to finish.
- Click Create to save the app.
- Open a new chat, confirm detectdown is available from the tools menu or the plus button near the composer under More, select it or refer to it in your prompt, then ask the verification prompt below.
- Check GitHub for me
CursorTools & MCP
Prerequisite: use a current Cursor build with MCP enabled for the profile you are signed into. If Tools & MCP is missing or OAuth does not open, update Cursor and check the active profile.
Source: Cursor Docs, Model Context Protocol (MCP); reviewed July 2026.
- Open Cursor Settings, then Tools & MCP.
- Choose Add custom MCP and paste
https://detectdown.me/mcp. - Connect, finish the OAuth sign-in, return to Cursor, confirm detectdown is enabled in Tools & MCP and its tools are visible, then ask the verification prompt below.
- Check GitHub for me
VS Code with CopilotCommand Palette
Prerequisite: use GitHub Copilot Chat in Agent mode with MCP support enabled. If MCP: Add Server is missing, update VS Code and Copilot, then check whether your organization allows MCP servers.
Source: VS Code Docs, add and manage MCP servers; reviewed July 2026.
- Open the Agent Customizations editor or the Command Palette.
- Run
MCP: Add Server, choose HTTP server, and pastehttps://detectdown.me/mcp. - Or add this remote HTTP server to your VS Code
mcp.json:{ "servers": { "detectdown": { "type": "http", "url": "https://detectdown.me/mcp" } } } - When VS Code asks, trust the server configuration and start detectdown, then continue with the browser sign-in.
- Follow the browser sign-in, verify your email, click Allow, return to VS Code agent mode, confirm detectdown is trusted, started, and available in the MCP servers list, then ask the verification prompt below.
- Check GitHub for me
If setup stalls
Check the basics, then retry.
- Paste the exact
https://detectdown.me/mcpURL as a remote or HTTP MCP server. - Update your client if OAuth does not open or tool scanning is missing.
- For work accounts, check whether workspace or organization policy allows MCP servers.
- Retry the email-code sign-in, then return to your client and check that detectdown is enabled, trusted, selected, or listed as connected.
Try asking
- Detect if Slack is down in Columbus
- What services are having issues right now?
- Check GitHub for me