trackmcp

Approved fixture catalogue

Test an MCP server with safe fixture scenarios

Use these scenarios to validate how a browser-direct MCP tester reports success, failure, authentication, pagination, and timeout behavior.

Echo catalog

A minimal healthy catalog with one descriptive, read-only tool definition.

Fixture endpoint publishing is separate

Authentication challenge

A controlled response that lets the tester distinguish authentication from browser blocking.

Fixture endpoint publishing is separate

Paginated catalog

Multiple tools/list pages for checking bounded cursor handling and truncation findings.

Fixture endpoint publishing is separate

Slow response

A delayed response scenario for checking cancellation, timeout, and incomplete verdicts.

Fixture endpoint publishing is separate

Protocol error

Malformed or JSON-RPC error responses for verifying safe error classification.

Fixture endpoint publishing is separate

Complex catalog

A larger catalog with schema variety for checking catalog quality and bounded rendering.

Fixture endpoint publishing is separate

Fixture boundary

This page does not fetch or host a mock server

The approved scenarios are listed here while their HTTPS fixture endpoints are published in a separate milestone. The tester itself remains browser-direct and never uses a server-side proxy.

Open the MCP tester