What is the key difference between Statuscraft and Statuser?

Statuscraft belongs to the Monitoring category with local stdio execution, while Statuser belongs to the Monitoring category with local stdio execution.

How do I install Statuscraft or Statuser in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Statuscraft and Statuser free or paid?

Statuscraft operates under a Free / Open Source model (No auth required). Statuser operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Statuscraft lists 5 tools with 1 views and 1 GitHub stars. Statuser lists 6 tools with 0 views and 24 GitHub stars.

Can I use both Statuscraft and Statuser together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Statuscraft vs Statuser

In-depth architectural comparison of the Statuscraft and Statuser MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Statuscraft

Monitoring · Local stdio

Quality: 57/100 (Good) | Auth: No auth required

Statuser

Monitoring · Local stdio

Quality: 48/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Statuscraft if you need specialized Monitoring tools running via a local process. Choose Statuser if your workspace requires Monitoring integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Statuscraft when:

You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: get_status, get_all_status, list_services.

Explore Statuscraft Details

Choose Statuser when:

You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: STATUSER_API_KEY.
Primary tools included: Service monitoring and status history, Incident diagnostics, summaries, reports, and comments, Status-page and maintenance management.

Feature & Specification Comparison

Specification	Statuscraft jabbawocky Monitoring	Statuser Monitoring
Summary	MCP server that checks the live status of 3831 software services in real time. Ask your AI agent "is GitHub down?" or "what's wrong with Sentry?" — and get a live answer pulled directly from official status pages, including full incident detail when something is broken. npx -y github:jabbawocky/statuscraft	Monitor services, manage incidents and status pages in Statuser.cloud from your AI assistant.
Category & Scope	Monitoring

Tools & Capabilities Breakdown

Statuscraft Tools (5)

get_status

Check the live status of a specific service (e.g. 'github', 'openai', 'stripe'). Returns operational/degraded/partial_outage/major_outage/maintenance.

get_all_status

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_services

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_multiple

Check the live status of a specific list of services in parallel. Faster than calling get_status repeatedly.

refresh_status

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.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Statuscraft Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "jabbawocky-statuscraft": {
      "command": "npx",
      "args": [
        "-y",
        "github:jabbawocky/statuscraft"
      ]
    }
  }
}

Statuser Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "statuser": {
      "command": "npx",
      "args": [
        "-y",
        "@statuser/mcp"
      ],
      "env": {
        "STATUSER_API_KEY": "YOUR_STATUSER_API_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

Statuscraft is categorized under Monitoring and uses a local stdio subprocess. In contrast, Statuser belongs to Monitoring using local stdio subprocess. Select Statuscraft when you need capabilities focused on monitoring and Statuser when you require tools for monitoring.

More alternatives to Statuscraft More alternatives to Statuser Monitoring category hub