Context7 MCP Server
Context7 remote MCP server by Upstash (keyless): up-to-date library and framework documentation as MCP tools.
Operational
Last checked · response time 250 ms
90-day uptime
Monitoring since · 78 days of data
Past incidents
No incidents reported.
No incidents reported.
No incidents reported.
No incidents reported.
No incidents reported.
No incidents reported.
No incidents reported.
No incidents reported.
No incidents reported.
No incidents reported.
No incidents reported.
No incidents reported.
No incidents reported.
No incidents reported.
- Guardian-measuredResolvedContext7 MCP Server: HTTP 503 · resolved after 12m
- Guardian-measuredResolvedContext7 MCP Server: HTTP 503 · resolved (start not recorded)
- Guardian-measuredResolvedContext7 MCP Server: Unreachable · resolved (start not recorded)
- Availability incidentEndpoint has failed 3 consecutive polls (latest: HTTP 0)
- Availability incidentEndpoint has failed 3 consecutive polls (latest: HTTP 0)
- Availability incidentEndpoint has failed 3 consecutive polls (latest: HTTP 503)
- Guardian-measuredResolvedContext7 MCP Server: HTTP 503 · resolved after 6m
- Guardian-measuredResolvedContext7 MCP Server: HTTP 503 · resolved after 2m
- Guardian-measuredResolvedContext7 MCP Server: Unreachable · resolved after 14m
- Guardian-measuredResolvedContext7 MCP Server: Unreachable · resolved after 15m
Recent changes
No changes detected in 78 days of monitoring (since 2026-06-11).
Integrate
The live status, 90-day uptime figure and change history on this page are also machine-readable: embed the badge, poll the JSON, or subscribe to the feed. No key needed.
Status badge: 
Markdown embed: [](https://guardiandev.ai/mcp/context7-mcp)
Machine-readable: JSON (versioned v1, CORS-enabled) · Atom feed of drift & outage events.
Guardian probes https://mcp.context7.com/mcp about every 15 minutes. How Guardian measures.