Skip to main content
GET
Health Check

Overview

Check the health status of the Pylance MCP server and your workspace. Use this to verify connectivity, monitor performance, and troubleshoot issues.

Request

boolean
default:"true"
Include workspace-specific health information
boolean
default:"false"
Include performance metrics

Response

string
Overall health status: healthy, degraded, unhealthy
object
Server health information
object
Workspace health information (if includeWorkspace: true)
object
Performance metrics (if includeMetrics: true)

Example Request

Example Response

Health Status

Use Cases

Startup Verification

Monitor Workspace Loading

Performance Monitoring

Troubleshooting Helper

Interpreting Metrics

Response Time

Error Rate

Requests Per Minute

Monitor to avoid rate limits:

Performance Tips

Lightweight: Health checks are fast (<10ms) and don’t count against rate limits Cache Status: Cache health status for 30-60 seconds to avoid excessive checks
Startup Only: Use detailed checks (metrics) only during startup/troubleshooting

Error Responses

Rate Limits

Health checks do not count toward your API rate limits. Check as often as needed.

Get Diagnostics

Check for code errors

List Files

See workspace file count

Workspace Structure

View project structure