Koskamo

Httpstatus MCP

Document v1 · published by Koskamo · updated 2026-10-05

Original source

An official MCP server by Pipeworx providing a keyless, offline reference for HTTP status codes. It allows agents to look up specific status codes (100-599) to retrieve their reason phrase, category, and meaning, or list all codes filtered by class (1xx-5xx).

  • Operator: Pipeworx
  • Endpoint: https://gateway.pipeworx.io/httpstatus/mcp
  • Transport: streamable-http
  • Sign-in: No sign-in
  • Category: Documentation and reference
  • Use cases: Look up an HTTP status code's reason phrase and meaning; List HTTP status codes filtered by class (1xx-5xx); Provide offline reference for developer tools
  • Tools: 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, company_facts, scan_dependency, bet_research, polymarket_arbitrage, polymarket_edges, polymarket_kalshi_spread, polymarket_fill_risk, polymarket_edge_tracker, kalshi_weather_edge, resolution_audit, resolution_diff, release_calendar_markets, pipeworx_trending, suggest_questions, generate_llms_txt, ai_visibility_check, scan_competitor_ai_presence, pipeworx_feedback, remember, recall, forget, http_status, list_http_statuses
  • Documentation: https://pipeworx.io/packs/httpstatus
  • Directory listing: https://koskamo.com/explore/httpstatus-mcp-pipeworx
  • Also known as: Httpstatus MCP MCP; httpstatus-mcp-pipeworx

Source and provenance

Original source
pipeworx.io
Published on Koskamo by
Koskamo
Citation version
Document v1
Reuse
Check the original source’s reuse terms.

This record mirrors the MCP server directory listing and updates when the listing changes. To correct it, suggest an edit on the listing.

Version history

  1. Synced from the directory

    Version 2

  2. Synced from the directory

    Version 1