Statuscraft vs Vendor Status MCP
A side-by-side look at the Statuscraft and Vendor Status MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Statuscraft for monitoring work as a local process; choose Vendor Status MCP for monitoring. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Statuscraft when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_status, get_all_status, list_services.
Choose Vendor Status MCP when
- You need dedicated capabilities in the Monitoring domain.
- You want tools like
find_vendor, vendor_status, vendors_down_now.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 55/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | 7 |
| Full listing | View Statuscraft | View Vendor Status MCP |
Tools & capabilities
Statuscraft tools 5
get_statusCheck the live status of a specific service (e.g. 'github', 'openai', 'stripe'). Returns operational/degraded/partial_outage/major_outage/maintenance.get_all_statusCheck 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_servicesList 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_multipleCheck the live status of a specific list of services in parallel. Faster than calling get_status repeatedly.refresh_statusForce 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.
Vendor Status MCP tools 7
find_vendorResolve a name, slug or status-page domain to its map entry: status page URL, platform, whether a machine-readable feed exists, and its state in the newest poll.vendor_statusOne vendor's state from the newest daily poll — ok / degraded / partial / major / maintenance / unknown — with the vendor's own status line, open-incident count and the poll timestamp.vendors_down_nowEvery vendor that was not fully operational in the newest poll, worst first, plus counts by state across all 804 polled vendors.vendor_incidentsOne vendor's incident history as its page posted it: title, state, impact, start/resolve times, latest update, link. Filter by date and state.vendor_resolution_timesMedian, 90th percentile, over-24h count and the longest incident on record, from the vendor's own posted start and resolve timestamps.status_feed_urlsThe summary JSON, incidents JSON, RSS and Atom endpoints for one vendor's page, by platform — so a script can poll it directly with no key.dataset_statusVendors mapped, feeds readable, incidents on record and in the last 30 days, platform breakdown, cadence, license, bulk downloads.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Statuscraft
{
"mcpServers": {
"jabbawocky-statuscraft": {
"command": "npx",
"args": [
"-y",
"github:jabbawocky/statuscraft"
]
}
}
}
Vendor Status MCP
No confirmed install command for Vendor Status MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Statuscraft is categorized under Monitoring and uses a local stdio subprocess. Vendor Status MCP belongs to Monitoring and uses an install path we have not confirmed yet. Pick Statuscraft for monitoring work and Vendor Status MCP for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Vendor Status MCP has no confirmed install command yet — follow its own setup instructions.
Statuscraft has no declared pricing — check the project's own site. Vendor Status MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add jabbawocky-statuscraft and vendor-status-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Statuscraft has a quality signal of 55/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Vendor Status MCP has 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.