modelcontextprotocol / modelcontextprotocol/inspector
Web client's backend server has no health/readiness endpoint
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10.9k
- Forks
- 1.5k
- Avg merge
- 6h 17m
- Merged PRs (30d)
- 151
Description
Which client?
Web
The problem
clients/web/server/server.ts exposes the proxy/API routes but nothing like /healthz -- there's no cheap way for an orchestrator (Docker, Kubernetes, a process manager) to check the backend process is up without exercising a real proxy/connect flow.
Solution you have in mind (optional)
Add a minimal unauthenticated GET /healthz (or /api/health) returning 200 plus basic status, matching the pattern used by most Node HTTP services.
Alternatives or workarounds you have tried
No response
Already built it locally?
No response
Before you submit
- I searched existing issues and this is not a duplicate.
- This is a request for the Inspector itself, not for the MCP specification or an SDK.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in clients/web/server/server.ts and inspect how the existing proxy/API routes are registered and how the web client server handles requests. Add the agreed minimal unauthenticated health or readiness route, then verify it returns HTTP 200 with basic status without exercising a proxy or connection flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- api, backend, devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 76/100