Schema | StatusCraft

StatusCraft

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
get_statusA	Check the live status of a specific service (e.g. 'github', 'openai', 'stripe'). Returns operational/degraded/partial_outage/major_outage/maintenance.
get_all_statusA	Check the live status of ALL tracked services at once. Returns a summary grouped by status — useful for a quick health check across the stack.
list_servicesA	List services tracked by StatusCraft, with their IDs and tags. Use this to discover service IDs for get_status. Supports name/ID search and tag filtering. Results are paginated (100 per page) — pass page to get more.
check_multipleA	Check the live status of a specific list of services in parallel. Faster than calling get_status repeatedly.
refresh_statusA	Force a fresh live fetch for one or all services, bypassing the 60-second cache. Use this when you need the absolute latest status — e.g. during an active incident or immediately after a known outage ends.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jabbawocky/statuscraft'

If you have feedback or need assistance with the MCP directory API, please join our Discord server