hono-telescope
Related Servers
Alternatives to hono-telescope
- AlicenseNot gradedqualityFmaintenanceA Model Context Protocol server implementation for Axiom that enables AI agents to query your data using Axiom Processing Language (APL).60MIT
- AlicenseNot gradedqualityDmaintenanceExposes Hono API endpoints as Model Context Protocol tools, allowing LLMs to interact with your API routes through a dedicated MCP endpoint. It provides helpers to describe routes and includes a codemode for dynamic API interaction via search and execute tools.42 npm86MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Sentry's error tracking and monitoring tools through a unified API, allowing natural language access to Sentry services.MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceEasily expose your Hono API endpoints as MCP tools with minimal configuration, supporting type-safe input handling and tool registration.42 npm2MIT
- AlicenseNot gradedqualityAmaintenanceSelf-hosted OpenTelemetry backend in one Go binary. Its MCP server exposes tools for service health, latency, topology, trace inspection, log search, read-only SQL over traces, logs and metrics, and dashboards.10Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Code, Codex, and Cursor to debug failing traces, sessions, and exceptions, inspect route decisions, prompts, datasets, and metrics, and control token overhead via compact output, file dumps, and selective tool loading. It supports local stdio or HTTP deployment with optional read-only mode for safer observability workflows.-
- AlicenseAqualityBmaintenanceRecord Python/Rust/TypeScript program runs to local SQLite; query call trees, exceptions, and value flow over MCP — refuses rather than guesses. Not the unrelated Telegram sensorium-mcp.9MIT
- FlicenseNot gradedqualityBmaintenanceRead-only MCP server for izlek, a terminal-first local frontend observability tool. Enables agents to query live session status, logs, errors, and HTTP request/response records from a running development session.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to locally debug observability data — traces, observations, sessions, exceptions, route decisions, prompts, datasets, metrics, and annotation queues — through 48 query and management tools. Supports selective tool-group loading to cut token overhead and a read-only mode that disables all write operations.-
TDQS
Scored across 5 tools
Each tool maps to a distinct investigation step: stats for overview, recent_exceptions for thrown failures, recent_requests for status-based failures, slow_queries for DB performance, and request_detail for full inspection. There is no pair an agent would realistically confuse after reading the descriptions.
All names are snake_case noun phrases with a consistent recent_* prefix for list views and a clear singular request_detail for deep dive. The only minor deviation is the abbreviated stats, but the overall pattern is otherwise uniform.
Five tools is well-scoped for a Telescope observability server: an entry point, two list views, one detail drill-down, and one performance view. There are no redundant tools, and the count fits the purpose comfortably.
The tools cover the full inspection workflow: check what is retained, list failures, drill into a single request, and identify slow queries. The workflow has no dead ends because every list tool points toward request_detail for deeper context.