What you will accomplish
- Launch MCP Inspector with a compatible Node.js version
- List the live Quote.Trade tools and inspect their schemas
- Call public status and ticker tools without Quote.Trade account credentials; supply an MCP connector token only if the deployment requires one
- Save test results with secrets removed
Before you begin
- A Node.js version that satisfies the Inspector package’s current engines requirement
- npm/npx
- Network access to https://quote.trade/mcp
Confirm the runtime and Inspector version
Read the Inspector package version and engine requirement, then record the Node.js version before running the commands.
node --version
npm view @modelcontextprotocol/inspector version engines --jsonThe installed Node.js version satisfies the package engine requirement, and the Inspector version is recorded.
List tools through Streamable HTTP
Use the official remote HTTP CLI syntax and save stdout, stderr, and exit code.
npx -y @modelcontextprotocol/inspector@latest \
--cli https://quote.trade/mcp \
--transport http \
--method tools/list \
--format jsonExit code 0 and a non-empty tools array.
Call public status
Use the tool name returned by tools/list.
npx -y @modelcontextprotocol/inspector@latest \
--cli https://quote.trade/mcp \
--transport http \
--method tools/call \
--tool-name quote_trade_status \
--format jsonExit code 0 and a structured status result.
Call a public ticker
Select a symbol from current metadata rather than hard-coding an unavailable market.
npx -y @modelcontextprotocol/inspector@latest \
--cli https://quote.trade/mcp \
--transport http \
--method tools/call \
--tool-name quote_trade_ticker \
--tool-arg symbol=BTC \
--format jsonExit code 0 and a structured ticker result.
Save test results with secrets removed
Save the command, Node.js and Inspector versions, UTC time, endpoint, exit code, output, and returned protocol or session headers. Remove credentials, approval tokens, wallet details, and balances first.
Common problems and fixes
Inspector cannot negotiate the protocol
Confirm the current protocol version in discovery and update Inspector. Check required Accept and MCP-Protocol-Version headers.
The CLI syntax has changed
Run npx @modelcontextprotocol/inspector --cli --help and use the current official CLI documentation.
The endpoint works in a browser but not Inspector
A GET response is not an MCP handshake. Verify POST, transport selection, content negotiation, and session handling.
A tool schema differs from documentation
Use the live tools/list response. Update the client when those tool definitions change.
Answers before you continue
Does GET /mcp returning 405 mean the MCP server is working?
No. It can be expected for GET, but a passing test requires a POST initialize exchange and successful MCP methods.
Should Inspector be given live trading credentials?
No for the public test. Authenticated testing should use a controlled account, limited credentials, small order limits, and output with private details removed.