Add StatusCraft to Monitoring & Observability#32
Open
jabbawocky wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
StatusCraft — live service status MCP server
Adds StatusCraft to the Monitoring & Observability section.
What it does: Real-time status monitoring for 141 major services that DevOps teams depend on — GitHub, AWS, Stripe, Datadog, Sentry, PagerDuty, CircleCI, Cloudflare, Vercel, and many more. Ask Claude "is GitHub down?" and get a live answer with full incident detail when something is broken.
Why it belongs here: DevOps practitioners monitoring deployments need to know if upstream dependencies are down. StatusCraft surfaces this in natural language — no manual status page checking, no extra tooling.
Key details:
npx -y github:jabbawocky/statuscraft, no API key neededHappy to provide any additional context.