Statuspage
Service status / uptime MCP — Atlassian Statuspage v2.
https://gateway.pipeworx.io/statuspage/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- pipeworx-gateway
- Version
- 0.1.0
- Capability keys
- tools, resources, prompts
- Tool names
- ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, search_within, deep_research, discover_tools, resolve_entity, compare_entities, subscribe, unsubscribe, list_subscriptions, recent_alerts, entity_profile, recent_changes, validate_claim, scan_dependency, bet_research, polymarket_arbitrage, polymarket_edges, polymarket_kalshi_spread, polymarket_fill_risk, polymarket_edge_tracker, pipeworx_trending, suggest_questions, generate_llms_txt, ai_visibility_check, scan_competitor_ai_presence, pipeworx_feedback, remember, recall, forget, statuspage_check, statuspage_incidents, statuspage_list_vendors, statuspage_multi_check
This Pipeworx connection is SCOPED to "statuspage": 4 tools across 1 pack(s) — statuspage. The 1 pack(s) above are the DIRECTLY listed tools. For ANYTHING ELSE — SEC filings, FDA/drugs, FRED/BLS economics, real estate, patents, weather, prediction markets, news, the full 5,558-tool catalog — just call ask_pipeworx({question}). On this connection it routes to AND runs the right tool across every pack and returns the answer; you do NOT need to add another server or connection. discover_tools({task}) browses the catalog (it flags packs as gated, but ask_pipeworx still runs them for you). Every tool ships inputSchema (+ examples) + outputSchema; errors carry retry_hint + feedback_hint for self-correction.
Reported Aug 17, 2026, 05:12 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 34ms