create_mockLABSCO SUMMARY
The whole loop around an API, without four separate logins.
Mocking, security scanning, uptime monitoring and workflow automation are normally four separate products with four separate logins; the argument for this one is that they answer to the same conversation. The mocks, monitors and workflows are hosted state that persists after the chat ends, so the list tools matter — they are how you find what a previous session left running.
What it is
A hosted API-tooling server covering mocking, chaos injection, security and specification validation, network diagnostics, uptime monitoring, and workflow automation generated from specs or Postman collections. Everything runs against the vendor's service rather than on your machine.
What you get
- Mock endpoints created with custom response, headers and delay, then updated, listed and deleted
- Chaos rules created against an endpoint, listed and disabled
- A URL scanned for security issues across headers, TLS, CORS, CSP, HSTS and XSS, and its certificate checked for validity, expiry, issuer chain and protocols
- OpenAPI specifications validated, and JWTs decoded into header, payload and signature metadata
- Redirect chains analysed, CORS diagnosed against a given origin, distributed traces read from Jaeger, Zipkin or OpenTelemetry, and HAR files analysed for performance and errors
- Uptime monitors created with custom intervals and regions, and their status and uptime percentage read back
- Automation workflows created from steps, generated from an OpenAPI spec, imported from a Postman collection, then run and checked
- A webhook capture endpoint, and a resolve operation started
Requirements
A client pointed at https://mcp.httpstatus.com/mcp over Streamable HTTP. Clients that support OAuth2 authorise in the browser; others send an API key from httpstatus.com as a Bearer token.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
Building against an API that does not exist yet
Stand up a mock with the response, headers and delay the real service will have, so the client can be written and tested before the backend lands. List and update the mocks as the contract moves.
Finding out whether your endpoint is exposed
Scan the URL across headers, TLS, CORS, CSP, HSTS and XSS, and check the certificate's expiry and issuer chain in the same pass — the two checks that get skipped until an audit forces them.
Debugging a request that fails only in the browser
Run CORS diagnostics for the target and the origin, follow the redirect chain, and read the HAR the browser recorded — the three angles a CORS failure hides behind.
Turning a spec you already have into tests
Validate the OpenAPI document first, then generate an automation workflow from it or import an existing Postman collection, and run it.
Seeing how your client behaves when the API misbehaves
Create a chaos rule against the endpoint, watch what your retry logic actually does, then disable the rule — with the list call there to confirm nothing was left switched on.
Knowing before your users do
Create an uptime monitor on the interval and regions that match where your traffic comes from, and read its status and uptime percentage when someone asks.
24 tools
Listed in project docs. Your client may show a different list.
update_mockdelete_mocklist_mockscreate_chaos_ruledisable_chaos_rulelist_chaos_rulesrun_security_scancheck_sslvalidate_openapidecode_jwtrun_redirect_analyzerrun_cors_debugrun_traceanalyze_harcreate_monitorget_monitor_statusautomation_create_workflowautomation_generate_from_openapiautomation_import_postman_collectionautomation_run_workflowautomation_get_workflow_statuscapture_webhookstart_resolveBEFORE YOU INSTALL
What to know first
Tools you get
24 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
https://mcp.httpstatus.com/mcp