io.github.labstack/pitot
Pitot
Is the Pitot MCP server down? No. It is up and needs your URL, probed 2026-11-13.
Investigate OpenTelemetry traces, metrics, and logs, and manage personal dashboards.
needs your URL probed 2026-11-14 · unchanged since 2026-11-13
The URL has placeholders that each user fills in: {pitot_host}.- Endpoint
- https://{pitot_host}/mcp (streamable-http)
- Host
- {pitot_host}
- Repository
- https://github.com/labstack/pitot
- Website
- https://pitot.dev
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Servers that mention opentelemetry or investigate.
- ai.getvda/llm-orchestration-agent-opentelemetry-api · newer protocol
- ai.getvda/llm-orchestration-agent-opentelemetry-instrumentation-fastapi · newer protocol
- ai.getvda/traced-openai-langchain-agent · newer protocol
- InfoLang Memory ai.infolang/mcp · no DNS
- Knowledge Grid ai.knowledgegrid/knowledge-grid · needs auth
- ai.smithery/demomagic-duckchain-mcp · not found
- Dregs com.dregs/dregs-mcp · needs auth
- Heystack dev.heystack/heystack · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- Every URL of the registry entry has a placeholder that each user fills in, such as a tenant, a project or a host of their own. Without that value there is nothing to call, so the probe does not call the URL, and the entry is not counted as down. A client asks the user for the value.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.